WordPress vs custom PHP, and the question that actually matters

Tuan Nguyen·April 22, 2026

The WordPress versus custom debate is usually framed as a speed contest. The real variable is accumulation, and the right question is not which loads faster but who maintains the site in a year.

The question usually arrives already framed as a speed contest. WordPress is slow, custom is fast, which one should I build on.

That framing is wrong in a way that costs people money, because the platform is not really the variable. Accumulation is.

A fresh WordPress install on decent hosting is quick. Nobody has a performance problem on day one. The problem arrives eighteen months later, after a form builder, an SEO plugin, a slider, a cookie banner, a booking widget, and two things nobody remembers installing have each added their own scripts and database queries to every page load. That is not WordPress being slow. That is thirteen separate pieces of software running on one page because each one solved a problem on the afternoon it was installed.

First, the metric everyone is still quoting is gone

If your developer or your last audit talked about FID, that advice is out of date.

Google retired First Input Delay in March 2024 and replaced it with Interaction to Next Paint. FID only measured the delay before the browser started responding to your first tap. INP measures how long the whole interaction takes to produce a visible result, across the entire visit. It is a much harder test, and plenty of sites that passed comfortably on FID fail on INP.

The three Core Web Vitals now are LCP for loading, INP for responsiveness, and CLS for visual stability. The thresholds Google considers good are 2.5 seconds, 200 milliseconds, and 0.1.

Worth being honest about the ranking side too, because it gets oversold. Core Web Vitals have been part of ranking since the 2021 page experience update, and Google has been consistent that they act as a tiebreaker rather than a dominant factor. A fast page about nothing will not outrank a slow page that answers the question. Speed decides between two pages that both deserve to be there.

Which is exactly the position most local businesses are in.

Where the time actually goes

Every plugin that touches the front end tends to load its own CSS and JavaScript on every page, whether that page uses it or not. Your contact form plugin loads its scripts on your about page. Your slider loads on pages with no slider.

That mostly hurts INP rather than LCP, and INP is the one people are not watching. More JavaScript means a busier main thread, and a busy main thread means the tap on your booking button sits there for a moment doing nothing visible. On a mid range Android phone, which is what a lot of your customers are actually holding, that moment stretches.

A custom build avoids this by construction rather than by discipline. There is no plugin ecosystem to accumulate, so the page loads what the page needs. That is the whole advantage, and it is a real one, but notice it is an advantage about restraint rather than about PHP being faster than PHP.

What it costs to own, not to build

WordPress is cheaper to start. Hosting runs roughly five to fifteen dollars a month, the build is fast, and a small site can sit comfortably in the low hundreds per year.

The cost that does not appear on the quote is attention. Plugins update, occasionally conflict, and periodically break something at an inconvenient moment. Someone has to notice and fix it. If that someone is you, it is not free, it is just unbilled.

A custom build asks for more upfront and less afterwards. Higher initial cost, similar or slightly higher hosting, and maintenance that is more predictable because there is no third party code updating itself underneath you. Fewer moving parts, fewer surprises.

WordPress is cheaper to buy. Custom is often cheaper to own. Which matters more depends entirely on how long you intend to keep the site.

When WordPress is clearly the right answer

I would not talk most small businesses out of WordPress, and it is worth saying that plainly on an agency website.

If you publish regularly and want to edit your own pages without calling anyone, the dashboard is genuinely valuable and a custom build takes that away. If you need to launch soon, WordPress launches sooner. If your site is small and stays small, the plugin accumulation problem never really arrives.

And a disciplined WordPress site performs fine. The catch is that discipline has to be ongoing, because one plugin update can undo a month of tuning, and the same accumulation that slows a site down is also what makes it easier to break into. Speed and security are the same problem viewed from two angles.

The question to actually ask

Not which is faster. Ask who maintains this in a year.

If the answer is you, in an evening, between customers, then WordPress with a deliberately short plugin list is the honest choice, and the job is keeping that list short. If the answer is a developer you already work with, custom removes a category of problem you would otherwise be paying them to manage.

Before deciding either way, get your own numbers rather than anyone else's. Run your site through PageSpeed Insights and read the field data section at the top, not the lab score underneath it. Field data is what real visitors on real phones experienced. The lab score is a simulation, and it is the number agencies quote because it is the flattering one.

Check your LCP, INP and CLS against 2.5s, 200ms and 0.1
Open your plugin list and count how many you could not explain the purpose of
Delete anything deactivated, since the code is still there
Test on a mid range Android phone rather than your own
Decide who is maintaining the site in twelve months, and choose for that person

Most sites I would look at do not need rebuilding. They need eight plugins removed.

Have you actually looked at what is loading on your home page?