alaskahikesearch.com
Data from Aug 20, 2026, 4:23 PM UTC — 26h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 26h
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-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 | 11.46 s | — | — | 11.46 s | 11.46 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 1.68 s | — | — | 1.68 s | 1.68 s | |
| Speed Index | 1.68 s | — | — | 1.68 s | 1.68 s | |
| TTFB Time to First Byte | 622 ms | — | — | 622 ms | 622 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, origin-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.03 s | good | 95.2% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 56 ms | good | 99.7% good |
| CLS CWV | 0 | good | 99.6% good |
| FCP | 787 ms | good | 94% good |
| TTFB | 501 ms | good | 88.7% good |
Lab vs field
Lab LCP 11.46 s · field p75 1.03 s · real users are 0.09× 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.02 s | 55 ms | 0 | 780 ms | 491 ms |
| 2026-08-08 | 1.02 s | 55 ms | 0 | 795 ms | 489 ms |
| 2026-08-01 | 1.07 s | 59 ms | 0 | 840 ms | 475 ms |
| 2026-07-25 | 1.11 s | 57 ms | 0 | 867 ms | 489 ms |
| 2026-07-18 | 1.11 s | 60 ms | 0 | 867 ms | 489 ms |
| 2026-07-11 | 1.08 s | 61 ms | 0 | 831 ms | 489 ms |
| 2026-07-04 | 1.08 s | 61 ms | 0 | 826 ms | 518 ms |
| 2026-06-27 | 1.08 s | 61 ms | 0 | 826 ms | 513 ms |
| 2026-06-20 | 1.07 s | 62 ms | 0 | 840 ms | 506 ms |
| 2026-06-13 | 1.07 s | 59 ms | 0 | 846 ms | 499 ms |
| 2026-06-06 | 1.03 s | 56 ms | 0 | 821 ms | 471 ms |
| 2026-05-30 | 991 ms | 55 ms | 0 | 779 ms | 441 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 1.98 MB | — | — | 1.98 MB | 1.98 MB | |
| Requests | 18 | — | — | 18 | 18 | |
| Third-party Weight | 36.8 kB | — | — | 36.8 kB | 36.8 kB | |
| Third-party CPU | 7 ms | — | — | 7 ms | 7 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 23.9 kB | — | — | 23.9 kB | 23.9 kB |
By resource type
Third parties 3 entities
36.8 kB transferred, 7 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 | 377 ms | — | — | 377 ms | 377 ms | |
| Long Tasks | 1 | — | — | 1 | 1 | |
| DOM Elements | 178 | — | — | 178 | 178 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 28 | — | — | 28 | 28 | |
| A11y Failures | 6 | — | — | 6 | 6 | |
| A11y Failing Nodes | 16 | — | — | 16 | 16 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
28 violating nodes across 8 rules, 289 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 -
critical
image-alt— Images must have alternative text 6 nodes -
serious
link-name— Links must have discernible text 6 nodes -
moderate
region— All page content should be contained by landmarks 4 nodes -
moderate
heading-order— Heading levels should only increase by one 1 node -
moderate
landmark-one-main— Document should have one main landmark 1 node -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node -
serious
link-in-text-block— Links must be distinguishable without relying on color 1 node
Accessibility failures 6 of 15 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.
-
image-alt— Image elements do not have `[alt]` attributes 6 nodes -
link-name— Links do not have a discernible name 6 nodes -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 1 node -
heading-order— Heading elements are not in a sequentially-descending order 1 node -
link-in-text-block— Links rely on color to be distinguishable. 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, 4:23 PM UTC | 74 | 11.46 s | 0 | 0 ms | 1.98 MB | 3/3 | ±1 | 2,455 | 26.7s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
alaskahikesearch.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://alaskahikesearch.com/"></speedlify-score>