About

NothingFaster.com is an attempt to make the world’s fastest website. The numbers on the live board are for this visit only. I am not claiming a crown. If you build under the same benchmark, share what you get. See the Rules. There is no form, just build.

Stack: Qwik 2 and Qwik Router (still beta), Vite 8.2, TypeScript, Cloudflare Workers, static assets, and edge cache. I author in Qwik, SSG the pages, then strip the client runtime so visitors get HTML plus a tiny proof script. Lab scores are self-hosted so the first paint does not wait on badge CDNs.

How it stays fast

The home page is the argument. These are the constraints I actually ship under — not a wish list. Longer hosting detail is under Originless hosting below.

• One HTML document on first paintStyles are minified and inlined. There is no separate stylesheet request on the home board, and no Qwik (or other framework) runtime in the HTML you receive.
• LCP-first markupThe headline paints immediately. No entrance animation hides it while the browser waits. Motion and theme polish load after first paint.
• System fonts onlyNo webfont download before text appears. If I added one, it would argue with the claim.
• Proof split and deferredCore Web Vitals run from one small deferred script. Edge delivery, payload, and lab scores load on idle — still on the same visit, not on the critical path.
• No third-party widgets on the boardNo speed-test iframes, badge CDNs, or analytics scripts before paint. Lab marks are plain HTML I control.
• Edge-static deliveryPages are pre-built at deploy time and served from nearby Cloudflare PoPs. Short same-origin APIs supply colo and cache proof without a distant origin in the path.
• Cache where it helpsHashed proof scripts are immutable. HTML gets a short edge TTL with stale-while-revalidate so warm PoPs stay fast without lying about freshness.
• Repeat visits can be warmerA small service worker caches the shell after the first load. That helps the second open feel instant; the first visit is still the fair test.

Originless hosting

Most sites still have an origin: One machine (or a small cluster) that holds the “real” copy. A CDN may sit in front, but a cache miss, a dynamic route, or a cold region still walks back to that origin. Latency becomes wherever that box lives, plus whatever it takes to wake it.

This site is originless in the practical sense: The pages are static HTML baked at build time and served from Cloudflare’s edge. There is no home server that must answer before you see the board. The Worker and asset store that hit you are already nearby on the network. The small edge APIs for colo and cache proof run there too, not on a separate origin you have to wait for.

“Originless” does not mean magic or “no computers.” It means there is no single distant source of truth in the request path. Many points of presence can answer. Which one you get depends on where you are, how DNS and anycast route you, and what is warm in cache. The PoP cell on the board is that answer for this visit, often a different code than someone on another continent sees.

A range of servers

Reload from another city, VPN, or network and the PoP label can change. Protocol, TLS, RTT, and cache HIT/MISS move with it. That is expected: the site is meant to be answered by the edge closest to you, not by one fixed rack. If the numbers look absurdly good, check the PoP and RTT. You may simply be close.

Built by Mikkel Scheike. More short answers on the FAQ.