Building URLs programmatically in Node.js - Performance & Optimization

Performance: Building URLs programmatically

MEDIUM IMPACT

This affects page load speed by controlling how URLs are constructed and used for resource fetching, impacting network requests and caching.

Constructing URLs with query parameters for API calls

Node.js

const url = new URL(baseUrl);
url.searchParams.set('user', userId);
url.searchParams.set('token', token);
url.searchParams.set('page', pageNumber);
const finalUrl = url.toString();

Using URL and URLSearchParams APIs ensures proper encoding and efficient construction with less CPU overhead.

📈 Performance GainReduces CPU time for string operations and avoids malformed URLs that cause network retries

Constructing URLs with query parameters for API calls

Node.js

const url = baseUrl + '?user=' + userId + '&token=' + token + '&page=' + pageNumber;

Manual string concatenation can cause errors, misses encoding, and triggers extra CPU work for string operations.

📉 Performance CostAdds CPU overhead for string concatenation and risks malformed URLs causing failed requests

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual string concatenation for URLs	0	0	0	[!] OK but error-prone and CPU costly
Using URL and URLSearchParams APIs	0	0	0	[OK] Efficient and reliable

Rendering Pipeline

URL building happens before network requests; efficient URL construction reduces CPU time and avoids delays in fetching resources, improving the critical rendering path.

→JavaScript Execution

→Network Request Initiation

⚠️ BottleneckJavaScript Execution when building URLs inefficiently

Core Web Vital Affected

LCP

This affects page load speed by controlling how URLs are constructed and used for resource fetching, impacting network requests and caching.

Optimization Tips

1Use the URL and URLSearchParams APIs to build URLs instead of manual string concatenation.

2Avoid building URLs inside tight loops to reduce CPU overhead.

3Always encode query parameters to prevent malformed URLs and failed requests.

Performance Quiz - 3 Questions

What is a performance benefit of using the URL and URLSearchParams APIs over manual string concatenation?

A They increase the size of the JavaScript bundle significantly.

B They reduce the number of network requests made.

C They automatically encode parameters, reducing errors and CPU overhead.

D They delay the network request until all parameters are set.

DevTools: Performance

How to check: Record a performance profile while your code builds URLs and initiates network requests; look for long scripting times related to string operations.

What to look for: High CPU time in JavaScript execution phase due to string concatenations indicates inefficient URL building.

Practice

1. What is the main benefit of using the URL class in Node.js when building URLs programmatically?

easy

A. It automatically encodes special characters and manages URL parts safely.

B. It allows direct string concatenation without any checks.

C. It disables query parameters to simplify URLs.

D. It only works with HTTP URLs, ignoring others.

Solution

1. Step 1: Understand the purpose of the URL class

   The URL class helps build URLs by handling encoding and structure automatically.

2. Step 2: Compare options with URL class features

   Only It automatically encodes special characters and manages URL parts safely. correctly describes automatic encoding and safe URL part management.

3. Final Answer:

   It automatically encodes special characters and manages URL parts safely. -> Option A

4. Quick Check:

   URL class = safe URL building [OK]

Hint: Remember: URL class handles encoding and structure safely [OK]

Common Mistakes:

• Thinking URL class just concatenates strings
• Assuming URL class disables query parameters
• Believing URL class only supports HTTP URLs

2. Which of the following is the correct way to create a new URL object for 'https://example.com' in Node.js?

easy

A. const url = new URL('https://example.com');

B. const url = new URL('example.com');

C. const url = URL('https://example.com');

D. const url = new URL(); url.href = 'https://example.com';

Solution

1. Step 1: Check URL constructor usage

   The URL constructor requires a full URL string including protocol, e.g., 'https://example.com'.

2. Step 2: Validate each option

   const url = new URL('https://example.com'); correctly uses new URL with full URL string. const url = new URL('example.com'); misses protocol, C misses 'new', D uses empty constructor which is invalid.

3. Final Answer:

   const url = new URL('https://example.com'); -> Option A

4. Quick Check:

   Use new URL('full-url') syntax [OK]

Hint: Always include protocol and use 'new' with URL [OK]

Common Mistakes:

• Omitting 'new' keyword
• Passing URL without protocol
• Trying to create URL without constructor

3. What will be the output of this Node.js code?

const url = new URL('https://example.com/path');
url.searchParams.append('q', 'nodejs');
url.searchParams.append('page', '2');
console.log(url.toString());

medium

A. https://example.com/path?page=2&q=nodejs

B. https://example.com/path?q=nodejs&page=2

C. https://example.com/path?q=nodejs&page=2&

D. https://example.com/path

Solution

1. Step 1: Understand searchParams.append behavior

   Appending 'q=nodejs' then 'page=2' adds these query parameters in order.

2. Step 2: Check URL string output

   Calling toString() returns full URL with query string '?q=nodejs&page=2' appended to path.

3. Final Answer:

   https://example.com/path?q=nodejs&page=2 -> Option B

4. Quick Check:

   Appended params appear in order in URL string [OK]

Hint: searchParams.append adds parameters in order [OK]

Common Mistakes:

• Assuming parameters order is reversed
• Expecting trailing '&' at end
• Ignoring appended query parameters

4. Identify the error in this code snippet that tries to add a query parameter:

const url = new URL('https://example.com');
url.searchParams.add('key', 'value');
console.log(url.href);

medium

A. The 'href' property is read-only and cannot be logged.

B. URL constructor is missing the protocol.

C. You cannot modify searchParams after URL creation.

D. The method 'add' does not exist on searchParams; should use 'append'.

Solution

1. Step 1: Check searchParams methods

   The correct method to add a query parameter is 'append', not 'add'.

2. Step 2: Validate other code parts

   URL has protocol, searchParams can be modified, and href can be logged. Only method name is wrong.

3. Final Answer:

   The method 'add' does not exist on searchParams; should use 'append'. -> Option D

4. Quick Check:

   Use searchParams.append, not add [OK]

Hint: Use 'append' to add query parameters, not 'add' [OK]

Common Mistakes:

• Using 'add' instead of 'append'
• Thinking href is not accessible
• Believing searchParams is immutable

5. You want to build a URL with base 'https://api.example.com/search' and add parameters 'query' with value 'node.js tips' and 'sort' with value 'recent'. Which code correctly builds this URL with proper encoding?

hard

A. const url = new URL('https://api.example.com/search');
url.searchParams.set('query', 'node.js tips');
url.searchParams.set('sort', 'recent');
console.log(url.toString());

B. const url = 'https://api.example.com/search?query=node.js tips&sort=recent';
console.log(url);

C. const url = new URL('https://api.example.com/search');
url.searchParams.append('query', 'node.js tips');
url.searchParams.append('sort', 'recent');
console.log(url.href);

D. const url = new URL('https://api.example.com/search');
url.searchParams.add('query', 'node.js tips');
url.searchParams.add('sort', 'recent');
console.log(url.href);

Solution

1. Step 1: Understand URL and searchParams usage

   Use new URL with base URL, then append parameters with searchParams.append to add multiple values safely.

2. Step 2: Check encoding and method correctness

   const url = new URL('https://api.example.com/search'); url.searchParams.append('query', 'node.js tips'); url.searchParams.append('sort', 'recent'); console.log(url.href); uses append correctly and prints href, which includes proper encoding of spaces as '%20'. const url = new URL('https://api.example.com/search'); url.searchParams.set('query', 'node.js tips'); url.searchParams.set('sort', 'recent'); console.log(url.toString()); uses set which replaces values but also works; however, question asks for correct code with proper encoding and append is more common for adding multiple params. const url = 'https://api.example.com/search?query=node.js tips&sort=recent'; console.log(url); is manual string and misses encoding. const url = new URL('https://api.example.com/search'); url.searchParams.add('query', 'node.js tips'); url.searchParams.add('sort', 'recent'); console.log(url.href); uses non-existent 'add' method.

3. Final Answer:

   Option C code correctly builds URL with proper encoding and appends parameters. -> Option C

4. Quick Check:

   Use URL + searchParams.append for safe, encoded URLs [OK]

Hint: Use URL and searchParams.append for safe, encoded query parameters [OK]

Common Mistakes:

• Manually concatenating query strings without encoding
• Using non-existent 'add' method
• Ignoring encoding of spaces and special characters