Caching API responses in Astro - Performance & Optimization

Performance: Caching API responses

HIGH IMPACT

Caching API responses improves page load speed by reducing network requests and speeds up rendering by serving stored data quickly.

Fetching data for a page that rarely changes

Astro

import { cache } from 'astro:cache';
const data = await cache(async () => {
  const response = await fetch('https://api.example.com/data');
  return await response.json();
}, { ttl: 3600 });
return data;

Caches the API response for 1 hour, serving stored data instantly on repeat visits.

📈 Performance GainReduces network requests to zero during cache lifetime, cutting load blocking by 200-500ms

Fetching data for a page that rarely changes

Astro

const response = await fetch('https://api.example.com/data');
const data = await response.json();
return data;

Fetches fresh data on every page load causing repeated network delays and slower rendering.

📉 Performance CostBlocks rendering for 200-500ms per request depending on network speed

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No caching, fetch on every load	Minimal	1 per data update	Moderate due to delayed content	[X] Bad
Caching API responses with TTL	Minimal	1 on cache miss	Low due to instant data	[OK] Good

Rendering Pipeline

Without caching, the browser waits for the network response before rendering content, delaying Style Calculation and Layout. With caching, data is available immediately, allowing faster Style Calculation and Layout.

→Network

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork latency delays initial data availability, blocking rendering

Core Web Vital Affected

LCP

Caching API responses improves page load speed by reducing network requests and speeds up rendering by serving stored data quickly.

Optimization Tips

1Cache API responses to reduce network latency and speed up page load.

2Set a reasonable TTL to balance freshness and performance.

3Use Astro's built-in cache utilities to simplify caching implementation.

Performance Quiz - 3 Questions

What is the main performance benefit of caching API responses in Astro?

A Triggers more reflows during rendering

B Increases bundle size significantly

C Reduces network requests and speeds up page load

D Blocks rendering longer due to cache checks

DevTools: Network

How to check: Open DevTools > Network tab, reload page, observe API request timing and frequency. Then enable caching and reload again to see reduced or no requests.

What to look for: Fewer or no repeated API requests and faster document load times indicate effective caching.

Practice

1. What is the main benefit of caching API responses in Astro?

easy

A. It speeds up the site by reusing previously fetched data

B. It increases the size of the API response

C. It makes the API slower to respond

D. It disables the API from updating

Solution

1. Step 1: Understand caching purpose

   Caching stores data from previous API calls to avoid fetching again.

2. Step 2: Identify benefit in Astro context

   Reusing cached data reduces load time and speeds up the site.

3. Final Answer:

   It speeds up the site by reusing previously fetched data -> Option A

4. Quick Check:

   Caching = Speed up site [OK]

Hint: Caching saves time by reusing data, not slowing down [OK]

Common Mistakes:

• Thinking caching makes API slower
• Confusing cache with data size increase
• Believing cache disables updates

2. Which syntax correctly sets cache revalidation time in Astro?

easy

A. const data = await fetch('https://api.example.com/data', { refresh: 60 });

B. const data = await fetch('https://api.example.com/data', { cacheTime: 60 });

C. const data = await fetch('https://api.example.com/data', { revalidate: 60 });

D. const data = await fetch('https://api.example.com/data', { updateAfter: 60 });

Solution

1. Step 1: Recall correct property name

   The correct property to control cache duration is revalidate.

2. Step 2: Match syntax with Astro docs

   The syntax uses { revalidate: 60 } inside fetch().

3. Final Answer:

   const data = await fetch('https://api.example.com/data', { revalidate: 60 }); -> Option C

4. Quick Check:

   Use revalidate property = const data = await fetch('https://api.example.com/data', { revalidate: 60 }); [OK]

Hint: Remember 'revalidate' sets cache time in seconds [OK]

Common Mistakes:

• Using wrong property names like cacheTime or refresh
• Forgetting to return an object
• Placing revalidate outside return

3. Given this code snippet in Astro:

const data = await fetch('https://api.example.com/data', { revalidate: 120 }).then(res => res.json());

What happens when a user visits the page after 3 minutes?

medium

A. The cached data is used without fetching again

B. The cache is cleared but data is not fetched

C. The page shows an error due to cache expiry

D. The data is fetched again from the API

Solution

1. Step 1: Understand revalidate timing

   The revalidate: 120 means cache lasts 120 seconds (2 minutes).

2. Step 2: Compare visit time with cache duration

   After 3 minutes (180 seconds), cache expired, so Astro fetches fresh data.

3. Final Answer:

   The data is fetched again from the API -> Option D

4. Quick Check:

   Cache expired after 120s, fetch again [OK]

Hint: If visit time > revalidate, data refetches [OK]

Common Mistakes:

• Assuming cache lasts forever
• Thinking cache clears but no fetch happens
• Confusing cache expiry with errors

4. Identify the error in this Astro caching code:

const data = await fetch('https://api.example.com/data').json();

medium

A. Missing await before .json() call

B. Incorrect property name 'revalidate'

C. fetch URL is invalid

D. Return statement missing props object

Solution

1. Step 1: Check fetch usage

   fetch returns a Promise; calling .json() needs to await the fetch first.

2. Step 2: Identify missing await

   Code calls fetch(...).json() without awaiting fetch, causing error.

3. Final Answer:

   Missing await before .json() call -> Option A

4. Quick Check:

   Await fetch before .json() [OK]

Hint: Always await fetch before calling .json() [OK]

Common Mistakes:

• Calling .json() directly on fetch without await
• Misnaming revalidate property
• Assuming fetch URL is wrong without checking

5. You want to cache API data in Astro but update it every hour. Which is the best way to set revalidate and why?

Options:
A) revalidate: 3600 to update every hour
B) revalidate: 60 to update every minute
C) revalidate: 0 to never cache
D) revalidate: -1 to disable caching

hard

A. revalidate: 60 to update every minute

B. revalidate: 3600 to update every hour

C. revalidate: 0 to never cache

D. revalidate: -1 to disable caching

Solution

1. Step 1: Understand revalidate meaning

   revalidate sets cache duration in seconds before refreshing data.

2. Step 2: Match desired update frequency

   To update every hour, set revalidate to 3600 seconds (60*60).

3. Step 3: Evaluate other options

   60 seconds updates too often, 0 disables caching, -1 is invalid.

4. Final Answer:

   revalidate: 3600 to update every hour -> Option B

5. Quick Check:

   1 hour = 3600 seconds revalidate [OK]

Hint: Set revalidate in seconds matching update frequency [OK]

Common Mistakes:

• Using too short revalidate causing frequent fetches
• Setting zero disables caching, not hourly update
• Negative values are invalid