/dashboard

dashboard

desktop · Tue, May 5, 2026 12:21 PM ·

demo

Perf

100/100

Global

92/100

Performance

Lighthouse Performance score

Accessibility

Lighthouse Accessibility score

+1 vs prev

Best Practices

Lighthouse Best Practices score

-14 vs prev

SEO

Lighthouse SEO score

-2 vs prev

Core Web Vitals

LCP

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

1136ms

Largest Contentful Paint

CLS

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

0.05

Cumulative Layout Shift

INP

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

118ms

Interaction to Next Paint

TTFB

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

307ms

Time to First Byte

Front-end ↔ Back-end breakdown

LCP composition 1136ms total

backend 307ms (27%)

frontend 829ms (73%)

Backend telemetry

Queries

19 (10 unique)

Query time

220ms

Memory peak

43.0MB

Cache hit rate

87%

Recommendations

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

Lighthouse: Enable text compression web.dev: Minify and compress network payloads

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

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

972 KB

HTTP requests

DOM elements

1,017

Render-blocking

262ms

LCP element

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

Resource breakdown

Type	Count	Size
script	6	598 KB
stylesheet	4	115 KB
image	24	346 KB
font	1	62 KB
document	1	37 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	516ms
`products`	XHR	24 KB	366ms

Diagnostics

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

vendor.js 208ms