Mobile-First Indexing for Irish Business Websites

During our morning operations review last month, I was looking at a cluster of support queries that had come in over the previous two weeks. Rankings have slipped. Nothing changed. A competitor is now appearing above us. Three separate customers. Three different businesses. The same underlying question each time.

I see this pattern regularly enough that it has its own shape in my head. A site that was well-positioned drifts down the page. The business owner opens it on their laptop, everything looks right, and the mystery deepens. We run a mobile performance check and the picture becomes clear almost immediately.

Consider what this typically looks like. An accountancy firm in Limerick, trading for nearly twenty years, a website that served them reliably for the best part of five years. They had never needed to think much about it. Google surfaced them consistently for the searches that mattered. Then gradually, a newer competitor started appearing above them. The newer firm's site had a Largest Contentful Paint on mobile of around 1.9 seconds. The Limerick firm's was 4.3 seconds. The difference was not content quality, domain authority, or backlink count. It was what Google has been measuring as its primary ranking signal since October 2023: mobile performance.

Not desktop performance. Mobile performance.

What Google Changed in October 2023

Google's shift to mobile-first indexing was not sudden. It began as a limited experiment in 2016, expanded gradually from 2018, and reached full completion in October 2023. ^[1] What full implementation means is precise: Googlebot, when it crawls and indexes your site, presents itself as a smartphone. It sees your mobile experience. It measures your mobile performance. It uses what it finds on mobile to determine how your site ranks in search results.

For all searches. Not just searches conducted on phones. A solicitor searching for accounting software on their office laptop sees results ranked on mobile performance signals. The desktop version of each site in those results is not what determined their position. Google made a single index based on mobile crawls and applies it to every query.

Page speed became a ranking factor for mobile searches in July 2018 ^[2]. Core Web Vitals, Google's specific set of performance measurements covering loading speed, visual stability, and responsiveness, joined the ranking algorithm in 2021 ^[3]. October 2023 completing mobile-first indexing brought these together. The practical outcome is this: your ranking in Google is now the product of your mobile experience, measured by mobile-specific metrics, applied to every search regardless of the device the searcher is using. Most business owners I deal with are not aware of this yet — and I will admit I assumed awareness had filtered through more broadly by now. Based on what comes into our operations queue, it has not.

The Three Ways It Affects Your Ranking

Understanding what mobile-first indexing means in practice takes less than a minute to explain. The operational implications take longer to sit with.

Your ranking reflects mobile performance even for desktop searches. This is the one that surprises people most. A potential customer on a laptop searching for "accountant Limerick" gets results ranked by mobile performance signals. The desktop experience of those sites is not what determined their position. Your ranking is set by how your site performs on a phone, regardless of the device your potential customers use to find you.

Content only visible on desktop is invisible to Google. Some older WordPress themes collapse sections on smaller screens, hide text behind toggles, or strip elements from mobile layouts. If a section of your site only renders on desktop, Google does not index it. Keywords in that content do not contribute to your ranking. This matters most for service descriptions, location details, and any text that is doing the heavy SEO work on a page.

Speed is tested on mobile hardware, not your broadband connection. Google's lab-based speed testing simulates a mid-range Android device on a 4G connection ^[4]. Your site loading in 1.2 seconds on a laptop connected to fast home broadband tells you very little about how Google assesses it. Under mobile testing conditions, that same site might load in 3.8 seconds. It is the 3.8 seconds going into ranking calculations. Checking your site's speed from a desktop browser at home is not a useful proxy for what Google actually measures.

What the Numbers Tell Us

The performance data from HTTP Archive, which tracks Core Web Vitals across the web at significant scale, shows a consistent pattern. Around 46 in 100 WordPress sites pass all Core Web Vitals measurements on mobile ^[5]. That figure has improved over the past few years — it was noticeably lower in 2022 and 2023. But it still means roughly half of WordPress business sites are below Google's mobile performance benchmarks.

Our detailed look at why Irish WordPress sites fail Google's mobile performance tests covers the specific failure rates in more depth. The pattern aligns with the global picture: image weight and unoptimised server response times are the two most consistent causes of failure on mobile.

The metric that fails most often is Largest Contentful Paint, which measures how quickly the main visible content of a page appears to the user. Google's "Good" threshold is 2.5 seconds. WordPress sites running on shared hosting with heavy themes and multiple plugins regularly produce LCP readings of 4 to 6 seconds on mobile testing. That is not a borderline fail. The Limerick accountancy firm we looked at earlier was in that range. Their content, their structure, their on-page SEO — all fine. Their mobile LCP was the problem.

The performance gap between mobile-optimised and unoptimised sites is what Google now measures. Your desktop speed is not in the calculation.

How to Check Whether Your Site Has a Problem

The most direct tool is Google's own PageSpeed Insights. Enter your URL, run the analysis, and go directly to the mobile results — not the desktop tab. Look at the Core Web Vitals section. You want three green indicators: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. If any of these show amber or red on mobile, that is directly affecting your position in search results.

If your site has enough traffic, PageSpeed Insights shows "Field Data" from real Chrome users at the top of the results. That is more valuable than the lab scores further down the page. Field data reflects what actual visitors experienced. Google uses Chrome User Experience Report data for ranking when it is available for your site ^[3]. The lab data helps diagnose the issue; the field data is what counts for ranking.

The second check is content parity. Open your site on a phone — a phone specifically, not a tablet — and review:

Service descriptions and about content
Contact details and location information
Any text-heavy sections doing SEO work on important pages

If something visible on desktop is absent on mobile, Google is not indexing it. For modern responsive WordPress themes this is rarely an issue. For older themes or certain page builders, hidden mobile content is a real and common problem.

One practical note: even after fixing mobile performance issues, ranking improvements do not arrive the next day. Google recrawls sites on schedules that vary by site size and activity. For a typical small business site, a meaningful recrawl after technical changes can take anywhere from a few days to a few weeks. Verify the fix in PageSpeed Insights and Google Search Console, then wait for the crawl cycle before drawing conclusions about ranking impact.

The Infrastructure Layer

Mobile performance is not purely a front-end problem. The server that delivers your site has a direct impact on the metrics Google measures on every mobile crawl, and this is where infrastructure choices make a material difference. Time to First Byte — how quickly your server starts responding to a request — is measured by Googlebot on each crawl. On shared hosting environments under load, TTFB regularly exceeds 800ms to over a second. On an Nginx-based managed hosting environment with FastCGI page caching, cached pages are served in under 200ms. That difference feeds directly into LCP and into Google's server response assessment.

Redis object caching reduces database query overhead for pages that are not fully cacheable. Without it, every visit to a dynamic WordPress page triggers a sequence of database queries. With it, frequently accessed data is held in memory and returned faster. Web60's infrastructure — Nginx, PHP-FPM, Redis object caching, and FastCGI page caching on enterprise-grade Irish servers — is structured around these performance characteristics. If you want to understand what's running underneath your site, our technology overview covers the full stack. For a complete walkthrough of how WordPress performance optimisation works in practice, the complete WordPress performance guide for Irish business owners goes through every layer.

One concession worth making: if you are running a high-volume e-commerce operation with a dedicated development team and specific infrastructure requirements, enterprise-tier hosting with dedicated resources and custom server configuration may offer headroom that standard managed hosting does not. That is a legitimate requirement at that scale. For a typical Irish business site with a few hundred to a few thousand visitors per week, the question is whether your hosting is configured to deliver mobile performance at all. Many shared hosting environments are not.

Conclusion

October 2023 completed a multi-year shift in how Google determines where your website sits in search results. The mobile version of your site is now the primary signal. Not the desktop version. The mobile one.

The sites that have benefited most since then are the ones that happened to be on infrastructure and themes that deliver solid mobile performance. The sites that have slipped are the ones where the desktop experience was the priority and mobile was an afterthought — technically responsive, but slow and sometimes content-incomplete.

Checking where you stand takes ten minutes. Google PageSpeed Insights, mobile tab, Core Web Vitals section. If you are passing on mobile, you are clear of this particular problem. If you are failing, you now know what to look at first.

Frequently Asked Questions

Does mobile-first indexing mean I need a separate mobile website?

No. A responsive WordPress theme that adapts to different screen sizes is the standard approach, and Google prefers it. What matters is that the responsive version loads quickly and shows the same content as the desktop version. A separate mobile subdomain is outdated practice and can create content parity and indexing complications.

Does Google rank my site differently for mobile searches versus desktop searches?

No. Since October 2023, Google uses a single index built from mobile crawls. All search results — regardless of whether the searcher is on a phone, a tablet, or a laptop — are ranked based on that mobile-first index. Your mobile performance affects your position on every device.

My website looks fine on my phone. Does that mean my mobile performance is good?

Not necessarily. Visually correct and technically performant are different things. A site can display without obvious issues on mobile while still failing Core Web Vitals, particularly Largest Contentful Paint, which measures how quickly the main visual content appears. Google's assessment is performance-based. Use PageSpeed Insights on the mobile tab to check the actual metrics rather than relying on visual inspection.

How long does it take to see ranking improvements after fixing mobile performance issues?

There is no fixed timeline. Google recrawls sites on a schedule that depends on your site's size, activity, and historical crawl frequency. For a typical small business site, meaningful changes in ranking after a technical fix can take anywhere from a few days to several weeks. Verify the fix in PageSpeed Insights and Google Search Console, then allow a full crawl cycle before expecting to see ranking movement.