Password reset in Laravel - Performance & Optimization

Performance: Password reset

MEDIUM IMPACT

This affects page load speed and interaction responsiveness during the password reset process, especially when rendering forms and sending reset emails.

Implementing password reset with form submission and email sending

Laravel

<?php
// Controller method
public function sendResetLinkEmail(Request $request) {
    $request->validate(['email' => 'required|email']);
    // Dispatch email sending to a queue
    Mail::to($request->email)->queue(new ResetPasswordMail($request->email));
    return back()->with('status', 'Reset link queued for sending!');
}

Using queued emails avoids blocking the HTTP response, improving interaction speed and user experience.

📈 Performance GainNon-blocking response, reduces server wait time by 500-1000ms

Implementing password reset with form submission and email sending

Laravel

<?php
// Controller method
public function sendResetLinkEmail(Request $request) {
    $request->validate(['email' => 'required|email']);
    // Directly send email synchronously
    Mail::to($request->email)->send(new ResetPasswordMail($request->email));
    return back()->with('status', 'Reset link sent!');
}

Sending email synchronously blocks the server response, causing slow page load and poor user experience.

📉 Performance CostBlocks rendering for 500-1000ms depending on mail server response

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous email sending on form submit	Minimal (simple form)	1 reflow on form render	Blocks paint until server responds	[X] Bad
Queued email sending with immediate response	Minimal (simple form)	1 reflow on form render	Paint happens immediately after response	[OK] Good

Rendering Pipeline

The password reset form rendering affects Style Calculation and Layout. Sending emails synchronously blocks server response delaying the browser's Paint and Composite stages.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckServer response blocking delays Paint and Composite stages

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness during the password reset process, especially when rendering forms and sending reset emails.

Optimization Tips

1Avoid synchronous email sending during password reset to prevent blocking server response.

2Use queued jobs for sending emails to improve interaction speed.

3Keep password reset forms simple to minimize DOM and layout costs.

Performance Quiz - 3 Questions

What is the main performance problem with sending password reset emails synchronously during form submission?

A It blocks the server response, delaying page rendering

B It increases CSS selector complexity

C It causes layout thrashing on the client side

D It adds large JavaScript bundles

DevTools: Performance

How to check: Record a performance profile while submitting the password reset form and observe the time between request start and first paint.

What to look for: Look for long tasks blocking the main thread and delayed paint events indicating synchronous email sending.