Let us get the honest part out of the way first. WordPress powers a huge share of the web, plenty of WordPress sites rank well, and Google does not penalize a site for the platform it is built on. Anyone who tells you otherwise is selling fear.

But that is not the setup most local businesses actually end up with. What you usually get is a heavy premium theme, a drag-and-drop page builder on top of it, a dozen or more plugins handling everything from contact forms to SEO, and cheap shared hosting underneath the whole thing. That stack is slow, fragile, and expensive to keep alive.

A custom-coded site takes the opposite approach. It ships only the code each page needs, which puts you in direct control of the exact things Google measures: speed, Core Web Vitals, clean semantic structure, and precise schema markup. That is the real argument, and it has nothing to do with penalties.

Google does not rank platforms. It ranks pages. Fast, clean pages win, and custom code makes them far easier to build.

Why do most WordPress sites end up so slow?

It is rarely WordPress core that drags. It is everything bolted on top. Page builders wrap every element on the screen in layers of extra markup. Themes load fonts, sliders, and features you never use, on every single page. Each plugin brings its own scripts and stylesheets, and most of them load whether the page needs them or not.

Stack it all up and a simple five-page contractor site is suddenly shipping megabytes of code just to render a headline, a photo, and a phone number. Put that on cheap shared hosting and the server is already slow before a single byte reaches the visitor.

A custom-coded site flips the equation. There is no builder, no theme, no plugin stack. Every line of code on the page is there because the page needs it. Nothing else ships.

Do Core Web Vitals actually affect rankings?

Yes. Core Web Vitals are the metrics Google uses to score real-world page experience: how fast the main content loads, how quickly the page responds to a tap, and whether things jump around while it loads. Google uses them as a ranking signal, and in local markets where competitors sit close together, small edges compound. Strong vitals also support everything you do in local search, because a page that loads fast and reads cleanly is easier for Google to crawl, understand, and trust.

Here is the part most owners never see: this is not a problem you can buy your way out of with a bigger agency. When we tested the portfolio sites of well-known, celebrated agencies, mobile speed scores in the 30s to 60s were common. Meanwhile, the site you are reading right now scores in the high 90s on the Google mobile PageSpeed test, because it was custom-built with performance as a requirement instead of an afterthought.

What about maintenance and security?

A typical WordPress stack needs constant babysitting. Core updates, theme updates, and a plugin list that all have to stay compatible with each other. Update one plugin and the contact form breaks. Skip the updates and you leave known holes open, because outdated plugins are one of the most common ways small business sites get hacked.

Then there is the quiet cost nobody quotes you upfront: someone has to do that maintenance forever, and you pay for it either in a monthly care plan or in a site that slowly rots.

A custom-coded site has almost no surface to attack and almost nothing to break. No plugin conflicts, no update treadmill, no third-party code you never chose. It just runs.

Do faster websites really book more jobs?

Think about how your customers actually find you. Someone has a burst pipe or a dead AC, they are on their phone, and they tap the first few results. If your site hesitates, they hit the back button and call the next company. You never even know the job existed.

Speed is not a vanity metric. It is the first link in the same chain we cover in speed to lead: the faster someone can load your page, understand what you do, and reach the call button, the more of your existing traffic turns into booked work. A website engineered to convert treats every tenth of a second and every tap as part of the sales process, not a technical detail.

Who actually owns your website?

Honesty cuts both ways here. WordPress is open source, and in theory you can pick your site up and move it anywhere. In practice, if it was assembled inside a page builder, the design lives inside that builder and its licenses. Leave, and you are usually rebuilding from scratch anyway.

Custom code deserves the same scrutiny. Before you hire anyone, ask who owns the code, where it lives, and what happens if you part ways. The right answer, on any platform, is that you own your domain, your content, and your site outright. If an agency dodges that question, keep walking.

When is WordPress actually the right call?

There are real cases where it wins. If your team publishes content daily, blog posts, photo galleries, project updates, and needs to edit all of it in-house without calling a developer, the WordPress editor earns its keep. Same story if the budget is genuinely tight and a template site this year beats a custom site someday. An honest agency tells you that instead of forcing one answer on everyone.

But most local service businesses are not media companies. The website has one job: show up in search, load instantly, and turn a visitor into a call. For that job, purpose-built code wins, and the gap shows up in rankings and booked jobs, not just in a report.

Find out what your current site is costing you

You do not have to take any of this on faith. Run your own site through the Google PageSpeed test on a phone and look at the score. If it sits deep in the yellow or red, you are losing rankings and jobs to something completely fixable.

If you want the full picture, a free audit from us looks at your speed, your rankings, and where visitors leak out before they ever call. You will know exactly what the site you already pay for is doing to you, and what a purpose-built one would change.