riafin.com
Data from Aug 21, 2026, 5:40 AM UTC — 13h old.
11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 13h
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 | 3.86 s | — | — | 3.86 s | 3.86 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 610 ms | — | — | 610 ms | 610 ms | |
| FCP First Contentful Paint | 2.73 s | — | — | 2.73 s | 2.73 s | |
| Speed Index | 4.69 s | — | — | 4.69 s | 4.69 s | |
| TTFB Time to First Byte | 714 ms | — | — | 714 ms | 714 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 | 416.0 kB | — | — | 416.0 kB | 416.0 kB | |
| Requests | 18 | — | — | 18 | 18 | |
| Third-party Weight | 49.7 kB | — | — | 49.7 kB | 49.7 kB | |
| Third-party CPU | 0 ms | — | — | 0 ms | 0 ms | |
| Unused JS | 30.1 kB | — | — | 30.1 kB | 30.1 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 1 entities
49.7 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 | 9.05 s | — | — | 9.05 s | 9.05 s | |
| Long Tasks | 20 | — | — | 20 | 20 | |
| DOM Elements | 608 | — | — | 608 | 608 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 9 | — | — | 9 | 9 | |
| A11y Failures | 3 | — | — | 3 | 3 | |
| A11y Failing Nodes | 10 | — | — | 10 | 10 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
9 violating nodes across 2 rules, 1039 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 8 nodes -
moderate
heading-order— Heading levels should only increase by one 1 node
Accessibility failures 3 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. 8 nodes -
button-name— Buttons do not have an accessible name 1 node -
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, 5:40 AM UTC | 66 | 3.86 s | 0 | 610 ms | 416.0 kB | 3/3 | ±8 | 2,350 | 31.9s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
riafin.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://riafin.com/"></speedlify-score>