Macros for reusable components in Flask - Performance & Optimization

Performance: Macros for reusable components

MEDIUM IMPACT

This affects page load speed by reducing template parsing time and DOM complexity through reusable HTML snippets.

Creating reusable HTML components in Flask templates

Flask

{% raw %}
{% macro card(title, description) %}
  <div class="card">
    <h2>{{ title }}</h2>
    <p>{{ description }}</p>
  </div>
{% endmacro %}

{{ card('Title 1', 'Description 1') }}
{{ card('Title 2', 'Description 2') }}
{% endraw %}

Defines reusable macro once, reducing template size and parsing overhead while keeping DOM structure consistent.

📈 Performance GainSingle macro parse, smaller template size, faster LCP, easier maintenance.

Creating reusable HTML components in Flask templates

Flask

{% raw %}
<!-- Repeating same HTML block multiple times -->
<div class="card">
  <h2>{{ title }}</h2>
  <p>{{ description }}</p>
</div>
<div class="card">
  <h2>{{ title2 }}</h2>
  <p>{{ description2 }}</p>
</div>
{% endraw %}

Repeating HTML blocks increases template size and parsing time, causing slower rendering and harder maintenance.

📉 Performance CostTriggers multiple template parses and larger DOM size, increasing LCP time.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Repeated HTML blocks	More nodes due to duplication	Multiple reflows as DOM grows	Higher paint cost due to larger DOM	[X] Bad
Macros for reusable components	Fewer nodes, reused structure	Single reflow per component type	Lower paint cost with smaller DOM	[OK] Good

Rendering Pipeline

Macros are expanded during template rendering on the server, producing cleaner HTML sent to the browser, reducing client-side parsing and layout complexity.

→Template Parsing

→HTML Generation

→DOM Construction

→Layout

⚠️ BottleneckTemplate Parsing and HTML Generation on server

Core Web Vital Affected

LCP

This affects page load speed by reducing template parsing time and DOM complexity through reusable HTML snippets.

Optimization Tips

1Use macros to avoid repeating HTML code in templates.

2Smaller templates parse faster and reduce server response time.

3Reducing DOM size improves browser rendering and LCP.

Performance Quiz - 3 Questions

How do macros improve Flask template performance?

A By adding more CSS styles inline

B By increasing the number of DOM nodes

C By reducing repeated HTML code and template parsing time

D By delaying server response

DevTools: Performance

How to check: Record page load and look for scripting and rendering times; compare template sizes in Network panel.

What to look for: Lower scripting time and smaller HTML size indicate efficient macro use; large repeated blocks increase load time.

Practice

1. What is the main purpose of using {% macro %} in Flask templates?

easy

A. To create reusable blocks of HTML code

B. To define Python functions inside templates

C. To import external CSS files

D. To handle form submissions

Solution

1. Step 1: Understand what macros do in Flask templates

   Macros are used to write reusable HTML blocks that can be called multiple times to avoid repetition.

2. Step 2: Compare options with macro purpose

   Only To create reusable blocks of HTML code correctly describes macros as reusable HTML blocks. Other options describe unrelated tasks.

3. Final Answer:

   To create reusable blocks of HTML code -> Option A

4. Quick Check:

   Macros = reusable HTML blocks [OK]

Hint: Macros create reusable HTML snippets in templates [OK]

Common Mistakes:

• Thinking macros define Python functions
• Confusing macros with CSS imports
• Assuming macros handle form data

2. Which of the following is the correct syntax to define a macro named button that takes a parameter label?

easy

A. {% define button(label) %} {{ label }} {% enddefine %}

B. {% macro button(label) %} {{ label }} {% endmacro %}

C. {{ macro button(label) }} {{ label }} {{ endmacro }}

D. <% macro button(label) %> {{ label }} <% endmacro %>

Solution

1. Step 1: Recall correct macro syntax in Flask Jinja templates

   Macros are defined with {% macro name(params) %} ... {% endmacro %} tags.

2. Step 2: Check each option's syntax

   {% macro button(label) %} {{ label }} {% endmacro %} uses correct {% %} tags and endmacro. Others use wrong delimiters or keywords.

3. Final Answer:

   {% macro button(label) %} <button>{{ label }}</button> {% endmacro %} -> Option B

4. Quick Check:

   Macro syntax = {% macro %} ... {% endmacro %} [OK]

Hint: Use {% macro %} and {% endmacro %} to define macros [OK]

Common Mistakes:

• Using {{ }} instead of {% %} for macro definition
• Using incorrect keywords like define or <% %>
• Forgetting the endmacro tag

3. Given the macro defined in macros.html as:

{% raw %}{% macro greet(name) %}Hello, {{ name }}!{% endmacro %}{% endraw %}

And imported in index.html with:

{% raw %}{% import 'macros.html' as m %}{% endraw %}

What will be the output of {{ m.greet('Alice') }} in index.html?

medium

A. Error: macro not found

B. {{ m.greet('Alice') }}

C. greet('Alice')

D. Hello, Alice!

Solution

1. Step 1: Understand macro import and usage

   The macro greet(name) returns 'Hello, {{ name }}!'. Importing as m allows calling m.greet('Alice').

2. Step 2: Evaluate the macro call output

   Calling m.greet('Alice') replaces {{ name }} with 'Alice', so output is 'Hello, Alice!'.

3. Final Answer:

   Hello, Alice! -> Option D

4. Quick Check:

   Macro call with parameter = rendered string [OK]

Hint: Imported macros called with alias render output [OK]

Common Mistakes:

• Expecting literal macro call text instead of rendered output
• Forgetting to import macros before use
• Confusing macro call syntax with variable output

4. What is wrong with this macro usage in a Flask template?

{% raw %}{% macro card(title) %}
{{ title }}
{% endmacro %}{% endraw %}
{{ card() }}

medium

A. The macro is not properly closed with {% endmacro %}

B. Macros cannot return HTML elements

C. The macro is called without the required parameter

D. The macro name is invalid

Solution

1. Step 1: Check macro definition and parameters

   The macro card requires one parameter: title.

2. Step 2: Check macro call

   The call {{ card() }} provides no argument, causing an error due to missing parameter.

3. Final Answer:

   The macro is called without the required parameter -> Option C

4. Quick Check:

   Missing macro argument = error [OK]

Hint: Always pass required parameters when calling macros [OK]

Common Mistakes:

• Calling macros without required arguments
• Thinking macros must return plain text only
• Missing endmacro tag (not the case here)

5. You want to create a reusable navigation bar macro that highlights the current page. Which approach correctly uses macros and parameters to achieve this?

hard

A. {% raw %}{% macro navbar(current) %}HomeAbout{% endmacro %}{% endraw %} Then call with {{ navbar('about') }}

B. {% raw %}{% macro navbar() %}HomeAbout{% endmacro %}{% endraw %} Then call with {{ navbar() }}

C. {% raw %}{% macro navbar(current) %}HomeAbout{% endmacro %}{% endraw %} Then call with {{ navbar('home') }}

D. {% raw %}{% macro navbar(current) %}HomeAbout{% endmacro %}{% endraw %} Then call with {{ navbar('home') }}

Solution

1. Step 1: Understand the need for dynamic class assignment

   The macro should accept a parameter to know which page is current and add 'active' class accordingly.

2. Step 2: Analyze each option's approach

   {% raw %}{% macro navbar(current) %}
   HomeAbout
   {% endmacro %}{% endraw %} Then call with {{ navbar('about') }} uses a parameter and conditional expression to add 'active' class only to the current page link. Others either hardcode classes or ignore the parameter.

3. Final Answer:

   Uses parameters and conditional logic to highlight current page -> Option A

4. Quick Check:

   Dynamic class with parameter = correct navbar macro [OK]

Hint: Use macro parameters with conditionals for dynamic HTML [OK]

Common Mistakes:

• Hardcoding active class without parameters
• Ignoring the current page parameter
• Assigning 'current' class to all links