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 ·

gruntjs.com

https://gruntjs.com/

100 73 96 92 29AXE CWV

Data from Aug 23, 2026, 1:16 AM UTC 21h old

Test Runners #7 · 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.

Cloudflare Hosted by Cloudflare

Scores

100
Performance
no change
73
Accessibility
no change
96
Best Practices
no change
92
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 1.36 s 1.37 s ↓ -12 ms (-0.9%) 1.36 s 1.37 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 0 ms 0 ms → no change 0 ms 0 ms
FCP First Contentful Paint 1.06 s 1.07 s ↓ -12 ms (-1.1%) 1.06 s 1.07 s
Speed Index 1.06 s 1.07 s ↓ -12 ms (-1.1%) 1.06 s 1.07 s
TTFB Time to First Byte 611 ms 623 ms ↓ -12 ms (-1.9%) 611 ms 623 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 1.36 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 82 ms
time to first byte 13 ms

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15
2026-08-08
2026-08-01
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27
2026-06-20
2026-06-13
2026-06-06
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 101 kB 101 kB ↓ -349 B (-0.3%) 101 kB 101 kB
Requests 24 24 → no change 24 24
Third-party Weight 0 B 0 B → no change 0 B 0 B
Third-party CPU 0 ms 0 ms → no change 0 ms 0 ms
Unused JS 0 B 0 B → no change 0 B 0 B
Unused CSS 12.7 kB 12.7 kB → no change 12.7 kB 12.7 kB

By resource type

image 76.6 kB · 19 req
stylesheet 14.7 kB · 1 req
document 3.2 kB · 1 req
font 2.9 kB · 1 req
other 294 B · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 353 ms 454 ms ↓ -101 ms (-22.2%) 328 ms 454 ms
Long Tasks 0 0 → no change 0 0
DOM Elements 185 185 → no change 185 185
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 29 29 → no change 29 29
A11y Failures 4 4 → no change 4 4
A11y Failing Nodes 28 28 → no change 28 28

Main thread work

other 180 ms
style layout 132 ms
paint composite render 18 ms
parse HTML 13 ms
script evaluation 9 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

29 violating nodes across 6 rules, 362 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.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 15 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 8 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious link-name — Links must have discernible text 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 4 of 14 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 15 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 11 nodes
  • link-name — Links do not have a discernible name 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:16 AM UTC 100 1.36 s 0 0 ms 101 kB 3/3 ±0 2,427 22.7s
Aug 22, 2026, 1:09 AM UTC 100 1.37 s 0 0 ms 101 kB 3/3 ±0 2,472 26.3s
Aug 20, 2026, 11:29 PM UTC 100 1.36 s 0 0 ms 101 kB 3/3 ±0 2,423 21.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show gruntjs.com'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://gruntjs.com/"></speedlify2-score>