austinjavascript.com
Data from Aug 20, 2026, 3:46 PM UTC 3d old
Built Awesome #708 · 1 measurement · since Aug 20, 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 | 2.12 s | — | — | 2.12 s | 2.12 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 210 ms | — | — | 210 ms | 210 ms | |
| FCP First Contentful Paint | 1.60 s | — | — | 1.60 s | 1.60 s | |
| Speed Index | 1.60 s | — | — | 1.60 s | 1.60 s | |
| TTFB Time to First Byte | 535 ms | — | — | 535 ms | 535 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 2.12 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.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 999 kB | — | — | 999 kB | 999 kB | |
| Requests | 141 | — | — | 141 | 141 | |
| Third-party Weight | 190 kB | — | — | 190 kB | 190 kB | |
| Third-party CPU | 113 ms | — | — | 113 ms | 113 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 3 entities
190 kB transferred, 113 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 | 1.48 s | — | — | 1.48 s | 1.48 s | |
| Long Tasks | 4 | — | — | 4 | 4 | |
| DOM Elements | 483 | — | — | 483 | 483 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 1 | — | — | 1 | 1 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 1 | — | — | 1 | 1 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
1 violating node across 1 rule, 2325 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
frame-title— Frames must have an accessible name 1 node
Accessibility failures 1 of 24 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.
-
frame-title— `<frame>` or `<iframe>` elements do not have a title 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:46 PM UTC | 95 | 2.12 s | 0 | 210 ms | 999 kB | 3/3 | ±10 | 2,334 | 30.9s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
austinjavascript.com'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://austinjavascript.com/"></speedlify2-score>