WordPress Speed Optimization: How to Pass Core Web Vitals in 2026

Visitors decide within seconds whether to stay. A slow page loses enquiries, sales and search visibility, and it hurts most on phones with patchy mobile data. The good news is that WordPress sites are slow for the same handful of reasons, and fixing them in the right order delivers most of the gains in an afternoon.

This WordPress speed optimization guide follows the exact order I use on client sites: measure, fix images, add caching, cut plugin and script weight, then tackle the specific Core Web Vitals. Download the checklist at the end to work through it step by step.

Step 1: Measure before you change anything

Open PageSpeed Insights and test three different pages: the homepage, a key service or product page and a blog post. Always look at the mobile results first. Write down the numbers so you can compare after each change.

Focus on the three Core Web Vitals Google uses:

• LCP (Largest Contentful Paint): how long the main content, usually the hero image or headline, takes to appear. Good: under 2.5 seconds.
• INP (Interaction to Next Paint): how quickly the page reacts when someone taps or clicks. Good: under 200 milliseconds.
• CLS (Cumulative Layout Shift): how much the layout jumps while loading. Good: under 0.1.

The report shows two kinds of data. Field data comes from real Chrome users over the last 28 days and is what Google uses. Lab data is a single simulated test, which is useful for debugging. Small sites may not have field data yet; use the lab results until they do.

Step 2: Fix your images (the biggest quick win)

Oversized images are the most common reason WordPress pages are slow. A 4000-pixel phone photo squeezed into a 600-pixel box wastes megabytes on every visit.

• Resize images to the largest size they are actually displayed at before uploading.
• Use modern formats such as WebP or AVIF. Recent WordPress versions and most image optimization plugins can convert automatically.
• Compress every image. A good optimizer reduces file size without visible quality loss.
• Lazy-load below the fold, not above it. WordPress lazy-loads images automatically, but your hero image should load immediately. If a plugin lazy-loads the hero, exclude it.
• Set width and height on images so the browser reserves space and the layout does not jump.

Step 3: Turn on caching

Without caching, WordPress builds every page from scratch using PHP and database queries for each visitor. Caching saves a ready-made copy and serves that instead, which is usually the single biggest improvement to server response time.

• If your host offers server-level caching (Hostinger, for example, includes LiteSpeed caching on many plans), use it with the matching plugin.
• Otherwise, install one reputable caching plugin. Never run two caching plugins at the same time; they conflict and can break your site.
• Clear the cache after design changes, and exclude cart, checkout and account pages if you run WooCommerce (good caching plugins do this automatically).

Step 4: Audit your plugins

Go to Plugins and question every one. Delete anything you do not use. For the rest, ask whether it loads scripts on pages that do not need them. Sliders, social media feeds, chat widgets and some form plugins are frequent offenders.

Tip: Check one plugin at a time on a staging copy: deactivate it, re-run PageSpeed Insights and note the difference. You will quickly find the expensive ones.

Step 5: Slim down fonts and third-party scripts

• Use at most two font families and only the weights you actually use. Each extra weight is another file to download.
• Host fonts locally where your theme allows it, and use font-display: swap so text appears immediately.
• Question every third-party script: chat widgets, heatmaps, tracking pixels and embedded social posts. Each one competes for bandwidth and main-thread time.
• Replace embedded YouTube videos with a lightweight click-to-play thumbnail that loads the real player only when someone presses play.

Step 6: Fix each Core Web Vital directly

Improving LCP

• Make sure the hero image is properly sized, compressed and not lazy-loaded.
• Reduce server response time with caching and a good host.
• Avoid sliders as the first element; a single static image loads far faster.

Improving INP

• Remove heavy JavaScript you do not need, especially from sliders, animations and multiple tracking tools.
• Delay non-essential scripts until after the page loads.
• Keep the page structure lean; very large pages with thousands of elements react slowly.

Improving CLS

• Give images, videos and embeds fixed dimensions.
• Reserve space for ads, cookie banners and announcement bars instead of pushing content down.
• Avoid fonts that swap to a very different size; pick fallback fonts with similar proportions.

Step 7: Tidy the database

Over the years the database collects old post revisions, spam comments and expired temporary data. Clean it with a trusted optimization tool, and always back up first. You can also limit future revisions with define( 'WP_POST_REVISIONS', 10 ); in wp-config.php.

Step 8: Check your hosting and PHP version

If even a simple page takes a long time before anything appears, the server itself is slow and no plugin can fully fix it. Use a current PHP version, which is noticeably faster than old ones, and upgrade your plan or host when your site grows. Our Hostinger WordPress setup guide covers the right settings on a new account.

Page builder sites: extra tips

• Use global colors and fonts instead of styling each widget individually.
• Build with Flexbox containers and avoid nesting containers inside containers inside containers.
• Turn on the builder's own performance features in its settings.
• Reuse saved templates instead of rebuilding similar sections on every page. See Elementor Pro features worth learning.

Change one thing at a time

The fastest way to break a site is to install three optimization plugins and change twenty settings at once. Make one change, clear caches, re-test the same pages and check that forms, menus and checkout still work. If something breaks, you know exactly what caused it.

Speed and security go hand in hand, because fewer plugins means fewer things to attack. Once your site is fast, run through the WordPress security checklist. Download the speed checklist below to track your progress.