FAQ
Short answers on speed, hosting, and why any of this matters.
Is this the fastest website in the world?
No idea. This is an honest attempt, measured in your browser on this load. If you know a faster page, or spot a cheat, tell me. Feedback is welcome.
Does this website mean anything?
Yes. The web is where business and public information live now: money, health, news, school, work, shopping. That share keeps growing, and the technology behind it should keep getting faster too.
Speed is not a vanity metric. In a Google and Deloitte study of 37 retail and travel brands over 30 million mobile sessions, a 0.1 s load-time improvement lifted conversion by about 8–10%. Half a second is five of those steps. At site scale, that is real revenue, real readership, and real time wasted.
Most pages could be much faster than they are. This site is proof that the gap is a build choice, not a law of nature, and that we can ship technology that keeps up as the world moves forward.
How does this site stay so fast?
By keeping the first document small and honest: inlined CSS, no framework runtime in shipped HTML, system fonts, a headline that paints immediately, and proof scripts that load after first paint. Edge delivery, payload, and lab scores arrive on idle. Full list on About → How it stays fast.
Why is my second visit faster?
A service worker may cache the HTML shell and static assets after your first load, so a return visit can skip the network for much of the page. That is intentional for repeat use, not a trick on the first open. Cold loads and lab runs are still the honest comparison.
What is originless hosting?
There is no central origin server in the path that must wake up before you get the page. HTML is pre-built and served from the edge network. Cache misses and dynamic proof still run at a nearby PoP, not on a single home machine. Longer write-up on the About page.
Do all visitors hit the same server?
No. Requests land on one of many Cloudflare points of presence, often the one closest to you on the network. The PoP cell on the live board is which one answered this visit. Someone else can see a different code, RTT, and cache state. That spread is the point of edge delivery, not a bug.
Is there still “a server” somewhere?
Yes, lots of them. Originless means no single distant origin in the critical path, not “no computers.” Builds and deploys still go through Cloudflare’s platform. You just do not wait on one rack in one region for every first byte.
Where do the numbers come from?
Core Web Vitals and FCP are measured in your browser for this visit. Edge and payload cells use the nearby server that answered you, plus Navigation and Resource Timing for this load. Lab scores are static marks I update after deploys, not live third-party widgets. Field averages (when configured) appear only in the note under This visit; they do not replace the cells.
What do the “vs avg” comparisons mean?
Hints that say “vs avg” or “typical web” are ballpark baselines, not a live crawl of the whole internet and not a promise that every site hits those numbers. Paint targets (LCP ~2.5s, FCP ~1.8s, CLS 0.1, INP 200ms) follow common Core Web Vitals / “good” thresholds. Payload and edge ballparks are rounded last-mile figures I keep in the proof scripts: HTML ~100 KB, full page ~2.2 MB, ~70 requests, TTFB ~800 ms, RTT ~80 ms. Tile colors use my own good / ok cutoffs for this demo (for example TTFB under 200 ms looks strong here). If a baseline is wrong for your lab, treat the raw value as the source of truth and send a better citation.
What is the Rank page?
Why is INP blank until I tap?
Interaction to Next Paint only counts a real click, tap, or key, not mouse move, scroll, or a scripted fake event. The tile says “Click to calculate” until a value exists; the tip opens only after that. If the browser doesn’t expose Event Timing, the tile stays blank. On Chromium, if the page is this fast you may see ≤16ms, below what the API reports.
Why keep the page so light?
Weight is the product. If the internet carries more commerce and more information every year, the pages themselves should not get heavier by default. Extra chrome, webfonts, and badge networks would argue with the claim. The metrics are meant to be read, not buried under decoration.
Can the numbers look “too good”?
Sometimes. A warm cache, a close PoP, or a quiet network helps. Reload, try another network, or run your own lab test if you want a second opinion. A healthy tile means healthy for this visit, not a lifetime trophy. Comparison percents inherit the same baseline caveats as above.
I would like to get in touch
Reach out through mikkelscheike.com.