Template partials and layouts in Express - Performance & Optimization

Performance: Template partials and layouts

MEDIUM IMPACT

This affects the server-side rendering speed and the size of the HTML sent to the browser, impacting the Largest Contentful Paint (LCP).

Rendering repeated HTML structures in multiple pages

Express

app.set('view engine', 'ejs');

// layout.ejs contains common header and footer
// page1.ejs and page2.ejs include only page-specific content

app.get('/page1', (req, res) => {
  res.render('page1', { title: 'Page 1' });
});

app.get('/page2', (req, res) => {
  res.render('page2', { title: 'Page 2' });
});

Using layouts and partials avoids repeating HTML, reducing server work and response size.

📈 Performance GainReduces server render time and HTML size, improving LCP by 100-200ms.

Rendering repeated HTML structures in multiple pages

Express

app.get('/page1', (req, res) => {
  res.render('page1', { title: 'Page 1' });
});

// page1.ejs contains full HTML including header and footer hardcoded

app.get('/page2', (req, res) => {
  res.render('page2', { title: 'Page 2' });
});

// page2.ejs also repeats full HTML header and footer

Duplicated HTML in each template increases server processing and response size, slowing rendering.

📉 Performance CostBlocks server rendering longer and sends larger HTML, increasing LCP by 100-200ms on average.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Duplicated full HTML in each template	High (large HTML size)	N/A (server-side)	High (large HTML to parse)	[X] Bad
Using partials and layouts for common HTML	Low (smaller HTML size)	N/A (server-side)	Low (smaller HTML to parse)	[OK] Good

Rendering Pipeline

Template partials and layouts reduce duplicated HTML generation on the server, lowering the time to produce the final HTML sent to the browser.

→Server-side Rendering

→Network Transfer

→Browser Parsing

⚠️ BottleneckServer-side Rendering time due to duplicated template processing

Core Web Vital Affected

LCP

This affects the server-side rendering speed and the size of the HTML sent to the browser, impacting the Largest Contentful Paint (LCP).

Optimization Tips

1Use layouts to wrap common HTML like headers and footers.

2Use partials for repeated smaller pieces like navigation or widgets.

3Avoid duplicating full HTML in each template to reduce server render time.

Performance Quiz - 3 Questions

How do template partials and layouts improve server rendering performance?

A By reusing common HTML to reduce duplicated template processing

B By increasing the number of DOM nodes on the client

C By adding more CSS styles to the page

D By delaying the server response intentionally

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network tab, reload page and check HTML response size; then use Performance tab to measure LCP timing.

What to look for: Smaller HTML response size and faster LCP time indicate good use of partials and layouts.

Practice

1. What is the main purpose of using template partials in Express apps?

easy

A. To define the main layout structure for all pages

B. To reuse small template parts like headers or footers across pages

C. To write JavaScript logic inside templates

D. To connect the app to a database

Solution

1. Step 1: Understand what partials are

   Partials are small pieces of templates like headers or footers that you can reuse.

2. Step 2: Differentiate partials from layouts

   Layouts provide the main page structure, while partials are smaller reusable parts inside layouts or pages.

3. Final Answer:

   To reuse small template parts like headers or footers across pages -> Option B

4. Quick Check:

   Partials = reusable small template parts [OK]

Hint: Partials = small reusable pieces like header/footer [OK]

Common Mistakes:

• Confusing partials with layouts
• Thinking partials define full page structure
• Assuming partials handle backend logic

2. Which syntax correctly includes a partial named header in an EJS template?

easy

A. <%- include('header') %>

B. <%= partial('header') %>

C. <% include header %>

D. <@include header>

Solution

1. Step 1: Recall EJS partial include syntax

   EJS uses <%- include('partialName') %> to include partials with unescaped output.

2. Step 2: Check each option

   <%- include('header') %> matches the correct syntax with parentheses and quotes around 'header'.

3. Final Answer:

   <%- include('header') %> -> Option A

4. Quick Check:

   EJS partial include = <%- include('name') %> [OK]

Hint: EJS partials use <%- include('name') %> syntax [OK]

Common Mistakes:

• Omitting quotes or parentheses in include
• Using <%= instead of <%- for unescaped output
• Confusing syntax with other template engines

3. Given this Express setup using EJS with a layout:

app.set('view engine', 'ejs');

// In route handler:
res.render('index', { title: 'Home' });

And the layout layout.ejs contains:

<html>
<head><title><%= title %></title></head>
<body>
<%- body %>
</body>
</html>

If index.ejs has <h1>Welcome</h1>, what will the rendered HTML look like?

medium

A. Welcome

B. Home<h1>Welcome</h1>

C. HomeWelcome

D. Error: body is undefined

Solution

1. Step 1: Understand layout and body insertion

   The layout uses <%- body %> to insert the rendered content of index.ejs unescaped.

2. Step 2: Check variable substitution

   The title variable is passed as 'Home', so <%= title %> becomes 'Home'. The body inserts <h1>Welcome</h1> as HTML.

3. Final Answer:

   <html><head><title>Home</title></head><body><h1>Welcome</h1></body></html> -> Option C

4. Quick Check:

   Layout inserts title and body correctly [OK]

Hint: Layout inserts body unescaped with <%- body %> [OK]

Common Mistakes:

• Using escaped output <%= body %> causing HTML to show as text
• Not passing title variable to template
• Assuming body variable is automatic without layout support

4. You try to use a layout in Express with EJS but get an error: ReferenceError: body is not defined. What is the likely cause?

medium

A. You forgot to use a layout engine or middleware that injects the body content

B. You used <%= body %> instead of <%- body %>

C. You named your layout file incorrectly

D. You did not install EJS package

Solution

1. Step 1: Understand how layouts work in Express with EJS

   EJS alone does not support layouts natively; you need middleware like express-ejs-layouts to inject body content.

2. Step 2: Identify cause of ReferenceError

   If body is undefined, it means the layout engine or middleware that sets body is missing or not configured.

3. Final Answer:

   You forgot to use a layout engine or middleware that injects the body content -> Option A

4. Quick Check:

   Missing layout middleware = body undefined error [OK]

Hint: Layouts need middleware to define body variable [OK]

Common Mistakes:

• Assuming EJS supports layouts without extra setup
• Confusing escaped vs unescaped output errors
• Ignoring middleware installation or configuration

5. You want to create a consistent site with a header, footer, and main content area using Express and EJS. Which approach best uses partials and layouts together?

hard

A. Use only partials for header, footer, and content without any layout file

B. Include header and footer partials directly in every page template without a layout

C. Write all HTML in each page template without partials or layouts

D. Create a layout.ejs with header and footer partials included, and insert page content in a <%- body %> area

Solution

1. Step 1: Understand roles of layouts and partials

   Layouts provide the main page structure; partials are reusable pieces like header and footer.

2. Step 2: Combine layout and partials for best practice

   Put header and footer partials inside the layout, then insert page-specific content in the body area.

3. Final Answer:

   Create a layout.ejs with header and footer partials included, and insert page content in a <%- body %> area -> Option D

4. Quick Check:

   Layout + partials = clean, consistent site structure [OK]

Hint: Use layout for structure, partials for reusable parts [OK]

Common Mistakes:

• Duplicating header/footer in every page instead of partials
• Skipping layout causing inconsistent page structure
• Mixing content and layout roles improperly