speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

readhostel.com

https://www.readhostel.com/

93 95 100 91 CWV 79AXE

Data from Aug 21, 2026, 2:34 PM UTC — 4h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 4h

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.

Vercel Hosted by Vercel

Scores

93
Performance
no change
95
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.78 s 2.78 s 2.78 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.33 s 2.33 s 2.33 s
Speed Index 2.33 s 2.33 s 2.33 s
TTFB Time to First Byte 642 ms 642 ms 642 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.

element render delay 357 ms
time to first byte 31 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 261.0 kB 261.0 kB 261.0 kB
Requests 5 5 5
Third-party Weight 127.6 kB 127.6 kB 127.6 kB
Third-party CPU 32 ms 32 ms 32 ms
Unused JS 43.3 kB 43.3 kB 43.3 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 128.2 kB · 1 req
script 126.8 kB · 1 req
document 5.0 kB · 1 req
stylesheet 801 B · 1 req
other 273 B · 1 req
third party 127.8 kB · 3 req

Third parties 2 entities

127.6 kB transferred, 32 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

tailwindcss.com 126.8 kB · 32 ms CPU
Google Fonts 801 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 779 ms 779 ms 779 ms
Long Tasks 4 4 4
DOM Elements 154 154 154
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 79 79 79
A11y Failures 1 1 1
A11y Failing Nodes 73 73 73

Main thread work

script evaluation 401 ms
style layout 211 ms
other 95 ms
script parse compile 36 ms
garbage collection 21 ms
parse HTML 8 ms
paint composite render 7 ms

Axe violations axe-core 4.13.0, full rule set

79 violating nodes across 4 rules, 371 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 75 nodes
  • moderate region — All page content should be contained by landmarks 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node

Accessibility failures 1 of 19 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. 73 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

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 PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 21, 2026, 2:34 PM UTC 93 2.78 s 0 0 ms 261.0 kB 3/3 ±0 2,325 25.2s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show readhostel.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://www.readhostel.com/"></speedlify-score>