WordPress speed is not a philosophical debate. It is an inventory problem: how many plugins enqueue assets, how heavy your theme is, how large your hero media is, and whether third parties are allowed to run before the user can interact.
Canadian SMBs often hear “WordPress is slow” when what they really have is a stack nobody governs. This article separates what WordPress can do from what your build actually ships, and when hand-coded templates are worth the migration pain.
When WordPress is legitimately competitive on performance
- Small plugin set with named owners and quarterly audits
- Performance-minded hosting sized for traffic peaks
- Modern image formats and responsive delivery
- Minimal page builders (or builder output optimized aggressively)
- Tag governance for marketing scripts
Where WordPress tends to fall behind hand-coded
Main-thread work (INP)
Plugins and builders increase JavaScript and long tasks. INP suffers on mobile first—especially outside downtown fibre.
Asset bloat (LCP)
Sliders, hero videos, and unoptimized photography inflate LCP.
CLS from ads and embeds
Late-loading banners and maps shift layout unless space is reserved.
Field-first measurement (non-negotiable)
- Search Console CWV segmented by template
- LCP element identification per template
- INP on menus, filters, forms
- CLS on consent and promo surfaces
Use Core Web Vitals & PageSpeed as your baseline vocabulary.
When hand-coded wins
If SEO money pages need minimum bytes and maximum control, bespoke static or lightly-templated HTML/CSS often wins—especially for local service hubs and comparison content.
Trade-off: editorial workflows must be rebuilt intentionally.
Migration caution
Speed is not only templates—it is redirects, internal links, and analytics continuity. If you are considering migration, read migration services and talk through risk before cutover.
Summary
WordPress can be “fast enough” with discipline. Hand-coded still wins absolute performance when you commit to governance and simpler publishing workflows.
