Why API integration matters in Vue - Performance Evidence

Performance: Why API integration matters

HIGH IMPACT

API integration affects page load speed and interaction responsiveness by controlling how and when data is fetched and rendered.

Fetching data from an API to display in a Vue component

Vue

<script setup>
import { ref, onMounted } from 'vue';
const items = ref([]);

onMounted(async () => {
  const response = await fetch('https://api.example.com/data');
  items.value = await response.json();
});
</script>

Using async onMounted fetches data after initial render, allowing faster LCP and smoother interaction.

📈 Performance GainNon-blocking fetch improves LCP by 30-50%; reduces input delay improving INP.

Fetching data from an API to display in a Vue component

Vue

export default {
  data() {
    return { items: [] };
  },
  created() {
    const xhr = new XMLHttpRequest();
    xhr.open('GET', 'https://api.example.com/data', false);
    xhr.send();
    this.items = JSON.parse(xhr.responseText);
  }
}

Fetching data synchronously in the created hook blocks rendering until data arrives, causing slower initial paint and possible UI freeze.

📉 Performance CostBlocks rendering for 200-500ms depending on network; delays LCP and increases INP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous XHR in created hook	Multiple updates after data arrives	Triggers 2-3 reflows	High paint cost due to blocking	[X] Bad
Asynchronous fetch in onMounted with ref	Single update after data arrives	Single reflow	Low paint cost, non-blocking	[OK] Good

Rendering Pipeline

API calls fetch data asynchronously, allowing the browser to render initial UI first. When data arrives, Vue updates the DOM efficiently without full reflows.

→Network

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckNetwork latency and blocking JavaScript during synchronous fetches

Core Web Vital Affected

LCP, INP

API integration affects page load speed and interaction responsiveness by controlling how and when data is fetched and rendered.

Optimization Tips

1Always fetch API data asynchronously after initial render to avoid blocking.

2Use Vue lifecycle hooks like onMounted for data fetching to improve LCP and INP.

3Cache API responses when possible to reduce network latency and re-renders.

Performance Quiz - 3 Questions

What is the main performance benefit of fetching API data asynchronously in Vue?

A It reduces the size of the API response.

B It allows the page to render initial content faster without waiting for data.

C It eliminates the need for JavaScript execution.

D It automatically caches data on the server.

DevTools: Performance

How to check: Record a performance profile while loading the page and interacting. Look for long tasks caused by fetch blocking and JavaScript execution.

What to look for: Check for long blocking times before first paint and multiple layout recalculations after data fetch.

Practice

1. Why is API integration important in a Vue application?

easy

A. It allows the app to get and show live data from outside sources.

B. It makes the app run faster by avoiding any data fetching.

C. It removes the need for user interaction in the app.

D. It automatically styles the app without CSS.

Solution

1. Step 1: Understand API integration role

   API integration connects the app to external data or services, allowing dynamic content.

2. Step 2: Identify the benefit in Vue apps

   This connection lets the app show live or updated data, improving usefulness.

3. Final Answer:

   It allows the app to get and show live data from outside sources. -> Option A

4. Quick Check:

   API integration = live data connection [OK]

Hint: API integration means connecting to live data sources [OK]

Common Mistakes:

• Thinking API integration speeds up app without data fetching
• Believing it removes user interaction
• Confusing API integration with styling

2. Which Vue code snippet correctly fetches data from an API inside onMounted?

easy

A. onMounted(async () => { const res = await fetch('/api/data'); data.value = await res.json(); })

B. onMounted(() => { fetch('/api/data').then(res => data = res.json()) })

C. onMounted(() => { const res = fetch('/api/data'); data.value = res.json(); })

D. onMounted(async () => { data = fetch('/api/data').json() })

Solution

1. Step 1: Check async fetch usage

   onMounted(async () => { const res = await fetch('/api/data'); data.value = await res.json(); }) uses async/await correctly to wait for fetch and JSON parsing.

2. Step 2: Identify reactive assignment

   It assigns the parsed JSON to data.value, which is correct for Vue refs.

3. Final Answer:

   onMounted(async () => { const res = await fetch('/api/data'); data.value = await res.json(); }) -> Option A

4. Quick Check:

   Async fetch + await json + reactive ref = correct [OK]

Hint: Use async/await and assign to ref.value in Vue [OK]

Common Mistakes:

• Not awaiting fetch or json parsing
• Assigning directly to data without .value
• Using fetch without async/await or then properly

3. Given this Vue code, what will be the value of message after mounting?

const message = ref('');
onMounted(async () => {
  try {
    const res = await fetch('/api/greet');
    const data = await res.json();
    message.value = data.text;
  } catch {
    message.value = 'Error loading';
  }
});

Assuming the API returns { "text": "Hello Vue!" } successfully.

medium

A. "" (empty string)

B. "Error loading"

C. "Hello Vue!"

D. undefined

Solution

1. Step 1: Analyze successful fetch and JSON parse

   The API returns { "text": "Hello Vue!" }, so data.text is "Hello Vue!".

2. Step 2: Assign value to message ref

   Inside try block, message.value is set to "Hello Vue!".

3. Final Answer:

   "Hello Vue!" -> Option C

4. Quick Check:

   API success sets message = "Hello Vue!" [OK]

Hint: Try block sets message on success, catch on failure [OK]

Common Mistakes:

• Assuming catch runs on success
• Forgetting to use .value for ref
• Expecting empty string if fetch succeeds

4. What is wrong with this Vue API call code?

const data = ref(null);
onMounted(() => {
  const res = fetch('/api/items');
  data.value = res.json();
});

medium

A. ref cannot hold null values initially.

B. fetch is asynchronous but not awaited, so data.value gets a Promise.

C. res.json() is not a valid method on fetch response.

D. onMounted cannot be used for API calls.

Solution

1. Step 1: Check fetch usage

   fetch returns a Promise and must be awaited or handled with then().

2. Step 2: Identify assignment error

   Assigning res.json() without awaiting means data.value gets a Promise, not actual data.

3. Final Answer:

   fetch is asynchronous but not awaited, so data.value gets a Promise. -> Option B

4. Quick Check:

   Missing await causes Promise assignment [OK]

Hint: Always await fetch and json() to get real data [OK]

Common Mistakes:

• Not awaiting fetch or json()
• Thinking ref can't start as null
• Believing res.json() is invalid
• Misunderstanding onMounted usage

5. You want to show a loading message while fetching API data in Vue. Which approach correctly handles loading and error states?

hard

A. Use a computed property to fetch data and handle errors inside it.

B. Only fetch data without loading or error states; Vue handles it automatically.

C. Set loading to false before fetch and true after fetch completes.

D. Use refs for loading and error, set loading true before fetch, false after, and catch errors to set error message.

Solution

1. Step 1: Understand loading and error state management

   Loading should be true before fetch starts and false after it ends. Errors should be caught and stored.

2. Step 2: Identify correct Vue pattern

   Using refs for loading and error, updating them properly around async fetch, is the correct approach.

3. Final Answer:

   Use refs for loading and error, set loading true before fetch, false after, and catch errors to set error message. -> Option D

4. Quick Check:

   Manage loading and error states explicitly [OK]

Hint: Set loading true before fetch, false after; catch errors [OK]

Common Mistakes:

• Ignoring loading and error states
• Setting loading false before fetch
• Using computed for async fetch (not recommended)