01Where the time goes
New here? Start at the pillar page for the full picture.
On an uncached request, PHP runs, the database answers queries, and the page gets assembled before anything reaches the visitor. A cache plugin stores the assembled result so repeat requests skip that work. So the first fix everyone installs is a cache, which is another plugin loading on every request, and which needs purging whenever content changes. Then images get optimised, then a CDN gets added, then heavy plugins get swapped. Each step helps. Together they are a part-time job, and they only treat the generation step they exist to hide.
02The honest limit of tuning
A tuned WordPress on decent hosting can be genuinely fast. If you enjoy the tuning, that is a legitimate hobby and this page is not for you. What tuning cannot change: the first visitor after a cache purge still pays the generation cost, every plugin still loads its code into every request, and the speed work has joined the maintenance list as a permanent resident. Buying better hosting moves the same costs onto faster hardware.
03The same page, two ways
WordPress, uncached request
PHP runs. The database answers queries. The page assembles. A cache plugin stores the result, then needs purging as content changes. Repeat visits are fast if the cache is warm and maintained.
Static, every request
The server reads a file and sends it. From Australia, single-digit milliseconds before first byte. There is no cache to warm, no plugin weight, and the images are exactly as heavy as you made them.
04What the same page looks like static
05What the same page looks like static
The server reads a file and sends it. From Australia that is single-digit milliseconds before the first byte. There is nothing to cache because nothing was generated, no plugin weight because there are no plugins, and the images are exactly as heavy as you made them. Our own pages run on this stack and score in the high nineties on Lighthouse, fonts preloaded and visuals drawn as inline SVG. Speed stopped being a topic here, which is the actual benefit: not a faster site, a simpler one.
06Frequently Asked Questions
Is WordPress always slow?
No. Tuned WordPress on good hosting is fast enough for almost anything. The phrase doing the work in that sentence is tuned, present tense, forever.
Do static sites feel faster to visitors?
First visits, yes: no cache-miss penalty exists. Return visits feel the same, which is exactly where a WordPress cache stops being an advantage.
What about dynamic features?
Dynamic features are the one thing WordPress does that static cannot, and on a mostly-read site they are usually load-bearing for no one. The comparison page keeps that honest.
Will faster pages improve my rankings?
Speed is a small ranking input and a real user-experience one. The safe claim: slowness costs you, and static versus WordPress is one way to stop paying it.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.