web-standards.ru
Data from Aug 21, 2026, 5:12 PM UTC — 2h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 2h
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.
Scores
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
A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.
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 | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 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.2 kB | — | — | 177.2 kB | 177.2 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
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
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.
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 | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 21, 2026, 5:12 PM UTC | 100 | 1.68 s | 0 | 0 ms | 177.2 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 speedlify-score.js component code into your site!
<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://web-standards.ru/"></speedlify-score>