bitsofco.de
Data from Aug 20, 2026, 3:51 PM UTC — 27h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 27h
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-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 957 ms | — | — | 957 ms | 957 ms | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 103 ms | — | — | 103 ms | 103 ms | |
| FCP First Contentful Paint | 957 ms | — | — | 957 ms | 957 ms | |
| Speed Index | 957 ms | — | — | 957 ms | 957 ms | |
| TTFB Time to First Byte | 609 ms | — | — | 609 ms | 609 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 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 | 198.5 kB | — | — | 198.5 kB | 198.5 kB | |
| Requests | 5 | — | — | 5 | 5 | |
| Third-party Weight | 168.0 kB | — | — | 168.0 kB | 168.0 kB | |
| Third-party CPU | 52 ms | — | — | 52 ms | 52 ms | |
| Unused JS | 74.1 kB | — | — | 74.1 kB | 74.1 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 1 entities
168.0 kB transferred, 52 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 | 384 ms | — | — | 384 ms | 384 ms | |
| Long Tasks | 2 | — | — | 2 | 2 | |
| DOM Elements | 122 | — | — | 122 | 122 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 10 | — | — | 10 | 10 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 1 | — | — | 1 | 1 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
10 violating nodes across 2 rules, 197 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
region— All page content should be contained by landmarks 9 nodes -
moderate
landmark-one-main— Document should have one main landmark 1 node
Accessibility failures 1 of 17 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.
-
landmark-one-main— Document does not have a main landmark. 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, 3:51 PM UTC | 99 | 957 ms | 0 | 103 ms | 198.5 kB | 3/3 | ±0 | 2,397 | 21.5s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
bitsofco.de'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://bitsofco.de/"></speedlify-score>