Form submission basics in HTML - Performance & Optimization

Performance: Form submission basics

MEDIUM IMPACT

Form submission affects page load speed and interaction responsiveness when sending data to the server.

Submitting a form without blocking the page or causing layout shifts

HTML

<form id="myForm">
  <input type="text" name="name" required>
  <button type="submit">Send</button>
</form>
<script>
  document.getElementById('myForm').addEventListener('submit', async e => {
    e.preventDefault();
    const formData = new FormData(e.target);
    await fetch('/submit', { method: 'POST', body: formData });
    alert('Form sent without page reload!');
  });
</script>

Prevents full reload by sending data asynchronously, keeping page interactive and stable.

📈 Performance GainNon-blocking submit, improves INP by avoiding page reload delays

Submitting a form without blocking the page or causing layout shifts

HTML

<form action="/submit" method="post">
  <input type="text" name="name" required>
  <button type="submit">Send</button>
</form>

This causes a full page reload on submit, blocking rendering and resetting page state.

📉 Performance CostBlocks rendering during page reload, increases INP due to waiting for server response

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Traditional form submit (full reload)	Destroys and rebuilds entire DOM	Multiple reflows due to full page layout	High paint cost for entire page	[X] Bad
JavaScript async submit (fetch API)	No DOM rebuild, only updates needed	No reflows triggered by submit itself	Minimal paint cost, only updates if needed	[OK] Good

Rendering Pipeline

Traditional form submission triggers a full page reload, causing the browser to discard current DOM and styles, then re-parse and repaint the new page. Using JavaScript to submit forms asynchronously avoids this by keeping the current DOM and styles intact.

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Paint during full page reload

Core Web Vital Affected

INP

Form submission affects page load speed and interaction responsiveness when sending data to the server.

Optimization Tips

1Avoid full page reloads on form submit to keep interactions fast.

2Use JavaScript fetch or XMLHttpRequest for asynchronous form submission.

3Prevent default form submit behavior to control page updates and reduce layout shifts.

Performance Quiz - 3 Questions

What happens to page performance when a form submits with a full page reload?

A The page stays fully interactive without delay.

B The page blocks rendering and reloads, causing slower interaction.

C Only the form inputs are updated without reload.

D The browser caches the form data automatically.

DevTools: Performance

How to check: Record a session while submitting the form. Look for long tasks or page reload events.

What to look for: Long blocking tasks or full page reloads indicate poor performance; smooth async submit shows minimal blocking.

Practice

1. What does the action attribute in an HTML form specify?

easy

A. The type of input fields inside the form

B. The style of the form on the page

C. The method used to send the form data

D. The URL where the form data is sent after submission

Solution

1. Step 1: Understand the role of action attribute

   The action attribute tells the browser where to send the form data when the user submits the form.

2. Step 2: Differentiate from other attributes

   The method attribute controls how data is sent, not where. Styling and input types are unrelated to action.

3. Final Answer:

   The URL where the form data is sent after submission -> Option D

4. Quick Check:

   action = URL destination [OK]

Hint: Remember: action = destination URL for form data [OK]

Common Mistakes:

• Confusing action with method
• Thinking action controls form style
• Assuming action sets input types

2. Which of the following is the correct way to start a form that sends data using POST method to '/submit' URL?

easy

A.

B.

C.

D.

Solution

1. Step 1: Check attribute order and values

   Both action and method attributes are needed. The method should be 'post' and action should be '/submit'. The order of attributes does not affect correctness.

2. Step 2: Validate each option

   The <form method='post' action='submit'> has incorrect action (missing leading '/'). The <form action='/submit' method='post'> uses correct attribute names and values. The one with method='get' uses wrong method for POST. The one with method='submit' uses invalid method and action values.

3. Final Answer:

   <form action='/submit' method='post'> -> Option B

4. Quick Check:

   Correct syntax with POST method and action URL [OK]

Hint: Use for POST forms [OK]

Common Mistakes:

• Using 'submit' as method instead of 'post' or 'get'
• Mixing up method and action attribute values
• Using wrong attribute names

3. What happens when a user submits this form?

<form action='/send' method='get'>
  <input type='text' name='username' value='alice'>
  <input type='submit'>
</form>

medium

A. The form data is not sent because method is missing

B. The browser sends a POST request to '/send' with username in the body

C. The browser sends a GET request to '/send?username=alice'

D. The browser reloads the page without sending data

Solution

1. Step 1: Identify form method and action

   The form uses method='get' and action='/send', so data will be sent via URL query string to '/send'.

2. Step 2: Understand how GET sends data

   GET appends form data as key=value pairs in the URL. Here, username=alice is added to the URL.

3. Final Answer:

   The browser sends a GET request to '/send?username=alice' -> Option C

4. Quick Check:

   GET method sends data in URL [OK]

Hint: GET method sends data in URL query string [OK]

Common Mistakes:

• Thinking GET sends data in request body
• Assuming missing method means no data sent
• Confusing reload with form submission

4. Identify the error in this form code:

<form action='/submit' method='post'>
  <input type='text' name='email'>
  <input type='submit' value='Send'>
</form>

Why might this form cause accessibility issues?

medium

A. Missing <label> for the input field

B. Incorrect method attribute value

C. Submit button missing type attribute

D. Action attribute URL is invalid

Solution

1. Step 1: Check form attributes and elements

   The form uses correct action and method. The submit button has a value and defaults to type='submit'.

2. Step 2: Identify accessibility issue

   The input field lacks a <label> element, which helps screen readers and improves usability.

3. Final Answer:

   Missing <label> for the input field -> Option A

4. Quick Check:

   Labels improve accessibility [OK]

Hint: Always add <label> for inputs to help all users [OK]

Common Mistakes:

• Thinking submit button needs explicit type
• Assuming method='post' is wrong
• Believing action URL must be absolute

5. You want to create a form that sends user feedback to '/feedback' using POST. The form should have a text area labeled 'Comments' and a submit button labeled 'Send Feedback'. Which code snippet correctly implements this with accessibility and submission basics?

hard

A. \n Comments\n \n Send Feedback\n

B. \n \n \n

C. \n Comments\n \n Send Feedback\n

D. \n Comments\n \n \n

Solution

1. Step 1: Check form action and method

   The form must send data to '/feedback' using POST method. <form action='/feedback' method='post'>\n <label for='comments'>Comments</label>\n <textarea id='comments' name='comments'></textarea>\n <button type='submit'>Send Feedback</button>\n</form> and B have method='post', but B lacks label.

2. Step 2: Verify accessibility and button labeling

   <form action='/feedback' method='post'>\n <label for='comments'>Comments</label>\n <textarea id='comments' name='comments'></textarea>\n <button type='submit'>Send Feedback</button>\n</form> uses a <label> linked to the textarea with for and id, improving accessibility. The submit button is a <button> with clear text.

3. Step 3: Eliminate incorrect options

   <form action='/feedback' method='get'>\n <label>Comments</label>\n <textarea id='comments'></textarea>\n <button>Send Feedback</button>\n</form> uses GET method and missing name attribute on textarea, and label is not linked. <form action='/feedback'>\n <label for='comments'>Comments</label>\n <textarea id='comments' name='comments'></textarea>\n <input type='submit' value='Send Feedback'>\n</form> misses method attribute, so defaults to GET.

4. Final Answer:

   code snippet with proper action, method, label, and button -> Option A

5. Quick Check:

   Use POST + label + submit button for accessible form [OK]

Hint: Use label with for/id and method='post' for forms [OK]

Common Mistakes:

• Omitting method attribute defaults to GET
• Not linking label to input with for and id
• Using GET when POST is required