Axios interceptors in Vue - Performance & Optimization

Performance: Axios interceptors

MEDIUM IMPACT

Axios interceptors affect the network request lifecycle and can impact interaction responsiveness and perceived loading times.

Adding global request and response handlers in Axios

Vue

axios.interceptors.request.use(config => {
  // minimal synchronous logic
  config.headers['X-Custom-Header'] = 'value';
  return config;
});

axios.interceptors.response.use(async response => {
  // async processing without blocking UI
  await someAsyncFunction(response.data);
  return response;
});

Minimal synchronous work and async handling prevent blocking the main thread, keeping UI responsive.

📈 Performance GainNon-blocking interceptors improve interaction responsiveness (INP)

Adding global request and response handlers in Axios

Vue

axios.interceptors.request.use(config => {
  // heavy synchronous logic
  for (let i = 0; i < 1000000; i++) { /* slow loop */ }
  return config;
});

axios.interceptors.response.use(response => {
  // blocking UI with synchronous processing
  const start = Date.now();
  while(Date.now() - start < 50) {}
  return response;
});

Heavy synchronous code in interceptors blocks the main thread, delaying UI updates and slowing response handling.

📉 Performance CostBlocks rendering and input responsiveness for 50+ ms per request

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy synchronous logic in interceptors	0	0	Blocks main thread causing delayed paint	[X] Bad
Light synchronous + async logic in interceptors	0	0	Non-blocking, smooth paint and interaction	[OK] Good

Rendering Pipeline

Axios interceptors run during the network request lifecycle before and after HTTP calls, affecting when data is available for rendering and user interaction.

→JavaScript Execution

→Network

→Interaction Handling

⚠️ BottleneckJavaScript Execution when interceptors run heavy synchronous code

Core Web Vital Affected

INP

Axios interceptors affect the network request lifecycle and can impact interaction responsiveness and perceived loading times.

Optimization Tips

1Avoid heavy synchronous code inside Axios interceptors to keep UI responsive.

2Use async processing in interceptors to prevent blocking the main thread.

3Keep interceptor logic minimal to reduce impact on interaction responsiveness (INP).

Performance Quiz - 3 Questions

What is the main performance risk of heavy synchronous code inside Axios interceptors?

A It causes layout shifts by changing DOM structure.

B It increases network latency by adding extra HTTP requests.

C It blocks the main thread, delaying UI updates and input responsiveness.

D It increases bundle size significantly.

DevTools: Performance

How to check: Record a performance profile while making requests with interceptors active. Look for long tasks during interceptor execution.

What to look for: Long tasks blocking main thread during request/response phases indicate heavy interceptor logic slowing interaction responsiveness.

Practice

1. What is the main purpose of Axios interceptors in a Vue application?

easy

A. To modify requests or responses globally before they reach your components

B. To create new Axios instances for each API call

C. To replace Vue lifecycle hooks with Axios methods

D. To automatically refresh the Vue component state

Solution

1. Step 1: Understand Axios interceptors role

   Axios interceptors allow you to intercept and modify requests or responses globally before they reach your Vue components.

2. Step 2: Compare options

   Options B, C, and D describe unrelated or incorrect uses of Axios interceptors.

3. Final Answer:

   To modify requests or responses globally before they reach your components -> Option A

4. Quick Check:

   Interceptor purpose = Modify requests/responses globally [OK]

Hint: Interceptors act like global filters for requests and responses [OK]

Common Mistakes:

• Thinking interceptors create new Axios instances
• Confusing interceptors with Vue lifecycle hooks
• Assuming interceptors update component state automatically

2. Which of the following is the correct syntax to add a request interceptor using Axios in Vue?

easy

A. axios.use.interceptors.request(config => { return config })

B. axios.request.interceptors.use(config => { return config })

C. axios.interceptors.request.use(config => { return config })

D. axios.interceptors.use.request(config => { return config })

Solution

1. Step 1: Recall Axios interceptor syntax

   The correct syntax to add a request interceptor is axios.interceptors.request.use(callback).

2. Step 2: Identify correct option

   Only axios.interceptors.request.use(config => { return config }) matches the correct syntax; others have incorrect property order or method calls.

3. Final Answer:

   axios.interceptors.request.use(config => { return config }) -> Option C

4. Quick Check:

   Correct syntax = axios.interceptors.request.use [OK]

Hint: Remember: interceptors.request.use is the correct chain [OK]

Common Mistakes:

• Swapping 'request' and 'interceptors' order
• Using 'use' before 'interceptors'
• Missing the return of config in the callback

3. Given this Axios response interceptor code in Vue:

axios.interceptors.response.use(response => {
  response.data.modified = true;
  return response;
});

const result = await axios.get('/api/data');
console.log(result.data.modified);

What will be logged to the console?

medium

A. undefined

B. true

C. false

D. An error will occur

Solution

1. Step 1: Analyze the response interceptor

   The interceptor adds a property 'modified' with value true to response.data before returning it.

2. Step 2: Understand the logged value

   After the GET request, result.data.modified will be true because the interceptor modified it.

3. Final Answer:

   true -> Option B

4. Quick Check:

   Interceptor modifies data = logged true [OK]

Hint: Interceptors can add properties to response data before use [OK]

Common Mistakes:

• Assuming interceptor does not modify response
• Expecting undefined because property was added dynamically
• Thinking an error occurs due to property addition

4. Identify the error in this Vue Axios interceptor code:

axios.interceptors.request.use(config => {
  config.headers['Authorization'] = 'Bearer token';
});

medium

A. Missing return of config in the interceptor callback

B. Headers should be set on response, not config

C. Authorization header value must be a function

D. Interceptor should be added on axios.request, not axios.interceptors

Solution

1. Step 1: Check interceptor callback requirements

   Axios interceptors must return the config object after modifying it to continue the request chain.

2. Step 2: Identify missing return

   The code modifies headers but does not return config, causing the request to hang or fail.

3. Final Answer:

   Missing return of config in the interceptor callback -> Option A

4. Quick Check:

   Always return config in request interceptor [OK]

Hint: Always return config or response in interceptors [OK]

Common Mistakes:

• Forgetting to return config or response
• Setting headers on response instead of request config
• Misplacing interceptor on wrong Axios property

5. You want to globally handle 401 Unauthorized errors in your Vue app using Axios interceptors. Which approach correctly implements this behavior?

hard

A. Use a response interceptor to retry the request infinitely on 401 errors

B. Use a request interceptor to modify the request URL on 401 errors

C. Use a request interceptor to add a 401 status header before sending

D. Use a response interceptor to check error response status and redirect to login

Solution

1. Step 1: Understand 401 error handling

   401 Unauthorized errors come from server responses, so handling must be in a response interceptor.

2. Step 2: Choose correct handling method

   Use a response interceptor to check error response status and redirect to login correctly uses a response interceptor to detect 401 status and redirect user to login page.

3. Step 3: Eliminate incorrect options

   Retrying infinitely causes loops; using a request interceptor cannot handle response errors like 401; adding a 401 status header in the request is invalid.

4. Final Answer:

   Use a response interceptor to check error response status and redirect to login -> Option D

5. Quick Check:

   401 errors handled in response interceptor [OK]

Hint: Handle server errors in response interceptors, not request ones [OK]

Common Mistakes:

• Trying to handle response errors in request interceptors
• Retrying requests infinitely on 401 errors
• Adding fake status headers in requests