What “hand-coded” actually means
When we say a site is hand-coded, we mean every line of HTML, CSS, and JavaScript on it was written specifically for your business — not pulled from a theme and then bent into shape with plugins. There’s no WordPress core, no page builder, no third-party plugin marketplace involved at all.
That sounds like a small technical distinction, but it changes almost everything about how the site performs once it’s live.
The real cost of a plugin ecosystem
A typical small-business WordPress site isn’t just WordPress. It’s WordPress, plus a page builder, plus a contact form plugin, plus an SEO plugin, plus a caching plugin, plus a security plugin, plus whatever the theme itself bundles in to make its demo look good. Each one ships its own CSS and JavaScript — and a lot of that code loads on every page, whether that page needs it or not.
It adds up fast. A simple five-page brochure site can end up shipping a couple of megabytes of code before a single photo has loaded, just from plugin overhead the visitor never sees and didn’t ask for.
Why speed is a ranking factor, not just a nice-to-have
Google has used page experience signals, collectively known as Core Web Vitals, as an official ranking factor since 2021 (more on what those actually measure in our Core Web Vitals explainer). But even setting the literal ranking algorithm aside, speed shapes behaviour: slower pages have higher bounce rates, and Google’s systems pick up on that pattern too.
A hand-coded site starts from zero instead of starting from a stack of dependencies you then have to optimise away. There’s nothing to strip out, because nothing unnecessary was added in the first place.
How to check if this actually matters for your site
You don’t need to take any of this on faith. Run your own URL through Google’s PageSpeed Insights and look at the total page weight and request count alongside the LCP score — then run a competitor’s WordPress site through the same tool. The gap in transferred kilobytes is usually the clearest evidence of where a plugin stack is costing you.
Chrome DevTools’ Network tab (open it, reload the page, sort by size) will show you exactly which files are loading and how big they are. On a typical small-business WordPress site, it’s common to see ten or more separate CSS and JS files firing before the visible content even renders — most of them from plugins doing work that page doesn’t need.
What migrating away from WordPress actually involves
The two things people worry about most are losing their content and losing their rankings, and both are manageable with the right process. Existing pages, blog posts, and images get migrated across as part of the rebuild — nothing needs to be retyped from scratch. The bigger job is making sure every old URL 301-redirects to its new equivalent, so any backlinks or bookmarks pointing at the old site still land somewhere valid instead of a 404.
Rankings typically dip slightly for one to two weeks while Google re-crawls and re-indexes the new site, then recover and usually improve past the old baseline once the speed gains kick in — assuming the content itself didn’t change and the redirects are done properly. It’s not something to do carelessly, but it’s a well-understood process, not a leap of faith.
Common WordPress speed myths
| Myth | Reality |
|---|---|
| “A caching plugin fixes it” | Caching speeds up the server response, but doesn’t remove the CSS/JS your visitor’s browser still has to download and run |
| “A premium theme is faster than a free one” | Price has nothing to do with code discipline — many premium themes ship with a page builder baked in |
| “Fixing this needs a full rebuild” | Often it’s the plugin stack, not the content, that needs replacing |
Caching plugins help. They save a pre-built version of the page instead of assembling it fresh on every request, but they don’t remove the underlying CSS and JavaScript your visitor’s browser still has to download and run. Caching speeds up the server response; it doesn’t touch the plugin bloat that’s shipped to the browser afterward.
A premium theme being faster than a free one isn’t reliably true either. Price has nothing to do with code discipline. Plenty of premium themes ship with a page builder baked in and every demo feature toggled on by default, which is the opposite of lean. The only way to know is to check the actual page weight, not the price tag or the marketing copy.
The honest trade-off
It’s not all upside. A hand-coded site can’t have a brand-new feature bolted on with a $40 plugin the way a WordPress site can — adding something genuinely new means writing it. For a lot of small businesses that’s a fair trade: you give up some last-minute flexibility in exchange for a site that’s faster, simpler to maintain, and has nothing running in the background you didn’t explicitly choose to put there.
See our custom web design page for how we build hand-coded sites for Sydney businesses. Speed is only half of local visibility — see our local SEO checklist for Sydney businesses for the rest. Weighing this against what a WordPress rebuild would actually cost? See our website cost breakdown.