Template inheritance with base template in Django - Performance & Optimization

Performance: Template inheritance with base template

MEDIUM IMPACT

This affects the server-side rendering speed, impacting the initial page load time.

Reusing common layout across multiple pages

Django

{% comment %}Base template with blocks{% endcomment %}
<!-- base.html -->
<html>
<head><title>{% block title %}Default Title{% endblock %}</title></head>
<body>
<header>Site header</header>
<main>{% block content %}{% endblock %}</main>
<footer>Site footer</footer>
</body>
</html>

{% comment %}Child template{% endcomment %}
{% extends "base.html" %}
{% block title %}Page 1{% endblock %}
{% block content %}Content for page 1{% endblock %}

Template inheritance avoids repeating HTML, so server compiles less code.

📈 Performance GainReduces server template parsing time, improving LCP.

Reusing common layout across multiple pages

Django

{% comment %}Each page repeats full HTML structure{% endcomment %}
<html>
<head><title>Page 1</title></head>
<body>
<header>Site header</header>
<main>Content for page 1</main>
<footer>Site footer</footer>
</body>
</html>

Repeating full HTML structure in every template causes larger template files and more server processing.

📉 Performance CostIncreases server template parsing time, slowing LCP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Repeated full HTML in each template	No change (server-side)	No change (browser)	Larger templates increase server parsing time	[X] Bad
Template inheritance with base template	No change (server-side)	No change (browser)	Smaller templates reduce server parsing time	[OK] Good

Rendering Pipeline

Template inheritance is resolved on the server before HTML is sent. The browser receives a single combined HTML document.

→Server Template Rendering

⚠️ BottleneckServer Template Rendering can be slower if templates are large and duplicated.

Core Web Vital Affected

LCP

This affects the server-side rendering speed, impacting the initial page load time.

Optimization Tips

1Use base templates to avoid repeating full HTML in every page.

2Define blocks for variable content to keep templates small and reusable.

3Efficient server rendering from inheritance improves loading speed.

Performance Quiz - 3 Questions

How does template inheritance affect the size of the HTML sent to the browser?

A It increases HTML size by adding extra tags

B It has no effect on HTML size

C It reduces HTML size by avoiding repeated code

D It duplicates HTML for each block

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and inspect the HTML document size and load time.

What to look for: Faster document load time indicates good template inheritance usage.

Practice

1. What is the main purpose of using {% extends %} in a Django template?

easy

A. To define a new block inside the template

B. To include JavaScript files in the template

C. To inherit the layout and content from a base template

D. To load static files like images or CSS

Solution

1. Step 1: Understand the role of {% extends %}

   This tag tells Django to use another template as the base layout for the current template.

2. Step 2: Compare with other options

   Options B, C, and D describe different template tags or functions unrelated to inheritance.

3. Final Answer:

   To inherit the layout and content from a base template -> Option C

4. Quick Check:

   {% extends %} = inherit base template [OK]

Hint: Remember: extends means 'use base template' [OK]

Common Mistakes:

• Confusing extends with include
• Thinking extends loads static files
• Mixing block and extends tags

2. Which of the following is the correct syntax to define a block named 'content' in a Django template?

easy

A. {% content block %} ... {% endcontent %}

B. {% block 'content' %} ... {% endblock %}

C. {% define content %} ... {% enddefine %}

D. {% block content %} ... {% endblock %}

Solution

1. Step 1: Recall block syntax in Django templates

   The correct syntax uses {% block blockname %} and closes with {% endblock %} without quotes.

2. Step 2: Check each option

   {% block content %} ... {% endblock %} matches the correct syntax. Options A, C, and D use invalid tags. {% block 'content' %} ... {% endblock %} incorrectly uses quotes around the block name.

3. Final Answer:

   {% block content %} ... {% endblock %} -> Option D

4. Quick Check:

   Block syntax = {% block name %} ... {% endblock %} [OK]

Hint: Blocks never use quotes around their names [OK]

Common Mistakes:

• Adding quotes around block names
• Using wrong tag names like define or content block
• Forgetting to close the block with endblock

3. Given the base template

{% raw %}{% block title %}Base Title{% endblock %}{% block content %}Base Content{% endblock %}{% endraw %}

and a child template

{% raw %}{% extends 'base.html' %}{% block title %}Child Title{% endblock %}{% endraw %}

, what will be the rendered output for the content block when rendering the child template?

medium

A. Base Content

B. Child Title

C. Child Content

D. Empty content block

Solution

1. Step 1: Understand block overriding in inheritance

   The child template overrides only the title block, so the content block remains as defined in the base template.

2. Step 2: Determine output for content block

   Since the child does not override content, the base template's Base Content is used.

3. Final Answer:

   Base Content -> Option A

4. Quick Check:

   Unchanged blocks show base content [OK]

Hint: Only overridden blocks change output [OK]

Common Mistakes:

• Assuming all blocks are replaced
• Confusing title block content with content block
• Expecting empty output if block not overridden

4. Identify the error in this child template code:

{% raw %}{% extends 'base.html' %}{% block content %}Hello World{% endblock content %}{% endraw %}

medium

A. Incorrect closing tag for block; should be {% endblock %} not {% endblock content %}

B. Missing {% load static %} tag

C. The extends tag must be at the end of the file

D. Block name 'content' is invalid

Solution

1. Step 1: Check block closing syntax

   The correct way to close a block is with {% endblock %} without repeating the block name.

2. Step 2: Verify other options

   Missing {% load static %} tag is unrelated to block syntax. The extends tag must be at the end of the file is false; extends must be at the top. Block name 'content' is invalid is incorrect; 'content' is a valid block name.

3. Final Answer:

   Incorrect closing tag for block; should be {% endblock %} not {% endblock content %} -> Option A

4. Quick Check:

   Block ends with {% endblock %} only [OK]

Hint: End blocks with just {% endblock %} [OK]

Common Mistakes:

• Adding block name after endblock
• Placing extends tag incorrectly
• Confusing load static with block syntax

5. You have a base template with blocks header, content, and footer. You want a child template to reuse the base layout but add a sidebar inside the content block without losing the original content. Which is the correct way to do this?

hard

A. {% raw %}{% extends 'base.html' %}{% block sidebar %}Sidebar content{% endblock %}{% endraw %}

B. {% raw %}{% extends 'base.html' %}{% block content %}{{ block.super }}Sidebar content{% endblock %}{% endraw %}

C. {% raw %}{% extends 'base.html' %}{% block content %}Sidebar content{% endblock %}{% endraw %}

D. {% raw %}{% extends 'base.html' %}{% block content %}Sidebar content{% endblock %}{% endraw %}

Solution

1. Step 1: Understand how to keep base content in a block

   Using {{ block.super }} inside a block includes the original content from the base template's block.

2. Step 2: Analyze options

   {% raw %}{% extends 'base.html' %}{% block content %}{{ block.super }}
   Sidebar content{% endblock %}{% endraw %} correctly adds sidebar content after the original content. Options B and D replace the content entirely. {% raw %}{% extends 'base.html' %}{% block sidebar %}Sidebar content{% endblock %}{% endraw %} tries to add a new block 'sidebar' which doesn't exist in base, so it won't appear.

3. Final Answer:

   {% extends 'base.html' %}{% block content %}{{ block.super }}
   Sidebar content
   {% endblock %} -> Option B

4. Quick Check:

   Use {{ block.super }} to keep base block content [OK]

Hint: Use {{ block.super }} to keep base block content [OK]

Common Mistakes:

• Overwriting block content without block.super
• Adding blocks not defined in base template
• Forgetting to extend the base template