speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

gridsome.org

https://gridsome.org/

69 97 100 91 37AXE –CWV

Data from Aug 23, 2026, 1:15 AM UTC 20h old

Site Generators #14 · 3 measurements · since Aug 20, 2026

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Gridsome 0.7.20 Built with Gridsome 0.7.20
Netlify Hosted by Netlify

Scores

69
Performance
↓ -6 (-8%)
97
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.33 s 6.25 s ↓ -917 ms (-14.7%) 5.33 s 6.25 s
CLS Cumulative Layout Shift 0.158 0.060 ↑ +0.098 (+163.3%) significant 0.060 0.158
TBT Total Blocking Time 235 ms 175 ms ↑ +60 ms (+34.3%) 175 ms 235 ms
FCP First Contentful Paint 1.20 s 1.14 s ↑ +55 ms (+4.8%) 1.14 s 1.83 s
Speed Index 1.20 s 1.14 s ↑ +55 ms (+4.8%) 1.14 s 1.83 s
TTFB Time to First Byte 609 ms 625 ms ↓ -16 ms (-2.6%) 609 ms 625 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 5.33 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 402 ms
time to first byte 15 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.24 MB 1.24 MB ↓ -1.4 kB (-0.1%) 1.24 MB 1.24 MB
Requests 120 120 → no change 120 120
Third-party Weight 181 kB 181 kB ↑ +14 B 181 kB 181 kB
Third-party CPU 44 ms 57 ms ↓ -13 ms (-22.6%) 44 ms 57 ms
Unused JS 172 kB 173 kB ↓ -701 B (-0.4%) 172 kB 174 kB
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

other 691 kB · 99 req
script 341 kB · 4 req
font 144 kB · 4 req
document 50.8 kB · 1 req
stylesheet 14.0 kB · 1 req
third party 181 kB · 3 req

Third parties 2 entities

181 kB transferred, 44 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Tag Manager 160 kB · 40 ms CPU
Google Analytics 20.9 kB · 4 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 2.13 s 2.16 s ↓ -30 ms (-1.4%) 2.13 s 2.19 s
Long Tasks 6 5 ↑ +1 (+20%) 5 7
DOM Elements 512 512 → no change 512 512
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 37 37 → no change 37 37
A11y Failures 2 2 → no change 2 2
A11y Failing Nodes 2 2 → no change 2 2

Main thread work

other 726 ms
script evaluation 556 ms
style layout 460 ms
paint composite render 187 ms
script parse compile 156 ms
parse HTML 48 ms

Axe violations axe-core 4.13.0, full rule set

37 violating nodes across 5 rules, 760 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • moderate region — All page content should be contained by landmarks 33 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • serious label-title-only — Form elements should have a visible label 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 2 of 27 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 23, 2026, 1:15 AM UTC 69 5.33 s 0.158 235 ms 1.24 MB 3/3 ±7 2,363 30.2s
Aug 22, 2026, 1:10 AM UTC 75 6.25 s 0.060 175 ms 1.24 MB 3/3 ±18 2,334 30.6s
Aug 20, 2026, 11:35 PM UTC 75 5.57 s 0.061 199 ms 1.24 MB 3/3 ±23 2,335 29.7s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show gridsome.org's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://gridsome.org/"></speedlify2-score>