With
MeasuredThis page · under stress
- Received
- 0.0 KB
- Requests
- 1
- First words2.2 s
- Largest element2.2 s
- Finished2.8 s
Performance by design
Speed is not a plugin added at the end. On our new system it is decided in advance: pages assembled before anyone visits and kept close to whoever asks, images cut to the screen they land on, video that waits its turn, JavaScript only where someone touches. This page shows the machinery, then measures itself on your device.
Ready in 0.4 s. Normal connection · measured live · 2026‑11‑12
The figures come from this site and others built on our new system, measured where marked, with the date and the method. Diagrams are illustrative where marked.
01 · The difference
On a normal connection, this very page is ready in a fraction of a second. Here it is under stress, on a slowed processor over a slow connection, beside the same page without the strategy: photos at full size, fonts from an outside host, all of its code up front.
This page · under stress
This page · under stress, strategy removed
The same page loads twice on one clock, with the strategy and without it.
Normal connection · measured live
Whole page · desktop · read to the end
Stress test
Normal connection: live, cold cache, median of 9 runs, 2026‑11‑12. Stress test: lab, 2026‑11‑12, cold cache, CPU slowed ×4, 150 ms, 1.6 Mbps; “Without” is modelled.
An automated Chromium, on a phone-class lab profile: the standard yardstick for comparing loads like for like. Viewport 412×915 at 2.625×, CPU slowed ×4, 150 ms latency, 1.6 Mbps down and 750 kbps up, cache disabled. Three runs; the run with the median largest paint is the one shown. The page is this one, as it is served live, through that simulated connection: the first byte recorded is the real answer plus the simulated latency. Full weight and request counts come from an unthrottled desktop load of the same page, read to the bottom, the same day. “Ready” is the moment the largest element has painted: here that is the opening’s text, which paints with the first words. The clock runs to scale from start to finish. The normal-connection figures are a separate reading: this page as it is served live, in a desktop Chromium at 1440×900 with nothing slowed, a fresh browser and an empty cache for each of nine runs, from the studio’s own connection; the run with the median largest paint is the one shown.
The “without” lane is not a second measurement. It is this same page, with four strategies stripped out one at a time and each one’s real cost added back from parts of this site we did measure.
| Checkpoint | Time | Received |
|---|---|---|
| First byte | 255 ms | — |
| First words (FCP) | 2.2 s | 296 KB |
| Largest element (LCP) | 2.2 s | 296 KB |
| DOM ready | 2.3 s | 308 KB |
| Finished loading | 2.8 s | 439 KB |
| Checkpoint | Time | Received |
|---|---|---|
| First byte | 255 ms | — |
| First words (FCP) | 2.7 s | 358 KB |
| Largest element (LCP) | 2.7 s | 358 KB |
| DOM ready | 2.7 s | 358 KB |
| Finished loading | 4.3 s | 706 KB |
02 · Rendering
WordPress stays where your team writes, never where visitors wait. Each page is assembled ahead of time and kept at the edge of the network; a saved change is rebuilt in the background.
Where your team writes
Waiting for a visitElapsed0 ms
The site, pre-rendered
Bypassed by every visit
Near whoever asks
Bypassed by every visit
0Visitors sent
A typical WordPress site. Every visit travels all the way to WordPress.
| Pattern | Last answer | Reached WordPress |
|---|---|---|
| Typical WordPress | — | — |
| Our new system | — | — |
Measured 2026-09-28: 10/10 repeat requests answered HIT on 5 sites built on our new system · first byte ~131 ms
The visitor, the request and the rebuild are drawn at a readable pace, not to a stopwatch. The typical site’s timer counts that drawing, not a measurement of any real site.
Measured from one machine, one request at a time, a second apart, three visits to each of 5 sites built on our new system. 10 of 10 repeat requests were answered from the edge cache (a HIT in the response’s cache header); of the 5 first requests, 4 were, and one was STALE, a refresh already due. The first byte is the wait once the connection is open, the median of 14 HIT answers, ~131 ms, so it measures the site and not this network.
Documented On one of our shop sites, all 14 dynamic routes are such endpoints. No content page is dynamic.
03 · Images
A photo arrives huge, with the camera’s notes inside. We strip what is private, cap what is excessive and let each screen fetch the size it actually paints.
01 · One photo, three cutsBar: what is left of the original’s weight

The original
3,200 × 2,133 px
JPEG
4.96 MB
Strip
25 KB of camera notes inside25 KB of camera notes removed
4.96 MB4.94 MB
−0.5%Cap
3,200 px wide3,200 → 2,400 px
4.94 MB245 KB
−95%Encode
JPEGJPEG → WebP, same pixels
245 KB90 KB
−63%Every figure is measured on this photo: its licensed original, then this page’s own image optimizer.
04 · Video
Every loop is cut in our own tool, the Looper: shorter, lighter, silent, index first. On the page it is fetched only when it is about to be seen, and it pauses when you scroll past.
A real loop from this site, before the Looper touches it: the raw clip.
Weight at each step: Before 5.01 MB, Trim 2.10 MB, Boomerang 3.91 MB, Size 2.75 MB, Silence 2.75 MB, Index first 2.75 MB, Encode 444 KB.
A film wakes one screen ahead, plays while on screen and pauses once passed.
Published file, weighed as servedReproduced step, our own re-encode
A. Before and After are the two published files, weighed as served and read for their frame size, rate, length and audio. The index position comes from each file’s top-level atoms: in both, the index sits before the media (bytes 32–3,693 of the source, 32–2,323 of the result). The five steps between are our own re-encode of the same edits, since the Looper keeps no intermediate exports. The bar rises at Boomerang because the length doubles; nothing is smoothed away.
B. The page is a drawing; the sizes are real: Forest lake 776 KB, Blue motes 1.19 MB, Violet smoke 356 KB, still 49.8 KB. All three loops are set up like the forest-lake band on the home page: a still for every device, the film on screens 1,081 px wide and up, never on a connection that saves data. Other loops on the site use other settings. “At load” is what the drawn page fetches before any scrolling: nothing, since no loop lies within a screen of the first one. “Without the strategy” is the three films added together, all fetched up front.
05 · JavaScript
Words and pictures need no JavaScript to appear. The interactive parts of this site arrive on their own, the moment someone reaches for them.
Whole first visit: 503 KB in 35 requests
239 KB
319 KB
Computedof code. The whole first visit: 503 KB.
of code on every page, 1.3× as much.
The code of the menu’s drawings up front, for every visitor.
A visitor reads this page. Nothing asked yet.
Fetched ahead while idle: nothing. The pages behind the header and the menu wait for a hover or a focus.
Live page · desktop Chromium · cache off · 2026-11-12 · “Without the strategy” computed
Each figure is what the browser received on the wire, headers and body, for one first visit to this page as it is served live: desktop Chromium at 1440 × 900, no throttling, nothing cached, nobody signed in, nothing scrolled, the mouse not moved; three runs, the middle one kept. The column counts this page’s own requests only.
What this page weighs: HTML: 48 KB; CSS: 105 KB; Fonts: 106 KB; Images: 5.2 KB; Code: 239 KB; Arrives with this page: 239 KB; Without the strategy: 319 KB; On request · not in the first visit: 0 KB.
06 · The proof
Not our lab this time: yours. Your browser keeps a record of how this page loaded and how quickly it answers you. Here it is, against Google’s thresholds.
Waiting
Waiting
The practice
Two sites on the same stack can be seconds apart. The difference is rarely the framework. It is the hero photo left at full size, the request that skips the cache, the loop that plays off screen. We write those decisions down, check them on real devices, and keep them after launch.
What this page shows is our new system, the way we build today. Sites we delivered before it may not include it.
Send us your address. We will measure it the way we measure ours.