Kief Studio

Google Already Grades Your Mobile Website. Most Small Business Sites Still Design for a Desk.

Build

  • Published
  • Updated
  • 10 min read
An S-shaped gold light path through scattered violet streaks, cover for a note on how Google grades mobile websites

TL;DR: Google indexes and ranks the mobile website, not the desktop one, and it grades page experience on real visits. In the 2025 Web Almanac only 48% of mobile websites passed all three Core Web Vitals, against 56% on desktop. Design and test on a phone first, then fix loading, layout jumps and slow taps.

Correction, October 2026: an earlier version of this note said a new report replaced Search Console's Mobile Usability report, quoted 2016 local search figures, and cited speed figures for hosted builders and AI visible pages that we could not trace to a primary source. We removed them, dated what remains, and labeled the Deloitte study as commissioned by Google.

Open Search Console. Desktop looks fine, the mobile website column is red, and Google is reading the red column. Your analytics may still show plenty of desktop visits this year. Both can be true. The wide desktop mockup is still the wrong source of truth for what Google's crawler and a customer on a lunch break actually see.

A lot of small business sites treat the phone as a CSS breakpoint, a narrower version of the real site. In practice the phone is a slower computer on a worse network, and it is where many local customers decide whether to call you. I want to walk through what Google measures on a mobile website, what the latest public data shows, and the fixes that matter most.

Does Google really grade the mobile website first?

Yes, and it has finished the switch. On October 31, 2023, Google's Search Central blog announced that "the trek to Mobile First Indexing is now complete." (Google Search Central Blog (opens in a new tab)) Its documentation is plain about what that means: "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central, mobile-first indexing (opens in a new tab))

So whatever your mobile website leaves out, Google may not see. The same page says "Make sure that your mobile site contains the same content as your desktop site," and asks you to "Use the same clear and meaningful headings on the mobile site as you do on the desktop site." It also warns: "Google won't load content that requires user interactions (for example, swiping, clicking, or typing) to load." Hiding services behind a tap that never fires for a crawler is a quiet way to drop them from search on your mobile website.

The phone is where most people are

Pew Research Center's 2026 survey found that "About nine-in-ten (91%)" U.S. adults own a smartphone, and that 16% are "smartphone-only" internet users, meaning "they own a smartphone but do not subscribe to a home broadband service." (Pew Research Center, mobile fact sheet (opens in a new tab)) For that group, your mobile website is your website.

What happened to the Mobile Usability report?

Google retired it. In April 2023 it announced: "starting December 1, 2023, we'll be retiring Search Console's 'Mobile Usability' report, the Mobile-Friendly Test tool and Mobile-Friendly Test API." It added that this "doesn't mean that mobile usability isn't important for success with Google Search." (Google Search Central Blog, April 2023 (opens in a new tab)) Our earlier note on how many sites fail Google's speed checks covers what changed in Search Console's page experience reports at the same time.

What does Google measure on a mobile website?

Google scores a mobile website on three field metrics called Core Web Vitals, taken from real Chrome users. Google's web.dev guidance sets the targets:

  • Largest Contentful Paint (LCP), loading: "LCP should occur within 2.5 seconds of when the page first starts loading."
  • Interaction to Next Paint (INP), responsiveness: pages "should have a INP of 200 milliseconds or less."
  • Cumulative Layout Shift (CLS), visual stability: pages "should maintain a CLS of 0.1. or less."

The measure is "the 75th percentile of page loads, segmented across mobile and desktop devices." (web.dev, Web Vitals (opens in a new tab)) INP is the newest, and it is where a mobile website most often lags behind desktop. Google's Chrome team wrote that it "will officially become a Core Web Vital and will replace First Input Delay on March 12," in a post dated January 31, 2024. (web.dev blog (opens in a new tab))

Field data beats the lab score

Search Console's Core Web Vitals report "shows how your pages perform, based on real world usage data," and each number covers "the last 28 days." It groups similar pages, and "the URL group's status is its most poorly performing metric." (Search Console Help, Core Web Vitals report (opens in a new tab)) One slow template can mark a whole group of mobile website pages Poor. A perfect lab score on your laptop does not change what real phones recorded on your mobile website.

How much does it count for ranking?

It counts, but it does not outrank relevance. Google's page experience documentation says "There is no single signal" and "Core Web Vitals are used by our ranking systems." It also says "Google Search always seeks to show the most relevant content, even if the page experience is sub-par," and that a great page experience can contribute to success when many helpful pages compete. Good scores alone will not put a page at the top, and Google warns that chasing a perfect score just for SEO may not be the best use of your time. (Google Search Central, page experience (opens in a new tab)) For most small businesses, the bigger cost of a slow mobile website is the customer who gives up, not a ranking drop.

How many mobile websites still fail?

About half. The HTTP Archive's 2025 Web Almanac, built on Chrome field data, found good Core Web Vitals on "48% for mobile websites and 56% for desktop websites" in 2025, up from 44% and 55% in 2024. (HTTP Archive, Web Almanac 2025, Performance (opens in a new tab)) Each metric tells its own story on a mobile website:

  • Loading is the usual miss. "On phone devices, 62% of websites have a good LCP, 25% need improvement, and 13% perform poorly," nearly double the 7% poor rate on desktop.
  • Taps lag on phones. "For phones, 77% of websites have good INP," against 97% on desktop.
  • Layout shift is the one phones win. 81% of mobile pages had good CLS, against 72% on desktop.

Popularity matters in a way small businesses should notice. Among the top 1,000 websites, 51% passed on mobile, falling "to 42% for the top 10,000 and 37% for the top 100,000." The busiest sites pay for performance work. The middle carries complexity with nobody assigned to it.

Interior pages matter too. On mobile, home pages passed 45% of the time and secondary pages 56%, yet mobile INP was better on home pages (80%) than on secondary pages (69%). (HTTP Archive, Web Almanac 2025 (opens in a new tab)) Quote forms, booking calendars and filters live on the pages that are supposed to convert.

Why does the same page run slower on a phone?

Because the phone is a slower machine and most sites keep getting heavier. The Almanac reports that "The median TBT on mobile increased to 1,916 milliseconds in 2025," up 58% from 1,209 milliseconds in 2024, while desktop sat at 92 milliseconds. (HTTP Archive, Web Almanac 2025 (opens in a new tab)) Total Blocking Time is a lab measure of how long scripts keep the page busy. Extra JavaScript hides on a laptop on office Wi-Fi. It shows up on an older phone on a cell signal.

The hero image is usually the problem

On a typical mobile website, images are the largest element: 76% of mobile pages have an image as that element, and JPG still accounts for 57% of those images. About 16% to 17% of pages lazy load that main image, and "62% of pages fail to set dimensions on at least one image" on mobile. (HTTP Archive, Web Almanac 2025 (opens in a new tab)) Lazy loading is useful below the fold. Chrome's own analysis found that "overuse can negatively affect performance," and that eagerly loading images in the first screen while lazy loading the rest gives fewer bytes and better vitals. (web.dev, LCP lazy loading (opens in a new tab))

Then something moves the button

A cookie banner, a chat bubble or an ad slot that loads late pushes the Call button down just as someone taps it. That is a layout shift, and on a mobile website it can turn a call into a mis-tap on the wrong link.

What does a slow mobile website cost a business?

Sales, in the cases that have been measured. Vodafone ran "an A/B test specifically focused on optimizing Web Vitals" and found "a 31% improvement in LCP led to 8% more sales, a 15% improvement in their lead to visit rate, and a 11% improvement in their cart to visit rate." (web.dev, Vodafone case study (opens in a new tab))

A broader study, Milliseconds Make Millions, was commissioned by Google and prepared by Deloitte, so read it as vendor commissioned research. Over a four week period it analysed mobile site data from retail, travel, luxury and lead generation brands. Based on "a 0.1s natural mobile site speed improvement," it reported that "Retail conversions increased by 8.4% and average order value increased by 9.2%," and that "Lead generation information pages bounce rate improved by 8.3%." (Deloitte, Milliseconds Make Millions (opens in a new tab)) Those are observed improvements across brands, not a controlled test, but they point the same way as the Vodafone result.

For a local service business, the moment is short. If your Business Profile wins the click and your mobile website takes four seconds to show anything, then jumps the button, the lead is lost after Google already sent it. Sales never hears from that person.

How do you fix a mobile website that fails?

Fix what is Poor before chasing a perfect score. Here is the order I would work in on a small business mobile website.

1. Read the field data

Open Search Console's Core Web Vitals report and pick the mobile tab. Note which URL groups are Poor and which metric failed. That list is your plan. If there is not enough traffic for field data, test key pages in PageSpeed Insights on mobile settings and treat the result as a rehearsal.

2. Fix the largest image on every template

  • Do not lazy load the main image in the first screen.
  • Serve it at the size a mobile website needs, in a modern format such as WebP.
  • Set width and height on every image so the page does not jump.

3. Cut the scripts that block taps

List every tag, pixel, widget and chat tool on the mobile website. Remove what nobody reads, delay what can wait, and test the booking and quote forms on a real phone after each change.

4. Keep the call button still

Reserve space for banners and late loading elements so nothing pushes the main actions. Put the phone number and the main button where a thumb finds them on the mobile website.

5. Match content across devices

Same headings, same text, same structured data on mobile and desktop. Use accordions or tabs if space is tight rather than deleting content from the mobile website.

6. Check again in a month

Field data covers 28 days, so changes to a mobile website take time to show. Recheck the report monthly. If you want a second view, LTFI's free site check grades security, search, DNS, email, speed and privacy basics (opens in a new tab), and I wrote a practical list of Core Web Vitals fixes (opens in a new tab) on my own site.

Frequently asked questions

Does Google rank my desktop site or my mobile website?

Your mobile website. Google uses the mobile version of a site's content, crawled with its smartphone agent, for indexing and ranking, and it completed that switch in 2023.

What are good Core Web Vitals scores?

LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of real page loads.

Where did the Mobile-Friendly Test go?

Google retired the Mobile-Friendly Test and the Mobile Usability report on December 1, 2023. It said mobile usability still matters and pointed to tools such as Lighthouse. The Core Web Vitals report in Search Console still shows field data.

Will fixing my mobile website move me to the top of Google?

Not by itself. Google says relevance comes first and that good scores alone will not put a page at the top. Speed helps most when many relevant pages compete, and it helps conversions either way.

Why does my site score well on desktop but fail on mobile?

Phones have slower processors and networks, so heavy scripts and large images hurt more. In the 2025 Web Almanac, median mobile blocking time was 1,916 milliseconds against 92 on desktop.

How long until Search Console shows my fixes?

The report uses the last 28 days of real visits, so expect about a month before the change shows fully.

Where we fit

We build websites starting from the phone, because that is the version Google reads and many customers use. Our custom web application work keeps sites fast, patched and yours after launch, hosted on dedicated infrastructure. With managed website operations, one studio runs hosting, pages, publishing, search and security, and watches uptime, speed and security so we can fix problems before visitors see them. Our SEO, AEO and GEO work keeps the site fast and crawlable, with pages that answer the questions your buyers ask.

First conversation is free. No commitment.

Tell us how your mobile website performs today

Related articles

  1. Build

    44% of Websites Fail Core Web Vitals in Real Visits. A Green Lab Score Won't Tell You

    Core Web Vitals come from 28 days of real visits, not a one-time lab test. What Google measures, why mobile scores lag, what small firms should fix first.

    Brian Gagne

  2. Build

    Does Google Grade Your Whole Site by Its Slowest Page? What Core Web Vitals Actually Measure

    Core Web Vitals are measured per page from real visits, and Search Console groups similar URLs. What Google documents, what it doesn't, and what to fix first.

    Brian Gagne

  3. Build

    The March 2026 Google Core Update: What Changed, What Didn't, and How a Small Business Recovers

    What the March 2026 Google core update changed and didn't, how to see if it hit your site in Search Console, and a 30-day recovery plan from Google's advice.

    Amelia Gagne