css-tip.com
Data from Aug 20, 2026, 8:28 PM UTC — 22h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 22h
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.
Core Web Vitals field data, origin-level
Real Chrome users, 28-day window (2026-07-22 → 2026-08-18). This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 2.41 s | — | — | 2.41 s | 2.41 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 48 ms | — | — | 48 ms | 48 ms | |
| FCP First Contentful Paint | 791 ms | — | — | 791 ms | 791 ms | |
| Speed Index | 791 ms | — | — | 791 ms | 791 ms | |
| TTFB Time to First Byte | 611 ms | — | — | 611 ms | 611 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-22 → 2026-08-18). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 1.00 s | good | 94.3% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 93 ms | good | 98.4% good |
| CLS CWV | 0 | good | 95.2% good |
| FCP | 1.00 s | good | 89.9% good |
| TTFB | 686 ms | good | 81.2% good |
Lab vs field
Lab LCP 2.41 s · field p75 1.00 s · real users are 0.41× 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 | — | — | — | — | — |
| 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 | 461.4 kB | — | — | 461.4 kB | 461.4 kB | |
| Requests | 18 | — | — | 18 | 18 | |
| Third-party Weight | 270.0 kB | — | — | 270.0 kB | 270.0 kB | |
| Third-party CPU | 60 ms | — | — | 60 ms | 60 ms | |
| Unused JS | 71.0 kB | — | — | 71.0 kB | 71.0 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 5 entities
270.0 kB transferred, 60 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 735 ms | — | — | 735 ms | 735 ms | |
| Long Tasks | 2 | — | — | 2 | 2 | |
| DOM Elements | 163 | — | — | 163 | 163 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 2 | — | — | 2 | 2 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 1 | — | — | 1 | 1 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
2 violating nodes across 2 rules, 301 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
heading-order— Heading levels should only increase by one 1 node -
critical
image-alt— Images must have alternative text 1 node
Accessibility failures 1 of 21 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.
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 20, 2026, 8:28 PM UTC | 98 | 2.41 s | 0 | 48 ms | 461.4 kB | 3/3 | ±2 | 2,348 | 25.5s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
css-tip.com'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://css-tip.com/"></speedlify-score>