Resultoz · Guides · Reports

WordPress site slow on a phone: safe first steps

For small local businesses · November 9, 2026

A WordPress site can feel quick on a desktop and sluggish on a phone, where the connection is weaker and the screen is smaller. The good news is that the usual causes are a short list, and you can work through them yourself without touching code. This guide is not made by, partnered with or endorsed by WordPress.

Back up before you change anything

Speed work means editing images, turning things off and adding a plugin or two. Before any of that, make a full backup of files and database so you can undo a mistake in minutes instead of rebuilding pages from memory.

Many hosting dashboards include a one-click backup or restore point. If yours does not, install a reputable backup plugin, run a full backup, and download a copy somewhere off the site, such as cloud storage on your own computer.

• Run a full backup (files plus database), not just a theme export.
• Save a copy away from the hosting account.
• Note the date and what you plan to change, so you know what to roll back.
• Make one change at a time, then reload your site on a phone.
• Keep the previous backup until the new version has been live for a while.

Fix the images first

Large photos are the usual reason a page crawls on a phone. A picture straight from a phone camera or a stock library is often far wider than any phone screen needs, and the visitor downloads every bit of it.

In the WordPress dashboard, go to Media, open each large image, and check the dimensions listed on the right. Resize oversized files on your computer or with an image editing tool, then re-upload and swap them in. Save photos as JPG and logos or flat graphics as PNG, or use WebP if your theme supports it.

• Resize photos so they are no wider than the area they fill on the page.
• Compress each file before uploading, aiming for the smallest size that still looks clean.
• Replace background video or sliders on the home page with a single still image.
• Add descriptive alt text while you are in there, so the image still makes sense if it fails to load.
• Avoid uploading PDFs or print-quality files as page images.

Add one caching plugin, not three

Caching saves a ready-made copy of your pages so the server does less work for each visitor. Go to Plugins, then Add new, search for a well-reviewed caching plugin, install it, and turn on page caching plus file minification if offered.

Use a single caching plugin. Two or more fighting over the same job can cause broken layouts or stale pages. After turning caching on, clear the cache, then open your site in a private browser window on your phone to see what a new visitor sees. Check the menu, contact form and booking buttons still work.

• Enable page caching first, then test before switching on anything else.
• Turn on lazy loading for images below the fold if the plugin offers it.
• Clear the cache after every content or settings change while testing.
• Ask your host whether server-level caching is already active, to avoid doubling up.

Remove plugins and features you no longer use

Every active plugin can add scripts and styles to each page. Open Plugins and read the list honestly: old sliders, unused contact forms, analytics add-ons, social feeds and leftovers from a previous designer.

Deactivate one, reload your site on a phone, and confirm nothing broke. If all is well, delete it rather than leaving it dormant. Keep updates current for what remains, including the theme and WordPress itself.

• Deactivate, test, then delete, in that order.
• Check contact forms and maps after each removal.
• Replace heavy page builder sections with simple text blocks where you can.
• Limit the fonts and icon sets your theme loads.

Test speed the way a customer experiences it

Run your home page and one service page through pagespeed.web.dev and read the mobile results. Largest Contentful Paint is considered good at two and a half seconds or less and poor above four seconds. Cumulative Layout Shift should stay at or below 0.1, and Interaction to Next Paint at or below 200 milliseconds.

Also do the simple test: open your site on your own phone, off wifi, and time how long it takes before you can read something and tap a button. Retest after each change so you know which fix helped.

Resultoz, Van Nuys, CA · Privacy · Terms