Measure before changing settings
Test the home page, an article and a service page, plus commerce pages where relevant. Record mobile and desktop PageSpeed Insights results. Separate real-user data from laboratory tests; device, network and sample availability affect results. A single run is insufficient evidence for buying a plugin or moving hosts.
Understand user-experience metrics
Core Web Vitals measure main-content rendering with LCP, interaction responsiveness with INP and visual stability with CLS. Good thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, assessed at the 75th percentile with mobile and desktop considered separately. They are experience targets, not ranking guarantees.
Optimize images, fonts and above-the-fold content
Serve appropriately sized images in suitable formats such as WebP or AVIF where supported, with acceptable visual quality. Reserve dimensions to reduce layout shifts and lazy-load offscreen images. Avoid delaying the main content image with lazy loading without measuring its effect. Reduce unused font families and weights.
Configure caching without breaking functionality
Back up and use staging where possible. Cache eligible public pages while excluding personalized pages, cart, checkout and account flows as required. Avoid stacking overlapping minification and script-delay systems at once. Test menus, forms, search, login and checkout after each change, then purge relevant caches.
Review plugins, hosting and the database
There is no magic plugin count. Investigate expensive queries, external calls and unnecessary work, and remove unused components after checking dependencies. Keep WordPress and the server stack supported and compatible. Examine resources and response times before upgrading hosting; a large image or external service may be the actual bottleneck.
Compare results and monitor impact
Retest the same pages under comparable conditions and log changes and results. Laboratory improvements may appear before real-user data reflects them. If functionality breaks, restore the last stable setup and isolate the cause. Prioritize less waiting and a functional experience rather than a perfect score at any cost.
Original article images
These are preserved original media and may depict obsolete tools or interfaces. Use the reviewed instructions above for current practice.
References and tutorial links
Is a score of 100 required?
It is not a guarantee of rankings or success. Assess functionality, user experience and actual metrics.
Do fewer plugins always mean a faster site?
Not necessarily. Workload and implementation quality matter more than count alone.
Should I cache every page?
No. Personalized, cart and checkout pages need exclusions appropriate to the system.
