Why structure conventions matter in Ruby on Rails - Performance Evidence

Performance: Why structure conventions matter

MEDIUM IMPACT

This affects how quickly the browser can load and render pages by enabling efficient asset loading and minimizing unnecessary file requests.

Organizing assets and code files in a Rails project

Ruby on Rails

app/assets/stylesheets/application.css
app/assets/javascripts/application.js
app/views/home/index.html.erb

# Files placed in standard Rails folders following naming conventions.

Rails asset pipeline precompiles and bundles assets efficiently, reducing HTTP requests and speeding up load.

📈 Performance GainImproves LCP by reducing asset load time and enabling browser caching.

Organizing assets and code files in a Rails project

Ruby on Rails

app/assets/stylesheets/custom.css
app/assets/javascripts/custom.js
app/views/home/index.html.erb

# Files placed randomly outside Rails conventions or in non-standard folders.

Rails cannot precompile or serve assets efficiently, causing extra HTTP requests and slower page load.

📉 Performance CostBlocks rendering longer due to inefficient asset pipeline and multiple HTTP requests.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Non-standard asset placement	No direct impact	No direct impact	Increased due to delayed CSS/JS loading	[X] Bad
Standard Rails structure	No direct impact	No direct impact	Reduced due to optimized asset loading	[OK] Good

Rendering Pipeline

Rails conventions enable the asset pipeline to bundle and serve CSS and JS efficiently, reducing the number of HTTP requests and file sizes. This speeds up Style Calculation and Paint stages in the browser.

→Network

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork requests for assets and Style Calculation due to CSS loading delays

Core Web Vital Affected

LCP

This affects how quickly the browser can load and render pages by enabling efficient asset loading and minimizing unnecessary file requests.

Optimization Tips

1Always place CSS and JS files in Rails standard asset folders.

2Use Rails naming conventions to enable asset pipeline bundling.

3Avoid random file placement to reduce HTTP requests and speed up LCP.

Performance Quiz - 3 Questions

How does following Rails structure conventions affect page load?

A It has no effect on asset loading

B It increases the number of HTTP requests for assets

C It reduces the number of HTTP requests by bundling assets

D It slows down the server response time

DevTools: Network

How to check: Open DevTools > Network tab > Reload page > Look for multiple small asset requests or large bundles

What to look for: Fewer, larger bundled asset files indicate good structure; many small requests indicate poor structure

Practice

1. Why is it important to follow structure conventions in a Rails application?

easy

A. Because Rails uses these conventions to automatically find files and connect parts of the app

B. Because it makes the app run faster by skipping code checks

C. Because it allows you to write less code by removing all comments

D. Because it prevents users from accessing the app without a password

Solution

1. Step 1: Understand Rails conventions role

   Rails relies on a specific folder and file structure to locate controllers, models, views, and other components automatically.

2. Step 2: Recognize the benefit of conventions

   Following these conventions means Rails can connect parts of the app without extra configuration, making development smoother.

3. Final Answer:

   Because Rails uses these conventions to automatically find files and connect parts of the app -> Option A

4. Quick Check:

   Rails conventions = automatic file connection [OK]

Hint: Rails finds files by convention, so follow the structure [OK]

Common Mistakes:

• Thinking conventions speed up runtime performance
• Believing conventions remove the need for comments
• Confusing conventions with security features

2. Which of the following is the correct folder for Rails controllers according to convention?

easy

A. app/models

B. app/controllers

C. app/views

D. app/helpers

Solution

1. Step 1: Recall Rails folder roles

   In Rails, controllers handle user requests and are placed in the app/controllers folder.

2. Step 2: Match folder to purpose

   Models go in app/models, views in app/views, and helpers in app/helpers.

3. Final Answer:

   app/controllers -> Option B

4. Quick Check:

   Controllers folder = app/controllers [OK]

Hint: Controllers live in app/controllers folder by Rails rules [OK]

Common Mistakes:

• Putting controllers in app/models
• Confusing views folder with controllers
• Using app/helpers for controllers

3. Given this Rails controller code, what will happen if the file is placed in app/models instead of app/controllers?

class ProductsController < ApplicationController
  def index
    @products = Product.all
  end
end

medium

A. The app will ignore the controller and show a blank page

B. Rails will find and use the controller normally

C. The code will run but views won't render

D. Rails will raise an error because it expects controllers in app/controllers

Solution

1. Step 1: Understand Rails file loading

   Rails loads controllers only from the app/controllers folder by convention.

2. Step 2: Predict behavior if misplaced

   If the controller file is in app/models, Rails won't find it as a controller and will raise a routing or missing controller error.

3. Final Answer:

   Rails will raise an error because it expects controllers in app/controllers -> Option D

4. Quick Check:

   Controllers must be in app/controllers [OK]

Hint: Controllers outside app/controllers cause errors [OK]

Common Mistakes:

• Assuming Rails finds controllers anywhere
• Thinking views won't render but no error occurs
• Believing the app ignores misplaced controllers silently

4. You moved a model file from app/models/user.rb to app/controllers/user.rb. What problem will this cause?

medium

A. Rails will treat the model as a controller and cause errors

B. Rails will load the model normally without issues

C. Rails will ignore the model and use a default one

D. Rails will automatically fix the file location

Solution

1. Step 1: Identify Rails loading rules for models

   Models must be in app/models for Rails to load them as data objects.

2. Step 2: Understand effect of wrong location

   Placing a model file in app/controllers makes Rails treat it as a controller, causing errors because the code does not match controller expectations.

3. Final Answer:

   Rails will treat the model as a controller and cause errors -> Option A

4. Quick Check:

   Models outside app/models cause loading errors [OK]

Hint: Models must stay in app/models or Rails misinterprets them [OK]

Common Mistakes:

• Thinking Rails auto-corrects file locations
• Assuming models load fine anywhere
• Believing Rails uses default models if missing

5. You want to add a new feature to your Rails app that shows a list of books. Which folder should you place the view files in to follow Rails conventions and ensure the app works correctly?

hard

A. app/models/books

B. app/controllers/books

C. app/views/books

D. app/assets/books

Solution

1. Step 1: Recall Rails view folder structure

   Views are stored in app/views inside a folder named after the controller, here books.

2. Step 2: Match feature to folder

   Since the feature is about books, the views go in app/views/books to match the BooksController and render pages properly.

3. Final Answer:

   app/views/books -> Option C

4. Quick Check:

   Views for books = app/views/books [OK]

Hint: Put views in app/views/controller_name folder [OK]

Common Mistakes:

• Placing views in controllers or models folders
• Using app/assets for views
• Not matching view folder to controller name