WordPress site speed optimization starts with measurement, not just installing another plugin. Check Google’s Core Web Vitals, identify bottlenecks such as heavy images, late-loading CSS, redundant plugins, and a slow server, and fix them in order. A fast WordPress site loads its main content within 2.5 seconds, responds to clicks in under 200ms, and remains stable during loading. At SGO, speed optimization is a core part of SEO and starts at ₪1,500 per site.
- Google's target: LCP up to 2.5 seconds, INP up to 200 milliseconds, CLS up to 0.1, in 75% of visits.
- A PageSpeed score of 90 to 100 is good, 50 to 89 needs improvement, and 0 to 49 is poor.
- According to Google, WebP images are 25% to 34% smaller than JPEGs of the same quality.
- WordPress recommends PHP 8.3 or higher. An old version slows down all pages.
- On SGO's own site, mobile LCP dropped from 9.4 to 3.3 seconds after fixing image loading.
Table of contents
How do you measure WordPress site speed?
Measure your site speed using two Google tools: PageSpeed Insights for individual pages and the Core Web Vitals report in Search Console for 28 days of real-user data. The PageSpeed score is a simulation of a mid-range phone on a slow network, which is why it is almost always lower than the desktop experience. Deciding what to fix should be based on field data, as that is what Google uses to evaluate page experience.
The three metrics Google tracks
According to Google's web.dev documentation, a page meets the target when it passes in 75% of visits, measured separately for mobile and desktop:
- LCP (Main content loading): under 2.5 seconds is good, over 4 seconds is poor.
- INP (Interaction to Next Paint): Under 200ms is good, over 500ms is poor. This metric replaced FID in March 2024.
- CLS (layout shifts): Up to 0.1 is good, over 0.25 is poor.
How to read PageSpeed scores
According to Lighthouse documentation, a score of 90 to 100 is green, 50 to 89 is orange, and 0 to 49 is red. A perfect 100 is difficult to achieve and is not necessarily the goal. A site with a score of 75 that passes field metrics is better than a site with a 95 score that feels slow to real users.
What slows down a WordPress site?
Most WordPress sites struggle with the same five factors: oversized images, render-blocking CSS and JavaScript, plugins that load files on every page, an outdated PHP version, and a crowded hosting server. The order matters: there is no point in buying an expensive server when your hero image weighs 2MB.
Images and fonts
The hero image is usually the element that determines LCP. When it is lazy loaded, the browser discovers it too late and the metric suffers. External fonts loaded without preloading also delay the appearance of text.
Page builders and plugins
Elementor and other page builders add CSS and JS files to every page. Every inactive plugin adds unnecessary server requests. Auditing your plugin list almost always reveals items that can be deactivated without affecting the design.
Server and PHP version
WordPress recommends PHP 8.3 or higher and MySQL 8.0 or MariaDB 10.11 or higher. A site running on PHP 7 loses speed on every page load, even with light content. If the server itself is slow, consider web hosting optimized for WordPress.
WordPress speed optimization in seven steps: what do we do?
Work from the heaviest factors to the lightest, and measure after every step. This helps you understand what actually worked and what just added complexity.
1. Baseline measurement
Record the PageSpeed scores of your homepage and your two highest-converting pages for both mobile and desktop. Without a starting point, you cannot prove improvement.
2. Converting images to WebP and resizing to actual dimensions
According to Google, WebP images are 25% to 34% smaller than JPEG and about 26% smaller than PNG at the same quality. Resize an image that is 4,000 pixels wide but displayed at 800 pixels before uploading.
3. Hero image: no lazy loading, with preload
Load the image above the fold immediately and defer images further down the page. This fix made the biggest impact on LCP for the SGO website.
4. Cleaning up plugins and scripts
Deactivate unused plugins and prevent active ones from loading files on pages where they are not needed. A common example: a forms plugin loading its files on pages without a form.
5. Cache, compression, and CDN
Page caching prevents the server from rebuilding every page, and a CDN serves files from the server closest to the user. Caution is needed: delayed loading of CSS without critical CSS causes the page to jump, which is exactly what happened on the SGO site.
6. PHP update and server check
Update PHP to a supported version, ensure all plugins are compatible, and measure the Time to First Byte (TTFB). A slow server slows down every page, even after all other fixes.
7. Monitoring and maintenance
Measure these pages again and compare to the baseline. Speed degrades over time: a new plugin, another marketing script, or a heavy image. This is why you should include speed checks in your monthly website maintenance.
Which fixes impact which metric?
| Fix | Primary metric improved | Metric or target |
|---|---|---|
| Converting images to WebP | LCP | 25% to 34% lighter than JPEG |
| Preloading the hero image | LCP | Target: up to 2.5 seconds |
| Reserved height for images, banners, and carousels | CLS | Target: Up to 0.1 |
| Less plugin JavaScript | INP | Target: up to 200 milliseconds |
| PHP update | TTFB, followed by LCP | Recommended: PHP 8.3 or higher |
| Page caching and CDN | TTFB and LCP | Green PageSpeed score: 90 to 100 |
What we learned from optimizing SGO site speed
On the SGO website, built with WordPress and Elementor, two issues common to many other sites were measured in July 2026. This data is from our own site, so we can publish it in full:
Late-loading hero image
The preload was pointing to an image that did not even display on mobile, and the header background image was loading without priority at double the size. After the fix, the mobile homepage LCP dropped from 9.4 seconds to 3.3 seconds.
Delayed CSS loading
Setting CSS to load asynchronously in a caching plugin caused the Elementor layout to load after the content, making the page jump. The desktop CLS was between 0.35 and 1.10. After disabling the setting, it dropped to 0.009. The lesson: a setting intended to speed up a site can actually hurt it, so always measure after every change.
How much does WordPress speed optimization cost?
At SGO, speed optimization starts at ₪1,500 and includes image optimization, plugin cleanup, cache configuration, and before-and-after PageSpeed testing. Full technical optimization starts at ₪3,000 and adds critical CSS, site-wide Core Web Vitals fixes, and a schema check. The final price depends on the number of templates and plugins, so we audit the site before providing a quote.
When to consider a different hosting provider
If the server response time is still high after all fixes, the problem is with the server, not the site. Hosting and maintenance at SGO start at ₪65 per month and include a free site migration.
SGO is a web design and SEO agency from Netanya that builds and maintains WordPress and Elementor websites for businesses across the country. Speed optimization is performed without changing the site design and is verified with before and after measurements.
Is your site slow on mobile?
Leave your details and we will check your site's Core Web Vitals, explain what is slowing it down, and provide a quote for the fix.
WordPress speed optimization FAQ
What is considered a fast WordPress site?
Why is the PageSpeed score lower on mobile than on desktop?
Is a caching plugin enough to improve site speed?
How much does WordPress site speed optimization cost at SGO?
Does speed optimization change the site design?
Which PHP version should you use for WordPress?
Want more customers from your website? SGO specializes in digital marketing and SEO that brings traffic and leads.