WordPress can be cached and optimised; Next.js can also ship heavy JavaScript. Choose from measured bottlenecks, editing needs and maintenance responsibility rather than a promised speed advantage.
Practical checks
-
Test hosting, page caching, images, plugins and third-party scripts on staging first.
-
Estimate rebuild costs including content migration, redirects, integrations and training.
-
Keep the platform when targeted fixes meet the agreed requirements at lower total cost.
What to record before a decision
Write a short decision record: the current problem, one proposed change, the evidence needed to accept it, the person responsible and a review date. Test with fictional data before exposing customer information. If evidence is missing, record it as unknown rather than presenting a forecast as an achieved result. Keep a working fallback so a customer can still reach staff when an integration fails.
Scope and limits
Both platforms require appropriate hosting, asset control, accessible design and maintenance. WordPress optimisation and Next.js static export each have documented options and limits. Framework choice does not guarantee a speed score, search ranking or conversion increase.
