Live Chat
Help Center
Measure before changing
Run repeatable tests on representative pages and note server response time, largest contentful paint and total page weight. Test both cached and uncached visits. A single score is less useful than identifying the resource that delays real users.
Use compatible hosting
Confirm supported PHP versions, memory limits, database software and HTTPS. Choose a data center close to the main audience or use a CDN for distributed visitors. Resource limits should reflect traffic, admin activity and scheduled jobs.
Configure caching carefully
Page caching can reduce repeated processing, while object caching can help database-heavy sites. Browser caching and compression reduce transfers. Exclude carts, account pages and other personalized routes from full-page caching.
Optimize media
Resize images to their displayed dimensions, use efficient formats and avoid oversized hero media. Lazy-load below-the-fold images without delaying the primary visual. Review font files and video embeds, which can quietly add significant weight.
Reduce plugin overhead
Keep plugins that solve a clear requirement and remove abandoned duplicates. Heavy page builders, tracking scripts and security scans can compete for resources. Test changes on staging and check both public pages and the WordPress dashboard.
Maintain the database
Clean expired transients and unnecessary revisions with a verified backup available. Inspect slow queries before applying broad optimizations. Performance maintenance works best as a routine: measure, change one factor, test and document the result.
Diagnose the slow step before buying a bigger plan
Separate browser, application and server delays
Start by checking a real page on mobile and desktop, then repeat after clearing the relevant caches. A slow page can be caused by large images, third-party scripts, unoptimized database queries, uncached requests or a saturated server. Do not assume a hosting upgrade will fix every cause.
A practical investigation sequence
- Record the URL, device, test time, network and whether the visitor is logged in.
- Use browser developer tools or an established performance-testing tool to spot oversized images and blocking requests.
- Check server-side logs and resource graphs for CPU, memory, PHP worker or database bottlenecks.
- Test one reversible change at a time on staging; document before-and-after results.
- Retest critical journeys including cart, checkout, login and password reset.
Cache safely
Public articles and brochure pages usually benefit from full-page caching. Personalised account pages, shopping carts and checkout sessions generally must not be served from a shared full-page cache. Confirm cache exclusions and purge behavior before enabling aggressive rules.
Images, fonts and plugins
Resize images to their displayed dimensions, use efficient formats where supported, and avoid loading a large hero image at thumbnail dimensions. Limit unnecessary plugins and external scripts, but review their purpose before disabling them. Always back up files and the database prior to plugin or PHP-version updates.
How to judge the improvement
Compare the same page and test conditions and check a representative set of pages—not only the homepage. Where available, use real-user measurements as well as lab results. Improvement should be measured in visitor experience and completed transactions, not just a single speed grade.