v-model with radio buttons in Vue - Performance & Optimization

Performance: v-model with radio buttons

MEDIUM IMPACT

This affects how user input updates the UI and how Vue manages DOM updates for radio button groups.

Binding user selection to a radio button group

Vue

<template>
  <input type="radio" value="option1" v-model="selected" /> Option 1
  <input type="radio" value="option2" v-model="selected" /> Option 2
</template>
<script setup>
import { ref } from 'vue'
const selected = ref(null)
</script>

v-model automatically binds the input and updates state efficiently with minimal DOM operations.

📈 Performance GainSingle event listener per input and optimized reactive updates reduce reflows and improve INP.

Binding user selection to a radio button group

Vue

<template>
  <input type="radio" value="option1" :checked="selected === 'option1'" @change="selected = $event.target.value" /> Option 1
  <input type="radio" value="option2" :checked="selected === 'option2'" @change="selected = $event.target.value" /> Option 2
</template>
<script setup>
import { ref } from 'vue'
const selected = ref(null)
</script>

Manually handling change events causes more code and can lead to unnecessary re-renders or missed updates.

📉 Performance CostTriggers multiple event listeners and may cause extra reflows if not managed properly.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual @change handlers on each radio	Multiple event listeners	Multiple reflows if state triggers broad updates	Higher paint cost due to extra layout recalculations	[X] Bad
v-model binding on radio buttons	Single reactive binding per input	Minimal reflows limited to changed input	Lower paint cost due to targeted updates	[OK] Good

Rendering Pipeline

When a radio button changes, Vue updates the reactive state, triggering a re-render only for affected parts. The browser recalculates styles and layouts only if necessary.

→Event Handling

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout stage if many DOM nodes update unnecessarily

Core Web Vital Affected

INP

This affects how user input updates the UI and how Vue manages DOM updates for radio button groups.

Optimization Tips

1Use v-model to bind radio buttons for efficient reactive updates.

2Avoid manual event handlers that cause extra DOM operations.

3Minimize layout recalculations by limiting updates to changed inputs.

Performance Quiz - 3 Questions

Why is using v-model with radio buttons better for performance than manual @change handlers?

A v-model adds more event listeners but batches updates later.

B v-model reduces the number of event listeners and optimizes reactive updates.

C Manual handlers are faster because they avoid Vue reactivity.

D There is no performance difference between them.

DevTools: Performance

How to check: Record a performance profile while interacting with radio buttons. Look for event handler calls and layout recalculations.

What to look for: Fewer event listeners and minimal layout thrashing indicate good performance with v-model.

Practice

1. What does v-model do when used with radio buttons in Vue?

easy

A. It binds the selected radio button's value to a single data property.

B. It creates multiple independent data properties for each radio button.

C. It disables all radio buttons except the first one.

D. It automatically submits the form when a radio button is clicked.

Solution

1. Step 1: Understand v-model binding

   The v-model directive in Vue binds form inputs to a data property, syncing the input's value with the data.

2. Step 2: Apply to radio buttons

   For radio buttons, v-model binds the selected button's value to a single data property, so only one value is stored.

3. Final Answer:

   It binds the selected radio button's value to a single data property. -> Option A

4. Quick Check:

   v-model syncs selected radio value = C [OK]

Hint: v-model links one data value to all radios in a group [OK]

Common Mistakes:

• Thinking each radio has its own data property
• Assuming v-model disables radios
• Believing v-model auto-submits forms

2. Which of the following is the correct syntax to bind a radio button group with v-model to a data property named choice?

easy

A. <input type='radio' :model='choice' value='A'>

B. <input type='radio' v-bind='choice' value='A'>

C. <input type='radio' v-model='value' value='choice'>

D. <input type='radio' v-model='choice' value='A'>

Solution

1. Step 1: Identify correct directive usage

   The correct directive to bind input value to data is v-model, not v-bind or :model.

2. Step 2: Check attribute values

   The value attribute sets the radio's value, and v-model='choice' binds the selected value to the choice data property.

3. Final Answer:

   <input type='radio' v-model='choice' value='A'> -> Option D

4. Quick Check:

   Use v-model='choice' with value='A' = A [OK]

Hint: Use v-model='dataProp' and value='option' for radios [OK]

Common Mistakes:

• Using v-bind instead of v-model
• Swapping value and v-model attributes
• Using incorrect directive like :model

3. Given this Vue template snippet:

<template>
  <input type='radio' id='red' v-model='color' value='red'>
  <label for='red'>Red</label>
  <input type='radio' id='blue' v-model='color' value='blue'>
  <label for='blue'>Blue</label>
  <p>Selected color: {{ color }}</p>
</template>

If the user clicks the radio button labeled "Blue", what will be displayed inside the paragraph?

medium

A. Selected color: undefined

B. Selected color: red

C. Selected color: blue

D. Selected color: true

Solution

1. Step 1: Understand v-model behavior on radio buttons

   When a radio button is selected, its value is assigned to the bound data property, here color.

2. Step 2: Apply user action

   User clicks the radio with value='blue', so color becomes 'blue'. The paragraph shows this value.

3. Final Answer:

   Selected color: blue -> Option C

4. Quick Check:

   Click blue radio sets color = 'blue' [OK]

Hint: Selected radio's value updates bound data shown in template [OK]

Common Mistakes:

• Assuming initial value stays after click
• Confusing value attribute with label text
• Expecting boolean true instead of string value

4. Consider this Vue code snippet:

<input type='radio' v-model='selection' value='A'>
<input type='radio' v-model='selection' value='B'>
<input type='radio' v-model='selection' value='C'>

Why might none of the radio buttons appear selected even after clicking them?

medium

A. Radio buttons require a name attribute to work with v-model.

B. The data property selection is not initialized in the Vue component.

C. The v-model directive is misspelled.

D. The value attributes are missing from the radio buttons.

Solution

1. Step 1: Check data initialization

   Vue's v-model binds to a data property. If selection is undefined initially, no radio is selected by default.

2. Step 2: Understand radio selection behavior

   Clicking a radio sets selection to that value, but if the component does not react or update, it may be due to missing reactive data or errors elsewhere.

3. Final Answer:

   The data property selection is not initialized in the Vue component. -> Option B

4. Quick Check:

   Uninitialized data property causes no selection [OK]

Hint: Always initialize data properties used with v-model [OK]

Common Mistakes:

• Thinking name attribute is required for v-model radios
• Ignoring data property initialization
• Assuming misspelled v-model without checking

5. You want to create a group of radio buttons bound to selectedFruit with options 'Apple', 'Banana', and 'Cherry'. You also want the label text to be clickable for accessibility. Which of the following Vue template snippets correctly implements this?

hard

A. <div>
<label>
<input type='radio' v-model='selectedFruit' value='Apple'> Apple
</label>
<label>
<input type='radio' v-model='selectedFruit' value='Banana'> Banana
</label>
<label>
<input type='radio' v-model='selectedFruit' value='Cherry'> Cherry
</label>
</div>

B. <div>
<input type='radio' v-model='selectedFruit' value='Apple'>
<label>Apple</label>
<input type='radio' v-model='selectedFruit' value='Banana'>
<label>Banana</label>
<input type='radio' v-model='selectedFruit' value='Cherry'>
<label>Cherry</label>
</div>

C. <div>
<input type='radio' v-model='selectedFruit' value='Apple'> Apple
<input type='radio' v-model='selectedFruit' value='Banana'> Banana
<input type='radio' v-model='selectedFruit' value='Cherry'> Cherry
</div>

D. <div>
<input type='radio' id='apple' v-model='selectedFruit' value='Apple'> Apple
<input type='radio' id='banana' v-model='selectedFruit' value='Banana'> Banana
<input type='radio' id='cherry' v-model='selectedFruit' value='Cherry'> Cherry
</div>

Solution

1. Step 1: Understand label accessibility

   Wrapping the input inside a label makes the label text clickable and improves accessibility without needing for and id.

2. Step 2: Check the options

   <div>
     <label>
       <input type='radio' v-model='selectedFruit' value='Apple'> Apple
     </label>
     <label>
       <input type='radio' v-model='selectedFruit' value='Banana'> Banana
     </label>
     <label>
       <input type='radio' v-model='selectedFruit' value='Cherry'> Cherry
     </label>
   </div>

   wraps each radio input inside a label with the text, which is the recommended accessible pattern.

3. Final Answer:

   The snippet wrapping inputs inside <label> tags for clickable labels. -> Option A

4. Quick Check:

   Wrap input in label for clickable text = B [OK]

Hint: Wrap input inside label for easy clickable text [OK]

Common Mistakes:

• Using labels without for/id pairs
• Not wrapping input in label causing unclickable text
• Forgetting to bind v-model on each radio