Why notifications reach users effectively in Laravel - Performance Evidence

Performance: Why notifications reach users effectively

MEDIUM IMPACT

This concept affects how quickly and reliably notifications appear to users, impacting perceived responsiveness and engagement.

Sending notifications to users without blocking the main request

Laravel

dispatch(function () use ($users, $message) { Notification::send($users, new NewMessageNotification($message)); })->delay(now()->addSeconds(1)); // queued notification

Queues notifications to send asynchronously, freeing the main request to respond faster.

📈 Performance GainNon-blocking notification sending reduces INP and improves perceived responsiveness.

Sending notifications to users without blocking the main request

Laravel

Notification::send($users, new NewMessageNotification($message)); // synchronous sending inside controller

Sends notifications synchronously during the HTTP request, blocking response and increasing wait time.

📉 Performance CostBlocks rendering and user interaction until notification sending completes, increasing INP.

Performance Comparison

Pattern	Server Processing	Response Delay	User Interaction Delay	Verdict
Synchronous notification sending	High CPU and I/O during request	Blocks response until complete	Delays user interaction	[X] Bad
Queued asynchronous notification sending	Offloaded to queue workers	Immediate response to client	Minimal delay in interaction	[OK] Good

Rendering Pipeline

Notifications sent synchronously block server response, delaying browser rendering and user interaction. Queued notifications allow the server to respond immediately, letting the browser paint and become interactive faster.

→Server Processing

→Network Response

→Browser Rendering

→User Interaction

⚠️ BottleneckServer Processing when notifications are sent synchronously

Core Web Vital Affected

INP

This concept affects how quickly and reliably notifications appear to users, impacting perceived responsiveness and engagement.

Optimization Tips

1Always queue notifications to avoid blocking HTTP responses.

2Use Laravel's built-in queue system for asynchronous notification delivery.

3Monitor request durations in DevTools to detect synchronous notification sending.

Performance Quiz - 3 Questions

What is the main performance benefit of queuing notifications in Laravel?

A It allows the server to respond faster by sending notifications asynchronously.

B It reduces the size of the notification payload.

C It improves the visual design of notifications.

D It caches notifications on the client side.

DevTools: Network

How to check: Open DevTools Network tab, observe the time taken for the notification-triggering request to complete.

What to look for: Long request duration indicates synchronous notification sending; short duration suggests asynchronous handling.

Practice

1. Why does Laravel use multiple channels like email and database for notifications?

easy

A. Because Laravel requires all notifications to be sent twice

B. To make the code more complex and harder to maintain

C. To ensure notifications reach users through their preferred method

D. To slow down the notification delivery process

Solution

1. Step 1: Understand notification channels in Laravel

   Laravel supports multiple channels like email, SMS, and database to send notifications.

2. Step 2: Reason why multiple channels are useful

   Using multiple channels ensures users get notifications in the way they prefer or can access easily.

3. Final Answer:

   To ensure notifications reach users through their preferred method -> Option C

4. Quick Check:

   Multiple channels = better delivery [OK]

Hint: Multiple channels mean better chances users see notifications [OK]

Common Mistakes:

• Thinking Laravel sends notifications twice by default
• Believing multiple channels slow down delivery
• Assuming complexity is the goal

2. Which of the following is the correct way to send a notification to a user in Laravel?

easy

A. sendNotification($user, 'InvoicePaidNotification');

B. notify($user, new InvoicePaidNotification());

C. Notification::sendUser($user, InvoicePaidNotification);

D. $user->notify(new InvoicePaidNotification());

Solution

1. Step 1: Recall Laravel notification syntax

   Laravel uses the notify method on the user model instance to send notifications.

2. Step 2: Match the correct syntax

   The correct syntax is $user->notify(new NotificationClass()); which matches $user->notify(new InvoicePaidNotification());.

3. Final Answer:

   $user->notify(new InvoicePaidNotification()); -> Option D

4. Quick Check:

   Use notify() method on user [OK]

Hint: Use $user->notify(new NotificationClass()) to send notifications [OK]

Common Mistakes:

• Using global notify() function which doesn't exist
• Calling Notification::sendUser which is invalid
• Passing notification name as string instead of object

3. Given this Laravel notification code snippet:

Notification::send($users, new InvoicePaidNotification());

What happens when this code runs?

medium

A. All users in $users receive the InvoicePaidNotification via their preferred channels

B. Only the first user in $users receives the notification

C. The code throws an error because Notification::send requires a single user

D. Notifications are queued but never sent

Solution

1. Step 1: Understand Notification::send method

   Notification::send accepts a collection or array of users and sends the notification to each.

2. Step 2: Determine behavior of sending notifications

   All users in the $users list receive the notification via their configured channels.

3. Final Answer:

   All users in $users receive the InvoicePaidNotification via their preferred channels -> Option A

4. Quick Check:

   Notification::send sends to all users [OK]

Hint: Notification::send sends to all users in the list [OK]

Common Mistakes:

• Thinking only one user gets notified
• Assuming Notification::send only accepts one user
• Believing notifications are not sent automatically

4. You wrote this code to notify a user:

$user->notify('InvoicePaidNotification');

But the notification is not sent. What is the problem?

medium

A. Notifications require a database channel to work

B. You must pass a notification object, not a string

C. You need to call notify() on Notification facade

D. The notify method only works with arrays

Solution

1. Step 1: Check notify method parameter type

   The notify method expects an instance of a notification class, not a string.

2. Step 2: Identify correct usage

   You should create a new notification object like new InvoicePaidNotification() and pass it.

3. Final Answer:

   You must pass a notification object, not a string -> Option B

4. Quick Check:

   notify() needs notification object [OK]

Hint: Pass new NotificationClass(), not string, to notify() [OK]

Common Mistakes:

• Passing notification class name as string
• Calling notify on Notification facade instead of user
• Assuming database channel is mandatory

5. You want to ensure users receive notifications even if they are offline. Which Laravel feature helps achieve this?

hard

A. Using the database notification channel to store notifications

B. Sending notifications only via email

C. Calling notify() multiple times quickly

D. Using the broadcast channel without queueing

Solution

1. Step 1: Understand offline notification delivery

   Offline users cannot receive real-time notifications but can see stored notifications later.

2. Step 2: Identify Laravel feature for offline delivery

   The database notification channel stores notifications in the database for users to view anytime.

3. Final Answer:

   Using the database notification channel to store notifications -> Option A

4. Quick Check:

   Database channel = offline notification storage [OK]

Hint: Store notifications in database for offline users [OK]

Common Mistakes:

• Thinking email alone ensures offline delivery
• Calling notify() multiple times doesn't help offline users
• Using broadcast without queue misses offline users