HomeWeb → Guides

Web guides

Written from operating our own servers rather than from reading someone else's post about it. Each one came from something that was wrong on our infrastructure until we measured it.

Maintained by SPELL · Cairo & worldwide
0.4msOur server response
50%Transfer we cut
2.6KBRender-blocking CSS
0Framework dependencies

The guides


Why these particular ones

Both came out of the same habit: measuring our own systems rather than assuming they were fine. The gzip problem had been costing us half our bandwidth since the server was built, and it was invisible because HTML was compressed — the half that worked concealed the half that did not.

The pattern generalises. The defects that survive longest are the ones that produce a plausible-looking result. A speed score that moves, a green tick in a dashboard, a page that loads. If you have never checked a thing directly, assume it is a coin flip.


What we are writing next

GuideThe thing that catches people
Measuring Core Web Vitals with CDPDriving real Chrome over the debugging protocol, so the numbers come from the same API Google reads.
Zero-dependency Node in productionWhat you give up, what you gain, and when a framework genuinely earns its weight.
Immutable caching without a build stepETags, stale-while-revalidate and why no-cache does not mean what most people think.

Send us a URL and we will tell you what it is shipping

Compression, caching, render-blocking assets and real Core Web Vitals — measured, with every finding attributed to the file causing it.

Book a call →

More on this