# How to make your business website fast and mobile-friendly

> What Core Web Vitals mean, how to test your site with PageSpeed Insights, what slows it down on phones and the fixes you can make without a developer.

- Canonical URL: https://businesswebsite.ai/blog/fast-mobile-friendly-website
- Section: Blog
- Language: en
- Published: 2026-11-13
- Publisher: Website (https://businesswebsite.ai)

## Key facts

- Author: Benjamin
- Reading time: 11 minutes

Most people meet your business on a phone first. They tap your link in a search result, on a map or in a social media bio, often on mobile data, and decide in seconds whether to stay. If the screen stays blank, or the "Call now" button jumps away just as they tap it, they go back and pick the next result.

Speed is one of the few parts of a website you can measure for free, and most fixes don't need a developer. Here is what Google checks in 2026, how to test your own pages and what to fix first.

> **In short:** A fast, mobile-friendly website shows its main content within 2.5 seconds, reacts to a tap within 200 milliseconds and doesn't shift around while it loads (a layout shift score of 0.1 or less). Those are Google's Core Web Vitals. Test your key pages in PageSpeed Insights on mobile, then fix the usual culprits: oversized images, too many fonts and scripts, slow hosting and pop-ups.

## Why speed and mobile matter for a small business

### Google judges the phone version of your site

Google "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking". This is called mobile-first indexing, and Google's [mobile-first indexing best practices](https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing) recommend responsive design: one page that adapts its layout to every screen size.

Keep the content identical on both versions. If your phone layout hides the price list or drops the photo gallery to look cleaner, Google may never see that content, and it warns that a mobile page with less content can expect some traffic loss. Move content into accordions or tabs instead of removing it.

### Most web traffic comes from phones

In October 2026, mobile devices accounted for 59.9% of web page views worldwide, against 38.51% for desktops and 1.59% for tablets, according to [Statcounter](https://gs.statcounter.com/platform-market-share/desktop-mobile-tablet/worldwide). Your own visitor statistics show the split for your business.

### Slow pages lose visitors and sales

When Google's Chrome team analyzed millions of page impressions in 2020, it found that visitors were 24% less likely to abandon a page load (leaving before any content appeared) when the site met the Core Web Vitals thresholds of the time ([The Science Behind Web Vitals](https://blog.chromium.org/2020/05/the-science-behind-web-vitals.html)).

In a 2021 A/B test, [Vodafone](https://web.dev/case-studies/vodafone) compared two versions of a landing page that looked and worked exactly the same. The version with a 31% better Largest Contentful Paint brought 8% more sales, and one of its fixes was simply resizing the hero image.

### Speed helps with Google, but it is no shortcut

Core Web Vitals are used by Google's ranking systems, but Google warns that good results in Search Console or other tools don't guarantee a top position ([Understanding page experience](https://developers.google.com/search/docs/appearance/page-experience)). Google "always seeks to show the most relevant content, even if the page experience is sub-par". Speed helps most when many pages answer the same search well, and chasing a perfect score just for SEO "may not be the best use of your time".

So aim for "good", then put your energy into useful content and your [Google Business Profile](https://businesswebsite.ai/blog/google-business-profile-local-seo).

## What are Core Web Vitals?

Core Web Vitals are three measurements of how a page feels to real visitors: loading, responsiveness and visual stability ([Web Vitals](https://web.dev/articles/vitals)). Picture a bakery's homepage on a phone:

- **Largest Contentful Paint (LCP):** the moment the biggest element appears, usually the photo of the cakes or the main headline.
- **Interaction to Next Paint (INP):** the delay between tapping "Order a cake" and the page visibly reacting.
- **Cumulative Layout Shift (CLS):** how much things jump unexpectedly, like text sliding down when a late banner appears.

| Metric | What it measures | Good | Needs improvement | Poor |
| --- | --- | --- | --- | --- |
| LCP | When the main content appears | 2.5 s or less | over 2.5 s, up to 4 s | over 4 s |
| INP | The delay after a tap, click or key press | 200 ms or less | over 200 ms, up to 500 ms | over 500 ms |
| CLS | How much the layout shifts unexpectedly | 0.1 or less | over 0.1, up to 0.25 | over 0.25 |

The targets apply to the 75th percentile of page loads, measured separately on mobile and desktop: at least three out of four visits should be good. A page passes the Core Web Vitals assessment only when all three metrics are good, or LCP and CLS when there isn't enough INP data yet ([About PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about)). A fast photo doesn't make up for a page that jumps.

## How to test your website speed

### Step 1: run PageSpeed Insights on mobile

Paste a page address into [PageSpeed Insights](https://pagespeed.web.dev/) and look at the mobile results first, since that is the version Google indexes. You get two kinds of data:

- **Real-user data** from the Chrome User Experience Report: how Chrome users experienced the page over the previous 28 days, with a pass or fail verdict for Core Web Vitals.
- **Lab diagnostics** from a tool called Lighthouse: one simulated load on a mid-tier phone over a mobile network, with a performance score (90 or above is good) and audits that explain what to improve.

Small and new sites often get no real-user data, because the Chrome report only covers public pages with enough visits; the tool then shows data for your whole domain, or none. A lab score that moves a few points between runs is normal. Test the pages people actually use, such as your services and contact page, not just the homepage.

### Step 2: open the Core Web Vitals report in Search Console

Once your site is in Search Console (our guide on [getting your website on Google](https://businesswebsite.ai/blog/how-to-get-your-website-on-google) shows how), the [Core Web Vitals report](https://support.google.com/webmasters/answer/9205520) shows real-user data for the whole site. It groups similar pages, separates mobile from desktop and labels each group Poor, Need improvement or Good, based on its worst metric.

Only indexed pages appear, and a group needs a minimum amount of data, so a small site may see "No data available". After you fix an issue, the Start Tracking button runs a 28-day check of whether it is really gone.

### Step 3: test it on a real phone

Open your site on your own phone, on mobile data and in a private tab. Tap the menu, the phone number and the contact form, and watch for jumps, tiny text and buttons that are hard to hit.

## Field data vs lab data: which numbers count?

The two halves of a PageSpeed Insights report often disagree, and both can be right. Field data records real visits on all kinds of devices and connections. Lab data is one simulated load on one device with fixed network settings, so, as Google puts it, "the values may differ".

| Question | Field data (real users) | Lab data (simulated) |
| --- | --- | --- |
| Where it comes from | Chrome users who opted in | One Lighthouse test |
| Time covered | The previous 28 days | The moment you run it |
| What it tells you | Whether visitors get a good experience | Why the page is slow |

Field data tells you whether there is a problem, lab data helps you find out why, and good lab data "does not necessarily mean real-user experiences will also be good". Since field data covers a rolling 28 days, an improvement shows up gradually, not the next morning.

## The usual culprits that slow a small business site

In the HTTP Archive's [Web Almanac 2025](https://almanac.httparchive.org/en/2025/page-weight), the median mobile home page weighed 2.56 MB. Images were the biggest part (911 KB), ahead of JavaScript (632 KB) and fonts (122 KB). For comparison, Google's Search Console help suggests less than 500 KB for a page and all its resources, and at most 50 resources per page on mobile.

Weight shows in the results. Among mobile home pages with real-user data, 57% of those under 1 MB passed all three Core Web Vitals, against 30% of those weighing 5 MB or more.

### Oversized images

A photo straight from a phone or camera is usually far larger than the space it fills on screen, and a homepage slider can load five of them before anyone scrolls. The element LCP measures is typically an image, often your hero photo, which makes it the first thing to optimize.

### Too many fonts

Every font family, and every weight of it, is another file to download. Custom web fonts "can add several hundred KB if multiple weights (bold, italic, light) are used", the Web Almanac notes.

### Too many scripts and widgets

Chat bubbles, social media feeds, review badges, embedded maps and videos, a tracking pixel left over from an old ad campaign: each one loads code from another server. The phone has to process and run that code, and "on a low-end smartphone, this 'weight' can freeze the screen for several seconds". That is the kind of delay INP picks up when a tap seems to do nothing.

### Slow hosting

PageSpeed Insights also reports Time to First Byte (TTFB), the wait for the server's first response: 0.8 seconds or less is good, more than 1.8 seconds is poor. If your TTFB is poor, compressing images won't fix it. The server may be far from your customers, build every page from a database on each visit, or simply be underpowered.

### Pop-ups that cover the page

Google says intrusive interstitials may frustrate visitors and erode their trust, and that they make your content hard for search engines to understand, "which may lead to poor search performance" ([Avoid intrusive interstitials and dialogs](https://developers.google.com/search/docs/appearance/avoid-intrusive-interstitials)). It recommends small banners instead, and treats legally required overlays, such as an age check, as an exception. A banner that appears late and pushes the content down also counts against your CLS.

## Fixes you can make without a developer

Start with images, since they are the biggest part of a typical page, then work down the list:

1. **Shrink photos before uploading.** Resize each one to no larger than it will appear on a big screen and save it as JPEG or WebP. Use one strong hero photo instead of a slider.
2. **Use one or two fonts,** with only the weights you need, such as regular and bold. System fonts, already installed on the device, need no download at all.
3. **Remove the widgets you don't need.** Replace an embedded social feed with a link, and keep the map on the contact page.
4. **Swap pop-ups for slim banners,** shown only after the visitor has seen your content.
5. **Check the server.** If TTFB is poor on several pages, ask your host why, or move to a platform that handles hosting for you.
6. **Make the mobile page complete.** Same text, prices and opening hours as on desktop, a tappable phone number and text you can read without zooming. Our guide on [how to write website content](https://businesswebsite.ai/blog/how-to-write-website-content) helps you keep it short.
7. **Re-test and track.** Run PageSpeed Insights after each change, then start tracking the fix in Search Console and give real-user data a few weeks.

## Checklist for a fast, mobile-friendly site

| Check | Where to look | Target |
| --- | --- | --- |
| LCP | PageSpeed Insights, mobile, real-user data | 2.5 s or less |
| INP | PageSpeed Insights, real-user data | 200 ms or less |
| CLS | PageSpeed Insights, real-user data | 0.1 or less |
| TTFB | PageSpeed Insights | 0.8 s or less |
| Performance score | PageSpeed Insights, mobile lab test | 90 or above, but not a goal in itself |
| Page size | Your photos and files | Under 500 KB per page |
| Content on mobile | Your phone next to your laptop | The same as on desktop |
| Pop-ups | Your phone, arriving from a search | No full-screen overlays |
| Secure connection (HTTPS) | The padlock in the browser | On every page |

## When rebuilding beats repairing

If your site runs on an old theme you can't change, Google's mobile guide suggests finding a new mobile-friendly theme, and a rebuild can be quicker than a long list of fixes.

Our AI website builder publishes every page [mobile-friendly](https://businesswebsite.ai/features/mobile-friendly-websites) and [fast](https://businesswebsite.ai/features/fast-hosting), with [free SSL](https://businesswebsite.ai/features/free-ssl) and a title, a description and structured data on each page. You can [import your existing site](https://businesswebsite.ai/import) from Wix, WordPress, Shopify, Squarespace, Webflow and other platforms to rebuild it, then keep editing [from your phone](https://businesswebsite.ai/features/edit-from-phone). Nobody can honestly promise you a ranking, but the mobile layout and the hosting are handled for you. Starting from zero? Our [guide to creating a business website](https://businesswebsite.ai/blog/how-to-create-a-business-website) covers every step.

## Frequently asked questions

### What is a good PageSpeed Insights score?

A score of 90 or above is good, 50 to 89 needs improvement and below 50 is poor. The score comes from one simulated test, so use it as a diagnostic. What counts more is whether your real-user data passes the Core Web Vitals assessment.

### Does website speed affect Google rankings?

Yes, but less than many people think. Core Web Vitals are used by Google's ranking systems, yet relevance comes first and good scores don't guarantee a top position. Speed helps most when other pages answer the same search equally well.

### Why does PageSpeed Insights show no real-user data for my site?

Real-user data comes from Chrome users who opted in, and a page must be public, indexable and visited often enough to be included. New and small sites often don't qualify yet, so rely on the lab results and a test on your own phone.

### Why is my site slower on mobile than on desktop?

Heavy pages need processing power and memory that low-end phones lack, whatever the connection speed. PageSpeed Insights also tests mobile on a simulated mid-tier phone over a mobile network, a tougher setting than its desktop test on a wired connection.

### Do I need a separate mobile version of my website?

No. Google recommends responsive design: the same page at the same address, with a layout that adapts to each screen. It is the easiest setup to maintain and keeps your content identical on phones and computers, which is what mobile-first indexing expects.

## Sources

1. [Mobile-first indexing best practices](https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing), Google Search Central, 2025.
2. [Understanding page experience in Google Search results](https://developers.google.com/search/docs/appearance/page-experience), Google Search Central, 2026.
3. [Avoid intrusive interstitials and dialogs](https://developers.google.com/search/docs/appearance/avoid-intrusive-interstitials), Google Search Central, 2025.
4. [Web Vitals](https://web.dev/articles/vitals), web.dev, 2024.
5. [About PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about), Google for Developers, 2024.
6. [Core Web Vitals report](https://support.google.com/webmasters/answer/9205520), Google Search Console Help, 2026.
7. [Page Weight, Web Almanac 2025](https://almanac.httparchive.org/en/2025/page-weight), HTTP Archive, 2026.
8. [Desktop vs Mobile vs Tablet Market Share Worldwide](https://gs.statcounter.com/platform-market-share/desktop-mobile-tablet/worldwide), Statcounter Global Stats, 2026.
9. [Vodafone: A 31% improvement in LCP increased sales by 8%](https://web.dev/case-studies/vodafone), web.dev, 2021.
10. [The Science Behind Web Vitals](https://blog.chromium.org/2020/05/the-science-behind-web-vitals.html), Chromium Blog, 2020.

---

Source: https://businesswebsite.ai/blog/fast-mobile-friendly-website