Why Is My Website Slow on Phones?

Short answer: Run the site through PageSpeed Insights on the Mobile tab and read the real-visitor section at the top. If Largest Contentful Paint is above 2.5 seconds, the cause is almost always oversized images, scripts from a page builder, theme or plugins, third-party widgets, or a server far from Singapore. Fixes handle the first and last; when the platform itself ships the scripts, a rebuild is the cheaper route.

This guide is for business owners. It stops at diagnosis and the decision, and leaves plugin-level configuration to a developer.

How do I measure my website speed?

Use PageSpeed Insights. It is free, it is Google's own tool, and it shows the same numbers Google uses in Search Console.

The report has two sections, and owners often read the wrong one. Google's documentation describes them as:

• Field data, at the top. Real Chrome visitors to your site over the past 28 days. This is what your customers experienced and what Google's ranking systems use.
• Lab data, below. One simulated load on a mid-range phone and a throttled connection. Useful for finding the cause, not for judging the site.

The field section decides whether you have a problem.

Steps:

• Enter the home page URL and switch to Mobile. Note the three Core Web Vitals and whether the overall assessment says Passed or Failed.
• Repeat for the top 3 service pages and the contact page. Home pages are often optimised while inner pages are not.
• If the field section says there is not enough data, the site has too few Chrome visitors for a 28-day sample. Use the lab section, and read Search Console's Core Web Vitals report for grouped URLs.
• Scroll to Diagnostics in the lab section. The items with the largest savings in seconds or kilobytes are your cause list.

What are Core Web Vitals?

Core Web Vitals are three measurements Google uses to summarise how a page feels to a visitor. web.dev sets the thresholds, and each is measured at the 75th percentile of page loads, so 3 in 4 visits must meet the target.

What each one tells you about the cause:

• Poor LCP: large images, slow server response, or scripts that block the page from painting.
• Poor INP: too much JavaScript running on the main thread, usually from builders, sliders, trackers and chat widgets.
• Poor CLS: images without set dimensions, late-loading banners, cookie bars and fonts that swap after the text has drawn.

What makes a site slow on phones?

A phone has a slower processor and a less stable network than a laptop. On Singapore business sites the causes, in rough order of frequency:

1. Images uploaded at camera size. A 4,000-pixel hero photo displayed at 400 pixels still downloads in full. One image can be 3 to 5 MB; the fix is resizing, modern formats and lazy loading below the fold.
2. Page builder and theme scripts. Visual builders ship their whole feature set on every page. The lab Diagnostics line "Reduce unused JavaScript" shows how much. 500 KB to 2 MB is common on WordPress builder sites.
3. Plugins. Each one adds its own scripts and styles to every page, whether that page uses the feature or not. 20 plugins is 20 extra downloads.
4. Third-party embeds. Chat widgets, Facebook pixels, Google Maps iframes, YouTube embeds, review carousels. Each loads code from another server and runs it on the visitor's phone.
5. Server location and response time. A server in the United States adds round trips for a Singapore visitor. Shared hosting under load can take over 1 second to send the first byte. Check "Reduce initial server response time" in Diagnostics.
6. No content delivery network. Static files served from one machine instead of from an edge location near the visitor.
7. Web fonts. 4 weights of 2 font families is 8 files before text can render in its final form.
8. Render-blocking CSS and scripts in the head. The browser waits for them before painting anything.

A site built from static, prebuilt HTML served from a content delivery network avoids items 2, 3, 5, 6 and 8 by construction. That is the main speed difference between a coded site and a builder or CMS site, and it is why the Next.js vs WordPress comparison matters for speed as well as maintenance.

Does speed affect rankings and enquiries?

Rankings: yes, as one signal. Google's page experience documentation says Core Web Vitals are used by its ranking systems, that there is no single page experience signal, and that Google still seeks to show the most relevant content even when the page experience is poor. The practical reading is that speed breaks ties between relevant pages and will not rescue an irrelevant one.

Enquiries: this is where speed costs money directly. A visitor from a Google Ads click who waits 5 seconds on a phone has paid you nothing and cost you the click. Measure it yourself rather than relying on published industry averages:

• In analytics, compare enquiry rate for visits with LCP under 2.5 seconds against visits above 4 seconds. Most analytics tools can segment on page timing.
• Compare bounce rate on mobile against desktop for the same landing page. A large gap with the same traffic source points at speed.
• Check Search Console's Core Web Vitals report for the share of URLs rated Poor on mobile. If your service pages are in that group, your paid and organic traffic is landing on your slowest pages.

If the field data says Poor on the pages that receive enquiries, fixing speed is usually the cheapest conversion improvement available.

When does a slow site need a rebuild?

Fix when the causes are content and configuration. Rebuild when they are structural, meaning the slowness cannot be removed without removing the platform.

A rebuild on a static framework typically brings a business site from a field LCP of 4 to 6 seconds to under 1.5 seconds, because the page arrives as finished HTML and the scripts that caused the delay no longer exist. Treat that figure as an estimate; the result depends on the images and embeds the new site keeps. A redesign also has to carry every indexed URL across, which the website redesign guide covers.

Before any rebuild, record the current field numbers for the top 10 pages, so the new site can be shown to be faster.

What cense does

cense builds sites in Next.js, hosted on Vercel or Google Cloud with a content delivery network, HTTPS and no plugins, so pages arrive as prebuilt HTML. A free SEO report, sent on WhatsApp within 2 working days, includes the Core Web Vitals field numbers for an existing site. See website infrastructure.