kula.blog
Data from Aug 21, 2026, 3:05 AM UTC 2d old
Built Awesome #865 · 1 measurement · since Aug 21, 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.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 904 ms | — | — | 904 ms | 904 ms | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 904 ms | — | — | 904 ms | 904 ms | |
| Speed Index | 904 ms | — | — | 904 ms | 904 ms | |
| TTFB Time to First Byte | 604 ms | — | — | 604 ms | 604 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 904 ms above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 336 kB | — | — | 336 kB | 336 kB | |
| Requests | 19 | — | — | 19 | 19 | |
| Third-party Weight | 313 kB | — | — | 313 kB | 313 kB | |
| 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
Third parties 2 entities
313 kB transferred, 0 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 | 223 ms | — | — | 223 ms | 223 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 291 | — | — | 291 | 291 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 71 | — | — | 71 | 71 | |
| A11y Failures | 2 | — | — | 2 | 2 | |
| A11y Failing Nodes | 66 | — | — | 66 | 66 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
71 violating nodes across 3 rules, 457 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 69 nodes -
moderate
heading-order— Heading levels should only increase by one 1 node -
moderate
region— All page content should be contained by landmarks 1 node
Accessibility failures 2 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. 65 nodes -
heading-order— Heading elements are not in a sequentially-descending order 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 21, 2026, 3:05 AM UTC | 100 | 904 ms | 0 | 0 ms | 336 kB | 3/3 | ±5 | 2,481 | 25.3s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
kula.blog'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://kula.blog/"></speedlify2-score>