Asset pipeline basics in Ruby on Rails - Performance & Optimization

Performance: Asset pipeline basics

HIGH IMPACT

This affects page load speed by controlling how CSS, JavaScript, and images are combined, compressed, and served to the browser.

Serving CSS and JavaScript files in a Rails app

Ruby on Rails

Using Rails asset pipeline to concatenate, minify, and fingerprint assets into single compressed files.

Reduces number of HTTP requests and file sizes, enabling faster loading and caching.

📈 Performance GainSingle HTTP request for CSS and JS, smaller file sizes, faster LCP.

Serving CSS and JavaScript files in a Rails app

Ruby on Rails

In development, serving many separate CSS and JS files without compression or concatenation.

Multiple HTTP requests and uncompressed files increase load time and block rendering.

📉 Performance CostTriggers many HTTP requests and blocks rendering until all files load.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Multiple separate CSS/JS files	N/A	N/A	Blocks rendering until all files load	[X] Bad
Concatenated and minified assets	N/A	N/A	Faster render, fewer blocking resources	[OK] Good

Rendering Pipeline

The asset pipeline processes source files into optimized bundles that the browser downloads and parses, affecting the critical rendering path.

→Network

→Parse & Compile

→Render

⚠️ BottleneckNetwork latency and blocking scripts/styles delay initial render.

Core Web Vital Affected

LCP

This affects page load speed by controlling how CSS, JavaScript, and images are combined, compressed, and served to the browser.

Optimization Tips

1Combine CSS and JS files to reduce HTTP requests.

2Minify and compress assets to reduce file size.

3Use fingerprinting for effective browser caching.

Performance Quiz - 3 Questions

How does using the Rails asset pipeline improve page load speed?

A By adding more CSS and JS files to increase functionality

B By disabling browser caching for assets

C By combining and compressing CSS and JS files to reduce HTTP requests and file size

D By loading assets only after the page is fully rendered

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and observe number and size of CSS/JS files loaded.

What to look for: Fewer, smaller files indicate good asset pipeline usage; many large files indicate poor optimization.

Practice

1. What is the main purpose of the Rails asset pipeline?

easy

A. To generate HTML templates dynamically

B. To handle database migrations automatically

C. To combine, compress, and manage CSS, JavaScript, and images for faster loading

D. To manage user authentication and sessions

Solution

1. Step 1: Understand asset pipeline role

   The asset pipeline organizes and prepares CSS, JavaScript, and images for the app.

2. Step 2: Identify its main benefits

   It combines and compresses assets to improve website speed and maintenance.

3. Final Answer:

   To combine, compress, and manage CSS, JavaScript, and images for faster loading -> Option C

4. Quick Check:

   Asset pipeline = combine and compress assets [OK]

Hint: Asset pipeline = faster loading by combining assets [OK]

Common Mistakes:

• Confusing asset pipeline with database tasks
• Thinking it generates HTML templates
• Mixing it up with user authentication

2. Which file is typically used to specify which JavaScript files to include in the Rails asset pipeline?

easy

A. application.js

B. routes.rb

C. database.yml

D. Gemfile

Solution

1. Step 1: Identify manifest files for assets

   Rails uses manifest files like application.js to list JavaScript files to include.

2. Step 2: Recognize unrelated files

   routes.rb manages URL routes, database.yml configures database, Gemfile manages gems.

3. Final Answer:

   application.js -> Option A

4. Quick Check:

   JavaScript manifest = application.js [OK]

Hint: JavaScript manifest file is application.js [OK]

Common Mistakes:

• Choosing routes.rb which is for routing
• Confusing Gemfile with asset files
• Picking database.yml which is unrelated

3. Given the following snippet in app/assets/javascripts/application.js:

//= require jquery
//= require_tree .

What will happen when the asset pipeline processes this file?

medium

A. It will cause a syntax error and fail to compile

B. It will only include jQuery and ignore other files

C. It will include files in reverse alphabetical order

D. It will include jQuery first, then all other JavaScript files in the directory

Solution

1. Step 1: Understand require directives

   "//= require jquery" includes jQuery first; "//= require_tree ." includes all files in the directory.

2. Step 2: Determine inclusion order

   jQuery is included first, then all other JavaScript files are included in alphabetical order.

3. Final Answer:

   It will include jQuery first, then all other JavaScript files in the directory -> Option D

4. Quick Check:

   require + require_tree = jQuery then all files [OK]

Hint: require_tree includes all files after listed requires [OK]

Common Mistakes:

• Thinking require_tree ignores previous requires
• Assuming syntax error from comments
• Believing files load in reverse order

4. You added a new CSS file custom.css to app/assets/stylesheets but it does not appear on your site. What is the most likely cause?

medium

A. You forgot to add *= require custom in application.css

B. The file name must be custom.scss to work

C. CSS files are not supported by the asset pipeline

D. You need to restart the Rails server to load new assets

Solution

1. Step 1: Check manifest file inclusion

   New CSS files must be included in application.css manifest using "*= require filename".

2. Step 2: Verify other options

   CSS files are supported; file extension .css is valid; server restart is not required for asset changes.

3. Final Answer:

   You forgot to add *= require custom in application.css -> Option A

4. Quick Check:

   Missing require in manifest = no CSS load [OK]

Hint: Add *= require line in application.css to include new CSS [OK]

Common Mistakes:

• Thinking .css files are unsupported
• Assuming server restart is needed
• Believing file extension must be .scss

5. You want to add a new image logo.png to your Rails app and use it in CSS. Which is the correct way to reference it in application.css using the asset pipeline?

hard

A. background-image: url('/assets/logo.png');

B. background-image: image-url('logo.png');

C. background-image: url('logo.png');

D. background-image: asset_path('logo.png');

Solution

1. Step 1: Understand asset pipeline helpers in CSS

   Rails asset pipeline uses helper functions like image-url() in CSS to reference images correctly with fingerprinting.

2. Step 2: Evaluate options

   background-image: url('/assets/logo.png'); uses a hardcoded path which may break with asset fingerprinting; background-image: url('logo.png'); lacks helper; background-image: asset_path('logo.png'); is invalid CSS syntax.

3. Final Answer:

   background-image: image-url('logo.png'); -> Option B

4. Quick Check:

   Use image-url() helper for images in CSS [OK]

Hint: Use image-url() helper to reference images in CSS [OK]

Common Mistakes:

• Hardcoding asset paths breaking fingerprinting
• Using url() without helper in asset pipeline
• Trying to use Ruby helpers directly in CSS