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 ·

gulpjs.com

https://gulpjs.com/

77 96 100 92 1AXE ✓CWV

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

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

Docusaurus 3.2.1 Built with Docusaurus 3.2.1
GitHub Pages Hosted by GitHub Pages

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-25 → 2026-08-21). This is what Google measures you on.

LCP 2.33 s good
INP — no data
CLS 0.080 good

Scores

77
Performance
↓ -1 (-1.3%)
96
Accessibility
no change
100
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 3.54 s 3.54 s ↑ +4 ms (+0.1%) 3.54 s 3.59 s
CLS Cumulative Layout Shift 0.107 0.107 → no change 0.107 0.107
TBT Total Blocking Time 316 ms 306 ms ↑ +10 ms (+3.3%) 218 ms 316 ms
FCP First Contentful Paint 2.43 s 2.44 s ↓ -11 ms (-0.5%) 2.43 s 2.44 s
Speed Index 2.43 s 2.44 s ↓ -11 ms (-0.5%) 2.43 s 2.44 s
TTFB Time to First Byte 608 ms 613 ms ↓ -5 ms (-0.8%) 608 ms 613 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 3.54 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 71 ms
resource load duration 20 ms
time to first byte 11 ms
resource load delay 11 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-25 → 2026-08-21). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.33 s good 80.9% good
CLS CWV 0.080 good 87.5% good
FCP 2.12 s needs-improvement 62.4% good
TTFB 1.34 s needs-improvement 49.4% good

Lab vs field

Lab LCP 3.54 s · field p75 2.33 s · real users are 0.66× faster than the lab.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 2.27 s — 0.080 2.09 s —
2026-08-08 — — 0.080 1.93 s —
2026-08-01 — — — 1.78 s —
2026-07-25 — — 0.080 2.09 s —
2026-07-18 2.15 s — 0.080 2.03 s 1.25 s
2026-07-11 2.22 s — 0.080 2.14 s 1.17 s
2026-07-04 2.22 s — 0.080 2.14 s 1.17 s
2026-06-27 2.26 s — 0.080 2.17 s 1.20 s
2026-06-20 2.30 s — 0.080 2.20 s 1.31 s
2026-06-13 2.30 s — 0.080 1.99 s 1.40 s
2026-06-06 2.11 s — 0.080 1.70 s 1.23 s
2026-05-30 1.70 s — 0.090 1.66 s —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 767 kB 767 kB ↑ +136 B 767 kB 767 kB
Requests 43 43 → no change 43 43
Third-party Weight 348 kB 348 kB ↑ +14 B 348 kB 348 kB
Third-party CPU 109 ms 111 ms ↓ -2 ms (-1.8%) 102 ms 111 ms
Unused JS 181 kB 182 kB ↓ -741 B (-0.4%) 181 kB 182 kB
Unused CSS 13.8 kB 13.8 kB → no change 13.8 kB 13.8 kB

By resource type

script 453 kB · 7 req
image 218 kB · 18 req
other 35.4 kB · 12 req
font 32.2 kB · 3 req
stylesheet 22.3 kB · 2 req
document 5.6 kB · 1 req
third party 348 kB · 8 req

Third parties 3 entities

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

Google Tag Manager 293 kB · 88 ms CPU
Google Fonts 34.1 kB · 0 ms CPU
Google Analytics 20.9 kB · 21 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.32 s 1.38 s ↓ -61 ms (-4.4%) 1.31 s 1.38 s
Long Tasks 5 5 → no change 4 5
DOM Elements 247 247 → no change 247 247
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 1 1 → no change 1 1
A11y Failures 1 1 → no change 1 1
A11y Failing Nodes 1 1 → no change 1 1

Main thread work

script evaluation 738 ms
other 243 ms
script parse compile 174 ms
style layout 119 ms
paint composite render 22 ms
parse HTML 18 ms
garbage collection 7 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 431 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 1 node

Accessibility failures 1 of 26 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. 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 77 3.54 s 0.107 316 ms 767 kB 3/3 ±17 2,474 26.4s
Aug 22, 2026, 1:10 AM UTC 78 3.54 s 0.107 306 ms 767 kB 3/3 ±14 2,497 27.3s
Aug 20, 2026, 11:30 PM UTC 80 3.59 s 0.107 218 ms 767 kB 3/3 ±1 2,453 29.2s

Embed this score

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