Speed Up a WordPress Site
WordPress performance depends on the visitor’s device and connection as well as hosting, page construction, caching, media and external services. Measure the affected pages first so each change can be compared with a baseline.
Describe where the site feels slow
- Identify the affected page and whether the delay is on the public site, WordPress admin or both.
- Check whether the problem affects all visitors, signed-in users or one device or location.
- Record when it began and any recent content, plugin, theme or hosting change.
- Measure several representative pages rather than relying on one score.
Review the main performance areas
- Hosting: response time, available resources and current PHP support.
- Caching: suitable page, browser, object and CDN caching without caching private content.
- Images and fonts: appropriate dimensions, compression, formats and loading behaviour.
- Themes and plugins: slow queries, repeated requests, large scripts and duplicate features.
- Database and scheduled work: excessive stored data, background tasks or uncached queries.
- External services: third-party scripts, advertising, analytics, chat and embedded media.
Change one area at a time
Create a backup and test significant performance changes on staging where possible. Record the before and after result, then check forms, accounts, checkout and other dynamic features. Stacking several cache or optimisation plugins can make problems harder to trace.
Maintenance monitoring includes performance and Core Web Vitals information. Read Reading Your Monitoring Dashboard, or submit a Fix Request when you want a developer to investigate a specific performance problem.
Common questions
Frequently Asked Questions
Why is WordPress admin slow when the public site is fast?
Public pages may be cached while admin requests are dynamic. Slow plugins, database queries, scheduled work, external API calls or limited server resources may affect admin separately.
Will installing a caching plugin always make the site faster?
No. It must suit the hosting and website. Duplicate caching layers or caching private pages can introduce errors without addressing the real bottleneck.
Why do performance test results change between runs?
Network conditions, test location, server load, cache state and third-party services vary. Compare several runs under similar conditions and focus on consistent patterns.
What should I include in a performance Fix Request?
Include the affected pages, when the slowdown occurs, who experiences it, recent changes and any monitoring or test result that demonstrates the pattern.