blog.fontawesome.com
Data from Aug 20, 2026, 7:09 PM UTC — 24h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 24h
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, url-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 | 1.36 s | — | — | 1.36 s | 1.36 s | |
| CLS Cumulative Layout Shift | 0.384 | — | — | 0.384 | 0.384 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 1.21 s | — | — | 1.21 s | 1.21 s | |
| Speed Index | 1.21 s | — | — | 1.21 s | 1.21 s | |
| TTFB Time to First Byte | 613 ms | — | — | 613 ms | 613 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, url-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 | 917 ms | good | 93.5% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 131 ms | good | 82.5% good |
| CLS CWV | 0 | good | 94.7% good |
| FCP | 930 ms | good | 89.1% good |
| TTFB | 385 ms | good | 87.4% good |
Lab vs field
Lab LCP 1.36 s · field p75 917 ms · real users are 0.67× 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 | 895 ms | 102 ms | 0 | 925 ms | 385 ms |
| 2026-08-08 | 917 ms | 140 ms | 0 | 1.03 s | 390 ms |
| 2026-08-01 | 1.06 s | 183 ms | 0 | 1.12 s | 406 ms |
| 2026-07-25 | 970 ms | — | 0 | 1.12 s | 463 ms |
| 2026-07-18 | 970 ms | — | 0 | 1.06 s | 493 ms |
| 2026-07-11 | 966 ms | 156 ms | 0.010 | 966 ms | 476 ms |
| 2026-07-04 | 966 ms | 128 ms | 0.010 | 970 ms | 487 ms |
| 2026-06-27 | 939 ms | 106 ms | 0.010 | 1.00 s | 500 ms |
| 2026-06-20 | 905 ms | 96 ms | 0.010 | 1.03 s | 500 ms |
| 2026-06-13 | 1.00 s | 115 ms | 0.010 | 1.13 s | 488 ms |
| 2026-06-06 | 991 ms | 101 ms | 0.010 | 1.04 s | 470 ms |
| 2026-05-30 | 979 ms | — | 0.010 | 979 ms | 457 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 859.6 kB | — | — | 859.6 kB | 859.6 kB | |
| Requests | 15 | — | — | 15 | 15 | |
| 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 | 380 ms | — | — | 380 ms | 380 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 307 | — | — | 307 | 307 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 0 | — | — | 0 | 0 | |
| A11y Failures | 0 | — | — | 0 | 0 | |
| A11y Failing Nodes | 0 | — | — | 0 | 0 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
0 violating nodes across 0 rules, 568 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.
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, 7:09 PM UTC | 82 | 1.36 s | 0.384 | 0 ms | 859.6 kB | 3/3 | ±18 | 2,473 | 21.7s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
blog.fontawesome.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://blog.fontawesome.com/"></speedlify-score>