Absolute vs relative URLs in HTML - Performance Comparison

Performance: Absolute vs relative URLs

MEDIUM IMPACT

This concept affects page load speed by influencing how quickly the browser can resolve and fetch resources.

Linking to internal resources on the same website

HTML

<img src="/images/photo.jpg" alt="Photo">

Relative URLs avoid extra DNS lookups and reuse existing connections, speeding up resource loading.

📈 Performance GainSaves DNS lookup time and reduces request latency by 50-100ms per resource

Linking to internal resources on the same website

HTML

<img src="https://www.example.com/images/photo.jpg" alt="Photo">

Using absolute URLs for internal resources causes extra DNS lookups and longer request times.

📉 Performance CostAdds extra DNS lookup and connection setup, increasing load time by 50-100ms per resource

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Absolute URL for internal resource	No extra DOM nodes	0	Minimal	[✗] Bad
Relative URL for internal resource	No extra DOM nodes	0	Minimal	[✓] Good

Rendering Pipeline

When the browser encounters a URL, it resolves it to a full address before fetching the resource. Absolute URLs require full resolution including DNS lookup, while relative URLs resolve faster using the current page's base URL.

→DNS Lookup

→Connection Setup

→Resource Fetching

⚠️ BottleneckDNS Lookup and Connection Setup

Core Web Vital Affected

LCP

This concept affects page load speed by influencing how quickly the browser can resolve and fetch resources.

Optimization Tips

1Use relative URLs for internal resources to reduce DNS lookups and speed up loading.

2Use absolute URLs for external resources to avoid confusion and ensure correct fetching.

3Check base URL settings to avoid broken relative links that hurt user experience.

Performance Quiz - 3 Questions

Why do relative URLs often load internal resources faster than absolute URLs?

A They use a different server optimized for speed

B They compress the resource automatically

C They avoid extra DNS lookups and reuse existing connections

D They load resources asynchronously by default

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and look at the requests for internal resources. Check if DNS lookup and connection times are present.

What to look for: Look for DNS Lookup and Initial Connection times. Relative URLs should show fewer or no DNS lookups compared to absolute URLs.

Practice

1. Which of the following best describes an absolute URL?

easy

A. A link that starts with a slash, like /images/photo.jpg

B. A full web address including protocol and domain, like https://example.com/page

C. A link that points to a file in the same folder, like photo.jpg

D. A URL that only works on your local computer

Solution

1. Step 1: Understand what an absolute URL is

   An absolute URL includes the full address: protocol (http/https), domain, and path.

2. Step 2: Compare options to definition

   A full web address including protocol and domain, like https://example.com/page shows a full address with protocol and domain, matching the absolute URL definition.

3. Final Answer:

   A full web address including protocol and domain, like https://example.com/page -> Option B

4. Quick Check:

   Absolute URL = full web address [OK]

Hint: Absolute URLs always start with http:// or https:// [OK]

Common Mistakes:

• Confusing relative URLs with absolute URLs
• Thinking a URL starting with / is absolute
• Believing file names alone are absolute URLs

2. Which of these is the correct way to write a relative URL to link to a file named style.css in the same folder?

easy

A. style.css

B. https://example.com/style.css

C. /style.css

D. ../style.css

Solution

1. Step 1: Understand relative URLs in the same folder

   A relative URL to a file in the same folder can be just the file name.

2. Step 2: Check options for correct relative URL

   style.css uses just style.css, which correctly points to the file in the same folder.

3. Final Answer:

   style.css -> Option A

4. Quick Check:

   Relative URL same folder = file name only [OK]

Hint: Use just the file name for same-folder relative URLs [OK]

Common Mistakes:

• Using a leading slash which points to root folder
• Using full URLs when relative is needed
• Using ../ which points to parent folder

3. Given the current page URL is https://example.com/blog/post1.html, what will the browser load for the relative URL ../images/pic.jpg?

medium

A. https://example.com/images/pic.jpg

B. https://example.com/blog/images/pic.jpg

C. https://example.com/blog/post1.html/images/pic.jpg

D. https://images/pic.jpg

Solution

1. Step 1: Understand the meaning of .. in relative URLs

   .. means go up one folder from the current page location.

2. Step 2: Apply to current URL

   Current URL folder is /blog/. Going up one folder leads to /. Then adding images/pic.jpg gives /images/pic.jpg.

3. Final Answer:

   https://example.com/images/pic.jpg -> Option A

4. Quick Check:

   .. moves up one folder [OK]

Hint: .. means go up one folder in URL path [OK]

Common Mistakes:

• Thinking .. stays in the same folder
• Appending path without going up folder
• Confusing relative with absolute URLs

4. You wrote this HTML link: <a href="images/photo.jpg">Photo</a> on the page https://example.com/about/index.html, but the image does not load. What is the likely problem?

medium

A. The URL should be absolute starting with https://

B. The relative URL is missing a leading slash to start from root

C. The file extension .jpg is incorrect

D. The relative URL points to a folder that does not exist relative to current page

Solution

1. Step 1: Understand relative URL resolution

   The relative URL images/photo.jpg looks for an images folder inside the current folder /about/.

2. Step 2: Check folder existence

   If the images folder is not inside /about/, the link will break. This is the likely cause.

3. Final Answer:

   The relative URL points to a folder that does not exist relative to current page -> Option D

4. Quick Check:

   Relative URLs depend on current folder [OK]

Hint: Check if relative folder exists where page is located [OK]

Common Mistakes:

• Assuming relative URLs start from root without slash
• Using absolute URLs unnecessarily
• Ignoring folder structure when linking

5. You want to link to the homepage from a page at https://example.com/products/item.html. Which URL should you use to ensure the link works correctly regardless of the current page location?

hard

A. /index.html

B. index.html

C. https://example.com/index.html

D. ../index.html

Solution

1. Step 1: Understand absolute vs relative URL behavior

   Relative URLs depend on current page location, so they may break if page moves.

2. Step 2: Choose URL that works anywhere

   An absolute URL with full domain always works regardless of page location.

3. Final Answer:

   https://example.com/index.html -> Option C

4. Quick Check:

   Absolute URL works anywhere [OK]

Hint: Use full URL to avoid relative path issues [OK]

Common Mistakes:

• Using relative URLs that break if page moves
• Assuming leading slash always works for all pages
• Not including protocol and domain for absolute URLs