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 ·

web-standards.ru

https://web-standards.ru/

100 96 100 100 4AXE ✓CWV

Data from Aug 21, 2026, 5:12 PM UTC 2d old

Built Awesome #444 · 1 measurement · since Aug 21, 2026

Core Web Vitals field data, origin-level

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

LCP 1.02 s good
INP — no data
CLS 0 good

Scores

100
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.68 s — — 1.68 s 1.68 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.08 s — — 1.08 s 1.08 s
Speed Index 1.24 s — — 1.24 s 1.24 s
TTFB Time to First Byte 783 ms — — 783 ms 783 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.68 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.

resource load duration 380 ms
time to first byte 172 ms
element render delay 65 ms
resource load delay 25 ms

Field data Chrome UX Report, origin-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.02 s good 95.3% good
CLS CWV 0 good 100% good
FCP 1.03 s good 91.6% good
TTFB 226 ms good 92.8% good

Lab vs field

Lab LCP 1.68 s · field p75 1.02 s · real users are 0.61× 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 1.03 s — 0 1.07 s 262 ms
2026-08-08 987 ms — 0 1.03 s 252 ms
2026-08-01 987 ms — 0 1.05 s 280 ms
2026-07-25 1.04 s — 0 1.06 s 299 ms
2026-07-18 1.04 s — 0 1.02 s 327 ms
2026-07-11 1.07 s — 0 1.03 s 349 ms
2026-07-04 1.08 s — 0 1.03 s 348 ms
2026-06-27 1.15 s — 0 1.05 s 364 ms
2026-06-20 1.22 s — 0 1.15 s 405 ms
2026-06-13 1.25 s — 0 1.19 s 344 ms
2026-06-06 1.24 s — 0 1.16 s 318 ms
2026-05-30 1.21 s — 0 1.18 s 278 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 177 kB — — 177 kB 177 kB
Requests 42 — — 42 42
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 85.6 kB · 7 req
image 69.0 kB · 28 req
stylesheet 10.9 kB · 2 req
document 6.5 kB · 1 req
other 3.5 kB · 3 req
script 1.6 kB · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 627 ms — — 627 ms 627 ms
Long Tasks 1 — — 1 1
DOM Elements 202 — — 202 202
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 4 — — 4 4
A11y Failures 1 — — 1 1
A11y Failing Nodes 2 — — 2 2

Main thread work

other 323 ms
style layout 196 ms
paint composite render 42 ms
script evaluation 31 ms
parse HTML 26 ms
garbage collection 6 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 1 rule, 501 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 4 nodes

Accessibility failures 1 of 23 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. 2 nodes

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 21, 2026, 5:12 PM UTC 100 1.68 s 0 0 ms 177 kB 3/3 ±0 2,426 26.3s

Embed this score

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