Laravel Vitals
Toggle theme
audit · May 25, 12:58
/products

product

mobile · Mon, May 25, 2026 12:58 PM ·
demo
Perf
B
88/100
Global
A
93/100
Performance
Lighthouse Performance score
B
-5 vs prev
Accessibility
Lighthouse Accessibility score
A
+6 vs prev
Best Practices
Lighthouse Best Practices score
A
-4 vs prev
SEO
Lighthouse SEO score
A
-1 vs prev

Core Web Vitals

LCP
Largest Contentful Paint — time until the largest visible content element is rendered. Good = under 2.5s.
1767ms
Largest Contentful Paint
CLS
Cumulative Layout Shift — how much visible content unexpectedly shifts during load. Good = under 0.1.
0.06
Cumulative Layout Shift
INP
Interaction to Next Paint — latency between user input and the next paint. Good = under 200ms.
173ms
Interaction to Next Paint
TTFB
Time to First Byte — how long the server takes to respond with the first byte. Good = under 800ms.
365ms
Time to First Byte

Front-end ↔ Back-end breakdown

LCP composition 1767ms total
backend 365ms (20.7%)
frontend 1402ms (79.3%)

Backend telemetry

Queries
20 (6 unique)
Query time
294ms
Memory peak
54.0MB
Cache hit rate
100%

Recommendations

2

performance

Enable text compression

Info
View all occurrences

Compress text-based responses with gzip or Brotli to reduce transfer size significantly.

Text-based resources (HTML, CSS, JS, JSON) compress 60-80% with gzip and even better with Brotli. Without compression every byte travels over the wire as-is, slowing FCP and LCP directly.

Typical savings: 60-80% transfer size on JS/CSS, 150-400ms LCP improvement
Recommended
# nginx — enable gzip + Brotli
gzip on;
gzip_types text/plain text/css application/javascript application/json;
gzip_min_length 1024;

# Brotli (ngx_brotli module)
brotli on;
brotli_types text/plain text/css application/javascript;
Avoid
# No gzip / Brotli block in nginx.conf
# Responses delivered uncompressed — 3-5x larger than necessary

Reduce unused JavaScript

Warning
View all occurrences

JavaScript shipped to the browser but never executed wastes bandwidth and parse time.

Unused JavaScript still costs network bandwidth, parse time, and CPU. The browser must download, parse, and compile every byte you ship — even if it never executes.

Typical savings: 30-60% bundle size, 200-500ms LCP improvement
Recommended
// Lazy-load route-specific JS
const Dashboard = () => import('./Dashboard.js');

// Or use @vite directive in Blade
@vite(['resources/js/app.js'])
Avoid
<!-- Loading the entire bundle on every page -->
<script src="/build/everything.js"></script>
Found in your application
resources/views/product.blade.php:12
<script src="/build/assets/app-abc.js"></script>
Hint: Use @vite([...]) instead.

Page details

Page weight
2,173 KB
HTTP requests
47
DOM elements
892
Render-blocking
153ms
LCP element
main > section.hero > img <img src="/images/hero.jpg" loading="eager">

Resource breakdown

Type
Count
Size
script 7 743 KB
stylesheet 2 70 KB
image 16 656 KB
font 1 91 KB
document 1 31 KB

Third-party impact

1
Entity
Transfer
Blocking
Main thread
Google Analytics 23 KB 60ms 100ms

Main thread breakdown

Slowest requests

URL
Type
Size
Duration
vendor.js
Script
371 KB
358ms
products
XHR
24 KB
361ms

Diagnostics

Critical request chain depth
2 levels
Top JS execution costs
  • app.js 201ms
  • vendor.js 148ms
Open Vitals Spotlight (Cmd+K)
Open Vitals Spotlight (Ctrl+K)
Type at least 2 characters to search
↑↓ Navigate Open
0 results