View transitions API in Astro - Performance & Optimization

Performance: View transitions API

MEDIUM IMPACT

This API affects the smoothness and visual stability of page transitions, improving perceived speed and reducing layout shifts.

Animating page transitions smoothly without layout shifts

Astro

document.startViewTransition(() => { document.body.innerHTML = newContent; });

The API captures the old and new states and animates between them, preventing layout shifts.

📈 Performance GainReduces CLS by animating layout changes, improving user experience

Animating page transitions smoothly without layout shifts

Astro

document.body.innerHTML = newContent; // direct DOM replacement without animation

This causes a sudden content swap triggering layout shifts and jank.

📉 Performance CostTriggers multiple reflows and a high CLS score

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct DOM swap without animation	High (full content replace)	Multiple reflows	High paint cost due to sudden changes	[X] Bad
Using View Transitions API	Moderate (batched updates)	Single reflow with animation	Lower paint cost with smooth compositing	[OK] Good

Rendering Pipeline

The View Transitions API captures snapshots of the DOM before and after changes, then animates the differences during the composite stage.

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Composite stages due to DOM changes and animation rendering

Core Web Vital Affected

CLS

This API affects the smoothness and visual stability of page transitions, improving perceived speed and reducing layout shifts.

Optimization Tips

1Avoid direct DOM swaps without animation to prevent layout shifts.

2Use View Transitions API to animate between old and new DOM states smoothly.

3Batch DOM updates inside the API callback to minimize reflows.

Performance Quiz - 3 Questions

What main Core Web Vital does the View Transitions API help improve?

A Cumulative Layout Shift (CLS)

B Largest Contentful Paint (LCP)

C Interaction to Next Paint (INP)

D Total Blocking Time (TBT)

DevTools: Performance

How to check: Record a performance profile during page transition, then look for layout shifts and composite layers.

What to look for: Lower layout shift events and smooth composite animations indicate good use of the API.

Practice

1. What is the main purpose of the startViewTransition method in the View Transitions API?

easy

A. To stop all animations on the page immediately.

B. To fetch data from a server before rendering a view.

C. To create a new HTML element dynamically.

D. To animate changes smoothly between different views or states in the UI.

Solution

1. Step 1: Understand the role of startViewTransition

   This method wraps DOM updates to animate the transition between views smoothly.

2. Step 2: Compare with other options

   Options B, C, and D describe unrelated actions like fetching data, creating elements, or stopping animations, which are not the purpose of this API.

3. Final Answer:

   To animate changes smoothly between different views or states in the UI. -> Option D

4. Quick Check:

   View Transitions = Smooth animation [OK]

Hint: Remember: startViewTransition animates view changes smoothly [OK]

Common Mistakes:

• Confusing it with data fetching methods
• Thinking it creates new elements
• Assuming it stops animations

2. Which of the following is the correct syntax to start a view transition using the View Transitions API?

easy

A. startViewTransition = updateDOM();

B. startViewTransition(() => { updateDOM(); });

C. startViewTransition.updateDOM();

D. startViewTransition[updateDOM];

Solution

1. Step 1: Recall the method signature

   The startViewTransition method takes a callback function that performs DOM updates.

2. Step 2: Check each option's syntax

   startViewTransition(() => { updateDOM(); }); correctly calls startViewTransition with a function. Options A, B, and D use invalid syntax or assignment.

3. Final Answer:

   startViewTransition(() => { updateDOM(); }); -> Option B

4. Quick Check:

   Function callback syntax = startViewTransition(() => { updateDOM(); }); [OK]

Hint: Use a function inside startViewTransition to update DOM [OK]

Common Mistakes:

• Using dot notation incorrectly
• Assigning instead of calling the function
• Using brackets instead of parentheses

3. Consider this code snippet using the View Transitions API:

startViewTransition(() => {
  document.getElementById('content').textContent = 'New content';
});
console.log(document.getElementById('content').textContent);

What will the console output show immediately after this code runs?

medium

A. Old content

B. undefined

C. New content

D. An error is thrown

Solution

1. Step 1: Understand the timing of DOM updates inside startViewTransition

   The callback inside startViewTransition runs synchronously, so the DOM textContent changes immediately.

2. Step 2: Check the console.log output

   Since the DOM is updated before the console.log runs, it prints the new content string.

3. Final Answer:

   New content -> Option C

4. Quick Check:

   DOM updates inside callback are immediate [OK]

Hint: DOM changes inside callback happen before next line runs [OK]

Common Mistakes:

• Thinking update is delayed or asynchronous
• Expecting old content to print
• Assuming an error due to API usage

4. You wrote this code but the view transition animation does not run:

startViewTransition(() => {
  const newDiv = document.createElement('div');
  newDiv.textContent = 'Hello';
});

What is the most likely reason the animation is missing?

medium

A. The new element was created but not added to the DOM.

B. startViewTransition requires an async function.

C. You must call animate() manually after updates.

D. The API only works with text content changes.

Solution

1. Step 1: Check what the callback does

   The code creates a new element but does not insert it into the page DOM.

2. Step 2: Understand animation triggers

   View transitions animate visible DOM changes. Since the new element is not added, no visible change occurs, so no animation.

3. Final Answer:

   The new element was created but not added to the DOM. -> Option A

4. Quick Check:

   Visible DOM changes trigger animation [OK]

Hint: Always add new elements to DOM inside callback for animation [OK]

Common Mistakes:

• Thinking async is required
• Believing manual animate() calls are needed
• Assuming API only works with text changes

5. You want to animate a view transition that changes the text inside a <div id='message'> only if the new text is different from the current text. Which code correctly uses the View Transitions API to do this efficiently?

hard

A. if (document.getElementById('message').textContent !== 'Hello') {
startViewTransition(() => {
document.getElementById('message').textContent = 'Hello';
});
}

B. startViewTransition(() => {
document.getElementById('message').textContent = 'Hello';
});

C. if (document.getElementById('message').textContent === 'Hello') {
startViewTransition(() => {
document.getElementById('message').textContent = 'Hello';
});
}

D. startViewTransition(async () => {
await fetch('/message');
document.getElementById('message').textContent = 'Hello';
});

Solution

1. Step 1: Check the condition to avoid unnecessary updates

   if (document.getElementById('message').textContent !== 'Hello') { startViewTransition(() => { document.getElementById('message').textContent = 'Hello'; }); } updates the text only if it differs, preventing redundant transitions.

2. Step 2: Verify the use of startViewTransition

   if (document.getElementById('message').textContent !== 'Hello') { startViewTransition(() => { document.getElementById('message').textContent = 'Hello'; }); } correctly wraps the DOM update inside the callback, enabling animation only when needed.

3. Final Answer:

   Update only if text differs, then wrap in startViewTransition callback. -> Option A

4. Quick Check:

   Conditional update + callback = if (document.getElementById('message').textContent !== 'Hello') { startViewTransition(() => { document.getElementById('message').textContent = 'Hello'; }); } [OK]

Hint: Check text difference before startViewTransition to avoid useless animations [OK]

Common Mistakes:

• Always updating without condition wastes animations
• Using async fetch inside callback unnecessarily
• Triggering transition when text is unchanged