Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Guide

How to Make WordPress Fast on Mobile

Short answer

To make WordPress fast on mobile, fix the server first, then shrink images and cut JavaScript. Aim for Largest Contentful Paint under two and a half seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift of one tenth or less at the 75th percentile of mobile visits. Measure with PageSpeed Insights before and after each change, and wait about four weeks for the field data to show the full result.

Key takeaways

  • Good mobile Core Web Vitals are LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less.
  • PageSpeed Insights field data covers the previous 28 days of real Chrome users and is judged at the 75th percentile.
  • WordPress.org recommends PHP 8.3 or newer, MariaDB 10.11 or newer or MySQL 8.4 or newer, and HTTPS support.
  • Since WordPress 5.5, images lazy-load by default, and since 5.9 the first content image is skipped so the top of the page loads sooner.
  • AVIF images can be up to 50% smaller than JPEGs at the same quality, according to the WordPress Performance Team.
  • The mobile lab test simulates Slow 4G at 150 milliseconds of latency, 1.6 Mbps down, 750 Kbps up, and a CPU slowed four times.

What does mobile speed mean for a WordPress site?

Mobile speed is how fast a WordPress page loads and responds on a phone.

A phone has a smaller screen, a slower chip, and a mobile network, so a page that feels instant on a laptop can take seconds on a phone.

Google judges pages with Core Web Vitals, three measures of loading, response, and visual stability, and mobile scores are judged apart from desktop scores.

Mobile speed also matters for search. Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking, as Google Search Central explains.

How fast should a WordPress site load on a phone?

Aim for a Largest Contentful Paint of 2.5 seconds or less on mobile.

That target comes from web.dev, which sets good limits of 2.5 seconds for LCP, 200 milliseconds for Interaction to Next Paint, and 0.1 for Cumulative Layout Shift.

MetricWhat it measuresGoodNeeds workPoor
LCPMain content load time2.5 seconds or less2.5 to 4.0 secondsOver 4.0 seconds
INPResponse to a tap or click200 ms or less200 to 500 msOver 500 ms
CLSHow much the layout moves0.1 or less0.1 to 0.25Over 0.25

Google judges each metric at the 75th percentile of real page visits, split by mobile and desktop, so at least 3 in 4 mobile visits must meet the limit.

Two extra numbers help with diagnosis. PageSpeed Insights rates First Contentful Paint as good at 1,800 milliseconds or less, and Time to First Byte as good at 800 milliseconds or less, though TTFB is still listed as experimental as of November 2026.

How do you measure mobile speed before changing anything?

Run PageSpeed Insights on your home page and your three most visited pages first.

Open PageSpeed Insights, enter a URL, click Analyze, and read the Mobile tab. The top half shows field data from real Chrome users over the previous 28 days, while the bottom half shows one Lighthouse lab run. Read the field data first, since it shows what real visitors felt.

A Lighthouse score of 90 or above is good, 50 to 89 needs work, and below 50 is poor. A good lab score does not guarantee good field data, so check both.

Record the mobile LCP, INP, and CLS for each page before you change anything, so you can tell whether a fix helped.

What do you need before you start?

You need admin access, a backup, and a list of your slowest pages.

First, update WordPress. WordPress 7.1.5 was released on November 18, 2026 as a security release, and WordPress.org recommends updating right away.

Second, check your server. WordPress.org's Requirements page recommends PHP 8.3 or newer, MariaDB 10.11 or newer or MySQL 8.4 or newer, and HTTPS support, as of November 2026.

Third, make a full backup of files and database before you change caching, images, or plugins, so you can undo a change that breaks a page.

Fourth, pick one test page and check it by hand on a mid-range Android phone on a mobile network. It shows problems that a fast laptop on Wi-Fi hides.

Allow about 2 to 4 hours for a first pass on a small site. Larger sites need more time, so work through one template at a time.

How do you speed up the server and caching for mobile visitors?

Fix the server first, because no image trick can make up for a slow first byte.

web.dev gives a useful split for LCP: on a well-tuned page, Time to First Byte is about 40% of LCP, and the image or text load is about 40%. The two delay parts should each stay under 10%.

Follow these steps in order:

  1. Go to Dashboard, then Updates, and install any pending WordPress, theme, and plugin updates.
  2. Go to Tools, then Site Health, and open the Info tab to confirm your PHP and database versions match the WordPress.org numbers above.
  3. Ask your host to move you to PHP 8.3 or newer if Site Health shows an older version.
  4. Turn on page caching, either with your host's built-in cache or a caching plugin from the WordPress.org plugin directory.
  5. Turn on object caching if your host offers it, so repeated database queries are served from memory.
  6. Check that your host serves pages over HTTPS and from a data center near most of your visitors.

Caching helps mobile visitors most on repeat visits, since a cached page skips most server work. For a wider look at server fixes, see our guide on how to speed up WordPress.

How do you make images load faster on phones?

Serve each phone the smallest image file that still looks sharp.

WordPress has added srcset and sizes attributes to image markup since version 4.4, so the browser can pick the right size. The default list caps at 1,600 pixels wide, per Make WordPress Core.

Use these rules for every image you upload:

  • Upload images at the size they will display, not at full camera size.
  • Pick Medium or Large in the block editor instead of Full Size for content images.
  • Use WebP or AVIF where your host supports them, and keep JPEG or PNG as a fallback.
  • Compress each image before upload.

WordPress 6.5 added support for AVIF, and the WordPress Performance Team says AVIF images can be up to 50% smaller than JPEGs at the same quality. Check support at Tools, then Site Health, then the Info tab, then Media Handling.

WordPress has supported uploading WebP images since version 5.8. It does not create WebP copies of your JPEG uploads on its own, so convert files before upload or use a plugin that does it.

Lazy loading is already built in. Since WordPress 5.5, images get loading="lazy" by default, and since 5.9 the first content image is skipped so the top of the page loads sooner.

For format choices, see our guide on serving images in next-gen formats in WordPress.

How do you fix a slow hero image and layout shift?

Make the hero image load first, and give it a fixed size so nothing below it jumps.

The hero is often the LCP element, so it decides your LCP score. Chrome's performance guidance says to put the LCP image in plain HTML, add fetchpriority="high" to it, and never lazy-load it.

Use these steps for the hero on each template:

  1. Use a plain img tag for the hero, not a background image set by CSS or JavaScript.
  2. Add fetchpriority="high" to that image, and loading="eager" if your theme adds lazy loading to it.
  3. Set the width and height attributes so the browser reserves the right space.
  4. Keep the hero file small, and use a mobile-sized version for narrow screens.

The hint works in practice. web.dev reports that it cut LCP from 2.6 seconds to 1.9 seconds in a Google Flights example.

Layout shift has a separate cause. When an image, ad, or embed loads without reserved space, the content below it moves. Check the page source for images missing width or height, since page builders and custom code can skip them.

How do you cut JavaScript that slows taps and scrolling?

Remove or delay every script that is not needed for the first screen.

JavaScript blocks the main thread, which is the single lane the browser uses to handle taps and paint frames. Chrome's performance guidance says any JavaScript task over 50 milliseconds should be split, with work over 250 milliseconds moved to a Web Worker.

Work through this list on your slowest pages:

  • Deactivate plugins you no longer use, then re-run PageSpeed Insights to see the change.
  • Delay chat widgets, social feeds, and video embeds until the visitor scrolls near them.
  • Load analytics and ad scripts with defer so they do not block the first paint.
  • Replace heavy sliders and pop-ups with plain images and links.

Do not add a second optimization plugin to fix the first one. Each plugin adds its own scripts, so one caching plugin and one image plugin is enough for most small sites.

For a deeper pass, see our guide on reducing unused JavaScript in WordPress.

How do you check that it worked?

Re-run the same PageSpeed Insights mobile test on the same pages, then wait for field data.

First, clear every cache: your caching plugin, your host cache, and your content delivery network if you use one. Then load the page once on your phone to warm the cache.

Second, run PageSpeed Insights again and compare the lab LCP, INP, and CLS with your starting numbers. A change of a few points in the lab score alone is noise, so look for a clear move in the metrics.

Third, wait about 4 weeks before judging the field data. PageSpeed Insights reports the previous 28 days of real-user data, so a fix only shows up in full after a month.

Fourth, check Search Console after that wait. Its Core Web Vitals report groups URLs by pass or fail, using the same field data.

If lab numbers improved but field numbers did not, real phones and networks are the likely cause. The mobile lab test simulates Slow 4G at 150 milliseconds of latency, 1.6 Mbps down, 750 Kbps up, and a CPU slowed 4 times, per Lighthouse's throttling docs.

What mistakes slow mobile WordPress sites down?

The most common mistakes are easy to spot once you know them.

First, a theme that loads desktop-sized images and videos on phones. A 4,000-pixel image shown at 400 pixels wide wastes most of its bytes.

Second, lazy-loading the hero image. WordPress skips the first content image since 5.9, but a theme or plugin can still add loading lazy to it, which delays the largest paint.

Third, hiding content on mobile to make the page look shorter. Google warns against lazy-loading primary content behind a tap or swipe, because it may not load that content at all, as its mobile-first indexing guide explains.

Fourth, stacking plugins that each add scripts and styles. Audit your plugin list twice a year and remove anything unused.

Fifth, skipping the phone check. Test every template on a real phone, because the desktop view hides mobile problems.

Fix one mistake at a time and re-test after each change, so you know which fix helped.

Frequently asked questions

Why is my mobile score lower than my desktop score?

The mobile lab test simulates a mid-range phone on a Slow 4G connection with the CPU slowed four times, while the desktop test uses a wired connection with no slowdown. Real mobile visitors also use slower phones and networks than your laptop. Fix the mobile-specific causes first: oversized images, a slow hero image, and heavy JavaScript.

Do I need a separate mobile theme or plugin to speed up WordPress?

No. A responsive theme plus WordPress built-in responsive images and lazy loading is enough for most sites, and Google recommends responsive web design because it is the easiest pattern to keep up. A separate mobile site risks showing less content than the desktop site, which can hurt indexing. Fix your current theme before adding a mobile-only layer.

How long does a speed fix take to show in PageSpeed Insights?

Lab results change as soon as you clear every cache and re-run the test, so you can check a fix the same day. Field data is slower: it covers the previous 28 days of real-user visits, so a fix only shows up in full after about four weeks. Judge a change by the lab numbers first, then confirm it in the field data later.

Should I lazy-load every image on the page?

No. Never lazy-load the hero image or any image in the first screen, because that delays the largest paint and hurts LCP. Lazy-load only images below the fold, where visitors have to scroll to see them. WordPress already skips lazy loading for the first content image since version 5.9, but check that your theme or a plugin has not added it back.

What PHP version should my WordPress site run?

WordPress.org recommends PHP 8.3 or newer, as of November 2026, along with MariaDB 10.11 or newer or MySQL 8.4 or newer. Check your versions at Tools, then Site Health, then the Info tab. Older PHP versions are end of life and can slow your site as well as expose it to security problems, so ask your host to upgrade.

Can I fix mobile speed without changing my theme?

Often yes. Updating PHP, turning on page caching, serving smaller image sizes, and removing unused plugins can fix most mobile speed problems without a theme change. Change themes only when the theme itself is the cause, for example when it loads desktop-sized images or scripts that you cannot turn off. Re-test after each change so you know what helped.

Sources

  1. Web Vitals web.dev
  2. About PageSpeed Insights Google for Developers
  3. Mobile-first Indexing Best Practices Google Search Central
  4. Requirements WordPress.org
  5. Lazy-loading images in 5.5 Make WordPress Core
  6. Optimize Largest Contentful Paint web.dev
  7. Throttling in Lighthouse Google Chrome

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test