hexo.io
Data from Aug 20, 2026, 11:31 PM UTC — 19h old.
Site Generators · 1 measurement · since Aug 20, 2026 · last attempt 19h
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 | 2.31 s | — | — | 2.31 s | 2.31 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 64 ms | — | — | 64 ms | 64 ms | |
| FCP First Contentful Paint | 1.85 s | — | — | 1.85 s | 1.85 s | |
| Speed Index | 1.85 s | — | — | 1.85 s | 1.85 s | |
| TTFB Time to First Byte | 633 ms | — | — | 633 ms | 633 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 | 1.41 s | good | 91.1% good |
| CLS CWV | 0 | good | 100% good |
| FCP | 1.41 s | good | 85% good |
| TTFB | 985 ms | needs-improvement | 65.4% good |
Lab vs field
Lab LCP 2.31 s · field p75 1.41 s · real users are 0.61× 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 | 1.60 s | — | 0 | 1.60 s | 1.04 s |
| 2026-08-08 | 1.68 s | — | 0 | 1.65 s | 962 ms |
| 2026-08-01 | 1.65 s | — | 0 | 1.65 s | 954 ms |
| 2026-07-25 | 1.41 s | — | 0 | 1.58 s | 944 ms |
| 2026-07-18 | 1.30 s | — | 0 | 1.38 s | 846 ms |
| 2026-07-11 | 1.30 s | — | 0 | 1.38 s | 921 ms |
| 2026-07-04 | 1.13 s | — | 0 | 1.15 s | 714 ms |
| 2026-06-27 | 1.13 s | — | 0 | 1.13 s | 738 ms |
| 2026-06-20 | 1.13 s | — | 0 | 1.13 s | 738 ms |
| 2026-06-13 | 1.07 s | — | 0 | 1.08 s | 671 ms |
| 2026-06-06 | 1.17 s | — | 0 | 1.26 s | 806 ms |
| 2026-05-30 | 1.16 s | — | 0 | 1.16 s | 740 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 861.9 kB | — | — | 861.9 kB | 861.9 kB | |
| Requests | 25 | — | — | 25 | 25 | |
| Third-party Weight | 540.0 kB | — | — | 540.0 kB | 540.0 kB | |
| Third-party CPU | 62 ms | — | — | 62 ms | 62 ms | |
| Unused JS | 101.2 kB | — | — | 101.2 kB | 101.2 kB | |
| Unused CSS | 21.9 kB | — | — | 21.9 kB | 21.9 kB |
By resource type
Third parties 5 entities
540.0 kB transferred, 62 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 | 653 ms | — | — | 653 ms | 653 ms | |
| Long Tasks | 2 | — | — | 2 | 2 | |
| DOM Elements | 173 | — | — | 173 | 173 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 19 | — | — | 19 | 19 | |
| A11y Failures | 6 | — | — | 6 | 6 | |
| A11y Failing Nodes | 10 | — | — | 10 | 10 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
19 violating nodes across 9 rules, 329 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
link-name— Links must have discernible text 5 nodes -
moderate
region— All page content should be contained by landmarks 3 nodes -
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 2 nodes -
critical
image-alt— Images must have alternative text 2 nodes -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 2 nodes -
critical
select-name— Select element must have an accessible name 2 nodes -
moderate
landmark-no-duplicate-banner— Document should not have more than one banner landmark 1 node -
moderate
landmark-one-main— Document should have one main landmark 1 node -
serious
list— <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node
Accessibility failures 6 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.
-
link-name— Links do not have a discernible name 4 nodes -
image-alt— Image elements do not have `[alt]` attributes 2 nodes -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 1 node -
list— Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 1 node -
select-name— Select elements do not have associated label elements. 1 node -
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, 11:31 PM UTC | 97 | 2.31 s | 0 | 64 ms | 861.9 kB | 3/3 | ±28 | 2,355 | 24.5s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
hexo.io'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://hexo.io/"></speedlify-score>