/dashboard

dashboard

mobile · Mon, May 18, 2026 12:05 PM ·

demo

Perf

96/100

Global

94/100

Performance

Lighthouse Performance score

-1 vs prev

Accessibility

Lighthouse Accessibility score

+6 vs prev

Best Practices

Lighthouse Best Practices score

-7 vs prev

SEO

Lighthouse SEO score

+3 vs prev

Core Web Vitals

LCP

Largest Contentful Paint — time until the largest visible content element is rendered. Good = under 2.5s.

1511ms

Largest Contentful Paint

CLS

Cumulative Layout Shift — how much visible content unexpectedly shifts during load. Good = under 0.1.

0.02

Cumulative Layout Shift

INP

Interaction to Next Paint — latency between user input and the next paint. Good = under 200ms.

116ms

Interaction to Next Paint

TTFB

Time to First Byte — how long the server takes to respond with the first byte. Good = under 800ms.

212ms

Time to First Byte

Front-end ↔ Back-end breakdown

LCP composition 1511ms total

frontend 1299ms (86%)

Backend telemetry

Queries

27 (10 unique)

Query time

96ms

Memory peak

32.0MB

Cache hit rate

70%

Recommendations

performance

Efficiently encode images

Info

View all occurrences

Unoptimized images contain redundant data. Compress them to improve LCP.

Unoptimized JPEG/PNG images contain metadata and redundant pixel data. Lossless or lossy compression can cut size 30-60% with no perceptible quality difference — directly improving LCP.

Typical savings: 30-70% image size, significant LCP improvement on image-heavy pages

Lighthouse: Efficiently encode images Intervention Image for Laravel

Recommended

// Intervention Image v3 — optimize on upload
use Intervention\Image\ImageManager;
use Intervention\Image\Drivers\Gd\Driver;

$manager = new ImageManager(new Driver());
$manager->read($path)
    ->toWebp(quality: 80)
    ->save(storage_path('app/public/images/hero.webp'));

Avoid

// Storing raw upload with no compression
$request->file('image')->store('images'); // may be a 4 MB JPEG

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

Lighthouse: Reduce unused JavaScript Vite: Code splitting

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/dashboard.blade.php:12

<script src="/build/assets/app-abc.js"></script>

Hint: Use @vite([...]) instead.

Page details

Page weight

1,039 KB

HTTP requests

DOM elements

858

Render-blocking

254ms

LCP element

main > section.hero > img <img src="/images/hero.jpg" loading="eager">

Resource breakdown

Type	Count	Size
script	14	627 KB
stylesheet	4	70 KB
image	8	740 KB
font	2	110 KB
document	1	15 KB

Third-party impact

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	383ms
`products`	XHR	24 KB	160ms

Diagnostics

Critical request chain depth: 3 levels
Top JS execution costs: app.js 477ms

vendor.js 188ms