WordPress Speed Optimization: 17 Practical Hacks That Work
A field-tested guide to improving Core Web Vitals, reducing server work and keeping WordPress fast as your site grows.
By Entitude Team · 14 min read
Start with a repeatable performance baseline
Measure before changing anything. Record mobile and desktop Core Web Vitals, time to first byte, page weight and request count on your homepage, a typical article, a product page and checkout. Test logged-out pages in a private window and repeat each run. A baseline prevents placebo fixes and exposes whether the bottleneck is hosting, database work, JavaScript or media.
Fix hosting, caching and PHP first
Use current PHP, persistent object caching where available, full-page caching for public traffic and a CDN for static assets. Keep cron reliable and remove abandoned scheduled tasks. These changes reduce expensive WordPress bootstrap work before you spend time shaving individual kilobytes. Never cache account, cart or checkout responses without explicit exclusions.
“The fastest WordPress site is not the one with the most optimization plugins; it is the one that asks the browser and server to do less work.”
Make images and fonts cheaper
Export images at their rendered dimensions, prefer modern formats, define width and height, and lazy-load media below the fold. Keep the hero image eager because it is often the largest contentful paint element. Self-host a restrained font set, preload only the critical face and avoid loading weights that the design never uses.
Control plugins and third-party scripts
Audit plugins by capability rather than count. One poorly designed extension can add more database queries and JavaScript than twenty disciplined ones. Remove duplicate analytics, social widgets and tag-manager experiments. Delay non-critical chat, heatmaps and advertising until consent or interaction, and verify that delay does not break attribution.
“Performance is a publishing habit. Every new script, font and plugin should earn its place.”
Clean the database without risky shortcuts
Back up before maintenance. Remove expired transients, orphaned options and obsolete tables only when ownership is understood. Check autoloaded options for unexpectedly large values. Revision limits and sensible log retention help, but frequent blind cleanup can create more risk than value. Optimize high-frequency queries instead of treating the database as a bin to empty.
Use a monthly performance budget
Set limits for page weight, JavaScript, fonts and third-party requests, then include them in release checks. Compare key templates after plugin updates. The goal is not a perfect laboratory score; it is a consistently quick experience for real visitors on average devices and connections.
Join the conversation
Have a question or a WordPress workflow worth sharing? Send it to our support team and we may include it in a future guide.
Contact the editorial team