"WordPress is slow." "Custom sites are always faster." Both statements are oversimplifications — and both cost businesses money when taken as absolute truth.
The honest answer: a well-optimised WordPress site can outperform a poorly built custom site, and a properly architected Next.js site will consistently beat an average WordPress installation. The question is not which platform is faster in theory — it is which fits your content needs, budget, and performance requirements.
The performance gap in numbers
Based on real projects and industry benchmarks, here is what typical scores look like for each approach without dedicated optimisation:
| Setup | Typical mobile PageSpeed | Typical LCP | Typical TTFB |
|---|---|---|---|
| WordPress + page builder (Elementor/Divi) | 30–55 | 4–8s | 600ms–1.5s |
| WordPress + lightweight theme + cache | 70–85 | 2–3.5s | 300–600ms |
| WordPress fully optimised (our standard) | 85–95 | 1.5–2.5s | 150–300ms |
| Next.js / custom (our standard) | 92–100 | 0.8–1.8s | 50–150ms |
| Static site (Astro, Hugo) | 95–100 | 0.5–1.2s | 30–80ms |
The gap between "WordPress with page builder" and "Next.js custom" is enormous — but the gap between "optimised WordPress" and "Next.js" is much smaller and often acceptable for content-heavy sites.
Why WordPress is often slow — and when it is not
WordPress itself is not inherently slow. PHP 8.2 with OPcache, a good object cache, and page caching can serve HTML in under 100ms. What makes most WordPress sites slow is everything built on top of it.
What slows WordPress down
- Page builders (Elementor, Divi) — 500 KB–2 MB of CSS/JS per page
- 20–40 plugins each adding hooks, queries, and assets
- No page cache — PHP rebuilds HTML on every request
- Shared hosting with 200 other sites on the same server
- Unoptimised media library with full-resolution uploads
- Database bloat from revisions, transients, and orphaned data
When WordPress can be fast
- Lightweight theme (GeneratePress, Astra) — minimal CSS/JS footprint
- Under 15 active plugins, regularly audited
- Page cache (WP Rocket) + object cache (Redis)
- Managed WordPress hosting or VPS with PHP 8.2
- CDN (Cloudflare) for static assets
- Professional optimisation — achievable 90+ PageSpeed
Full WordPress optimisation guide: why WordPress is slow and how to fix it →
Why custom sites are faster by architecture
Custom sites built with Next.js, Astro, or similar modern frameworks have structural advantages that WordPress cannot match without significant engineering effort:
Static generation and edge delivery
Pages are pre-built at deploy time and served from CDN edge nodes worldwide. No PHP execution, no database query, no server-side rendering on each request. TTFB drops from 400ms to under 50ms.
Zero plugin overhead
Every feature is code you wrote or chose deliberately — not 30 plugins each loading their own CSS, JS, and database queries. The JavaScript bundle contains only what the page needs.
Automatic image optimisation
Next.js <Image> converts to WebP/AVIF, generates responsive sizes,
and lazy-loads by default. In WordPress this requires plugins and configuration.
Code splitting and tree shaking
Only the JavaScript needed for the current page is loaded. WordPress themes typically enqueue the same 500 KB JS bundle on every page regardless of content.
Head-to-head: the same content, two platforms
We built identical marketing pages — same copy, same images, same layout — on WordPress and Next.js:
| Metric | WordPress (optimised) | Next.js (custom) |
|---|---|---|
| Mobile PageSpeed | 87/100 | 98/100 |
| LCP | 2.1s | 0.9s |
| INP | 180ms | 45ms |
| CLS | 0.06 | 0.01 |
| Total page weight | 1.4 MB | 320 KB |
| JavaScript | 680 KB | 85 KB |
| Time to build | 2 weeks | 3 weeks |
| Content editing | Client self-service | Developer or headless CMS |
Next.js wins on every performance metric. WordPress wins on content management flexibility and build time. The right choice depends on which trade-off matters more for your business.
When WordPress is the right choice for performance
- ✓You need frequent content updates by non-technical staff
- ✓Budget is limited and the site is primarily informational
- ✓You commit to proper optimisation (hosting, cache, image plugins, plugin audit)
- ✓Target PageSpeed 85–90 is acceptable for your traffic and conversion goals
- ✓WooCommerce or existing WordPress ecosystem integrations are required
When custom development is worth it for performance
- ✓PageSpeed 95+ and sub-1s LCP are business requirements, not nice-to-haves
- ✓High traffic volume where server costs and TTFB matter at scale
- ✓Complex interactivity — configurators, dashboards, real-time features
- ✓Core Web Vitals directly affect ad Quality Score and CPC
- ✓You are rebuilding anyway — migration is the right moment to switch stacks
Full technology comparison: WordPress vs Next.js comparison →
The headless hybrid — best of both worlds
You do not have to choose entirely. Headless WordPress (WordPress as CMS backend, Next.js as frontend) gives content editors the familiar WordPress admin while delivering Next.js performance to visitors.
Content team
Edits in WordPress admin — posts, pages, media, SEO fields. No code required.
Visitors
Receive statically generated Next.js pages from CDN — 95+ PageSpeed, sub-1s LCP.
Trade-off: higher development cost and complexity. Best for content-heavy sites where both performance and editorial flexibility are non-negotiable.
Performance and SEO — why the platform choice matters
Google ranks based on Core Web Vitals from real user data. A WordPress site scoring 55/100 on mobile will rank below a competitor at 92/100 — all else being equal.
The business cost of slow loading is measurable: why 90% of businesses lose customers in the first 3 seconds →
For a deeper look at what slows sites regardless of platform: 10 real reasons your website loads slowly →
The most expensive mistake: choosing wrong, then patching
Building a complex SaaS product on WordPress with 40 plugins, then spending 2,000 EUR/year on optimisation to keep it at 70/100 — when a custom build would have scored 95/100 from launch — is the pattern we see most often. Choose the right platform first. Optimise second.
// SINGULARITY EDGE STUDIO
We build fast — on any stack
WordPress optimised to 90+ PageSpeed, or custom Next.js at 95+ — we guarantee the score, not just the platform. We will tell you honestly which approach fits your project before you commit.
- WordPress performanceCustom lightweight themes, cache, CDN — 90+ guaranteed
- Custom developmentNext.js, TypeScript — 95+ PageSpeed by default
- Headless hybridWordPress CMS + Next.js frontend for content-heavy sites
Full WordPress vs Next.js comparison → · Website performance optimization →
Not sure which platform is right for you?
Free Speed Audit of your current site + honest recommendation: optimise WordPress, rebuild custom, or go headless.
Free Speed Audit →Conclusion
WordPress is not slow — unoptimised WordPress is slow. Custom is not automatically fast — poorly built custom sites exist too. The performance difference between a well-optimised WordPress site and a Next.js site is real but smaller than the gap between average WordPress and either optimised option.
If you need 95+ PageSpeed, complex interactivity, or scale — custom development wins. If you need content flexibility on a budget and commit to proper optimisation — WordPress can deliver. The worst choice is the wrong platform with no optimisation plan.
// TOPICS
Author
Singularity Edge Studio
Engineering studio for web and software — Plovdiv, Bulgaria. We build corporate sites, SaaS, e-commerce, and DevOps infrastructure with a focus on measurable outcomes.
// RELATED FAQ
// MORE ARTICLES
How Images Slow Down Your Website
Images account for up to 70% of page weight on typical websites. Formats, dimensions, compression, lazy loading, and CDN delivery — a complete guide to fixing the biggest speed bottleneck.
Web DevelopmentTypeScript — why it became a mandatory standard and what it means for your project in 2026
In 2026, plain JavaScript for a new professional project is already technical debt. How TypeScript cuts bugs, speeds up AI-assisted development, and protects business risk — with examples, migration steps, and a production tsconfig.
Web DevelopmentPWA — Mobile App Without the App Store: Why Your Business Needs It in 2026
Progressive Web App transforms your website into a mobile app without the App Store — offline mode, push notifications, one codebase. Complete guide with architecture, comparison, pricing and implementation steps.