Your website is live. It loads , eventually. On your office WiFi, on your laptop, it feels fine. But your potential client in Thika is on Safaricom 4G on a mid-range Android phone, and your site takes nine seconds to appear. They have already left. Page speed is not a technical problem that only developers need to think about. It is a client acquisition problem. In Kenya, where over 85% of internet traffic comes through mobile devices and most of that traffic runs on 4G networks with real-world variability, a slow website is not just annoying, it is invisible. Google ranks it lower, visitors leave before reading a word, and the business that shows up faster gets the inquiry. This guide explains what Core Web Vitals Kenya are, how they affect your search ranking in the country specifically, how they affect whether visitors trust you enough to make contact, and what you can do about it — with or without a developer.
| Does any of this apply to you? • Your website has been live for months but your search ranking hasn’t improved • You’ve been told your site is ‘fine’ but it feels slow on your phone • Visitors arrive but leave quickly — and you don’t know why • You’re investing in content or ads but the results don’t match the effort • A competitor with a worse-looking site is ranking above you on Google |
| When to Read This Guide This guide is for you if: • Your website has a PageSpeed Insights score below 70 on mobile and you’re not sure what that means or what to do about it • Your organic traffic has been declining and you’ve ruled out content as the cause • You’re building or redesigning a website and want to avoid the performance mistakes most Kenyan sites make • You want to understand whether speed is why visitors aren’t converting, before you invest in more marketing • You work with a developer and want to speak intelligently about what actually matters for ranking and trust |
| This Guide Is Best For Service business owners, digital marketers, and web designers in Kenya who want to understand how Google measures page experience and what it means for search visibility and client trust. You don’t need a technical background. You need to be willing to check your scores and take action on what you find. This guide is NOT for: developers looking for code-level implementation detail — it covers principles and priorities, not syntax. It does not cover e-commerce-specific performance optimisation. |
| Definition: Core Web Vitals Core Web Vitals are three specific performance metrics that Google uses to measure how a real user experiences a webpage , how quickly the main content loads, how quickly the page responds to a tap or click, and how stable the layout is while loading. They are part of Google’s Page Experience ranking signal, which means they directly affect where your pages appear in search results. As of 2025, the three metrics are: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). |
Google introduced these metrics because it had a problem: its own search results were sending users to pages that ranked well on content but delivered a poor experience. Pages that were slow to load, unresponsive to touch, or that shifted their layout mid-load were causing users to bounce before engaging. Core Web Vitals were Google’s way of measuring that experience with specific, consistent numbers — so that page experience could become a quantifiable ranking signal, not just a vague idea.
The important framing: Core Web Vitals are not the most important ranking factor. Content relevance and quality still dominate. But when two pages have similar content and authority, the one with better Core Web Vitals tends to rank higher. And in Kenya’s competitive digital market, where content quality across similar service businesses is often similar, page performance is frequently the tiebreaker.
You don’t need to understand the technical implementation of these metrics to make decisions about them. But you do need to know what each one is measuring, because the fix for each one is different.
LCP measures the time from when a user clicks your link to when the largest visible element on the page , usually your hero image, your headline, or a featured photo , appears fully on screen. It answers the question every visitor is asking when they click: ‘Is this going to show me what I came for?’ On a fast connection with a well-built site, LCP happens in under 2.5 seconds. On a slow site accessed via 4G in Nairobi traffic, it can take 8–12 seconds. The visitor has already decided to leave before the second second is up if nothing has appeared.
| LCP Score | Good | Needs Work | Poor |
| Time to load main content | Under 2.5 seconds | 2.5 – 4 seconds | Over 4 seconds |
INP replaced an older metric called FID in 2024. Where FID only measured the delay on the very first tap or click, INP measures responsiveness across the entire session , every tap, every scroll, every form input. A page with poor INP feels sluggish. The visitor taps a button and nothing happens for half a second. They tap again. The page jumps. They leave. This matters particularly on lower-spec Android devices, which are the primary device category in Kenya. A page that feels fast on a high-end smartphone can feel broken on a KSh 15,000 handset — and that handset is where most of your potential clients are.
| INP Score | Good | Needs Work | Poor |
| Time for page to respond to tap/click | Under 200ms | 200 – 500ms | Over 500ms |
CLS measures how much the visible content moves unexpectedly as the page loads. You know this experience: you’re about to tap a button and the page shifts, and you accidentally tap something else. Or you’re reading a paragraph and it suddenly jumps down the screen because an image loaded above it. CLS is scored as a number from 0 to 1. Below 0.1 is good. Above 0.25 is poor. Layout shift destroys trust specifically because it feels broken — even if the page eventually settles, the visitor’s first impression is that the site is unstable. In a market where clients are already cautious about online service providers, a visually unstable site reinforces doubt before a single word is read.
| CLS Score | Good | Needs Work | Poor |
| Layout shift score (lower is better) | Under 0.1 | 0.1 – 0.25 | Over 0.25 |
Google uses Core Web Vitals as part of its Page Experience signal. When it evaluates two pages with comparable content and backlink authority , which is most competitive searches at a local level — it uses page experience as a tiebreaker. The page that delivers a better experience to real users, measured through Chrome browser data, gets the edge.
Here is what the data shows: as of 2025, only about 33–47% of websites globally pass all three Core Web Vitals thresholds. In Kenya, where many service business sites are built on unoptimised WordPress themes with cheap shared hosting, the pass rate is likely lower. That creates a real opportunity — if your site meets these standards and your competitors’ sites don’t, you have a technical ranking advantage that compounds over time.
Google collects Core Web Vitals data from real Chrome browser users visiting your pages — this is called field data, as opposed to lab data from a tool like PageSpeed Insights. If your field data shows poor scores consistently, Google records that real users are having a poor experience on your pages, and factors that into its ranking calculation.
The ranking effect is not dramatic if your scores move from ‘good’ to ‘excellent.’ The effect is most significant when moving from ‘poor’ to ‘good’ — particularly on mobile. Google has confirmed that mobile scores are what count for rankings, because of its mobile-first indexing policy. Your desktop site could be fast and beautiful, and it would not save a slow mobile site from ranking penalties.
Kenya’s digital landscape creates specific performance challenges that generic guides ignore. Most Kenyan internet users are on Safaricom or Airtel 4G networks — not fibre. Network speeds on 4G in Kenya average around 15–25 Mbps in urban areas but can drop significantly in peri-urban areas like Thika, Eldoret, or Nakuru. A page that loads in 2 seconds on fibre in Westlands can take 6–8 seconds on a congested 4G connection in Mombasa’s Old Town.
The devices matter too. The dominant price range for smartphones in Kenya is KSh 8,000–20,000. These devices have processors significantly slower than a modern flagship phone and less RAM. A JavaScript-heavy site that renders smoothly on a Samsung Galaxy S24 can freeze and lag on a Tecno Spark or Infinix Hot. Google’s performance testing takes device capability into account — your real-world scores on Kenyan network conditions and device types are what determine your ranking.
The practical implication: test your site’s performance on the device and network your actual clients use, not on your office equipment. This connects directly to the conversion and trust mechanics covered in how to get more clients with a high-converting website in Kenya , speed is the foundation that all other conversion work sits on.
Rankings get you in front of people. Trust is what makes them contact you. Page speed affects both, but the mechanisms are different, and both matter for your bottom line.
When a potential client clicks through to your site from Google, they are making a series of rapid unconscious judgments. The first and most immediate one is: does this feel like a real, maintained business? A site that loads instantly — where the main content appears within two seconds — signals competence before a word is read. A site that takes five seconds while showing a blank screen signals the opposite.
Research consistently shows that as page load time increases from one second to five seconds, the probability of a visitor leaving immediately increases by over 90%. That is not a rounding error. A five-second site loses the majority of the visitors it worked to attract before they’ve read the headline.
In Kenya, there is a specific reason layout shift hurts more than in other markets: visitors are more cautious about digital interactions following years of exposure to scam websites and unreliable online services. A page that shifts, jumps, or renders inconsistently triggers an instinctive ‘something is wrong here’ response — the same response that makes someone close a suspicious-looking M-Pesa prompt.
A stable, fast-loading page signals: this business is professional, their digital presence is maintained, they are worth trusting. This is not a subtle effect. It operates before the visitor has read your headline, seen your testimonials, or evaluated your services. Speed and stability are the first trust audit your site undergoes.
There is a specific client type that slow sites lose at the worst possible moment: the visitor who has already decided they are interested and clicks through to your contact page. They’ve read your services. They’ve seen your testimonials. They are ready to reach out.
If your contact page loads slowly, or the form takes three seconds to respond after they tap the submit button, or the page shifts just as they’re entering their phone number — that friction is enough to lose the inquiry. Not because the client is impatient. Because in a market where alternatives are one Google search away, any added difficulty tips the decision.
No , and understanding the correct relationship matters so you don’t over-invest in performance optimisation at the expense of content quality.
Google has been explicit: content relevance and quality are still the dominant ranking factors. A fast site with poor content will not outrank a slower site with genuinely useful, well-structured content. John Mueller of Google has stated directly that being faster than competitors doesn’t automatically move you to position one in search results.
The accurate framing is this: Core Web Vitals are a tiebreaker, not a leapfrog. When your content is strong and your technical performance is also strong, you beat competitors whose content is equally strong but whose performance is poor. If your content is weaker, fixing your Core Web Vitals won’t compensate for that.
| Scenario | Impact on Ranking |
| Strong content + poor Core Web Vitals | Ranks, but loses to equally strong content with good performance |
| Weak content + excellent Core Web Vitals | Still ranks poorly — performance doesn’t override content quality |
| Strong content + good Core Web Vitals | Best position — content earns the ranking, performance keeps it |
| Improving from ‘poor’ to ‘good’ scores | Meaningful ranking improvement, especially on mobile |
| Improving from ‘good’ to ‘excellent’ scores | Diminishing returns — content investment pays more at this point |
The practical implication for a service business in Kenya: fix your site’s performance until you pass the ‘good’ threshold on all three metrics. After that, invest in content quality, structure, and authority. Chasing ‘excellent’ performance scores while your content is thin is the wrong sequence.
You do not need a developer or a paid tool to get a starting picture of where your site stands. These are the tools that give you actionable data.
Go to Google and search ‘PageSpeed Insights.’ Enter your URL and run the test. The tool returns a score from 0 to 100 for both mobile and desktop, along with specific scores for each Core Web Vitals metric. Always look at the mobile score first , that is what Google uses for ranking. A score below 50 on mobile is a serious problem. Between 50 and 89 is acceptable but improvable. Above 90 is good.
One important note: PageSpeed Insights runs a lab test — it simulates performance on a standardised device and connection. It gives you a directionally accurate picture but may not reflect exactly what a Kenyan user on a mid-range Android on Safaricom 4G experiences. Use it as your baseline diagnostic, not your final measurement.
If your site is registered with Google Search Console (and it should be , it’s free), go to Experience > Core Web Vitals. This shows you field data — actual scores from real Chrome users visiting your pages. This is the data Google uses for ranking decisions. Search Console shows your pages grouped into three categories: Good, Needs Improvement, and Poor. Pages in the Poor category are being penalised. Start with those.
For a Kenya-specific reality check: take your phone, switch from WiFi to data, and navigate to your site. Time how long it takes for the main content to appear. Try tapping buttons and form fields. Notice if anything shifts or jumps. This is the experience your client in Nakuru or Kisumu is having. If your site feels slow to you on your own data connection, it is slow. That experience is more reliable than any score as a business decision signal.
Most performance problems on Kenyan service business websites come from the same small set of causes. Knowing what they are helps you have an informed conversation with your developer , or fix the fixable ones yourself.
This is the most common cause of slow LCP on Kenyan sites. A full-resolution photo uploaded directly from a smartphone — 3–6MB in size — will take 8–15 seconds to load on 4G. The same image optimised to WebP format at the right display size should be under 200KB. That difference is the difference between a 2-second LCP and a 10-second one. You do not need a developer to fix this. Free tools like Squoosh (squoosh.app) and TinyPNG compress images without noticeable quality loss. If you use WordPress, plugins like ShortPixel or Smush do this automatically. This is a DO FIRST fix.
Many Kenyan websites are hosted on shared servers that handle hundreds of sites simultaneously. When server resources are stretched, your site takes longer to deliver its first response to any visitor’s browser , this is called Time to First Byte (TTFB), and it directly affects LCP. A server that takes more than 600ms to respond before the page even starts loading is adding a floor to your performance that image compression alone cannot fix.
If your PageSpeed Insights report shows ‘Reduce initial server response time’ as a high-impact recommendation, your hosting is likely the bottleneck. Moving from shared hosting to a VPS or managed WordPress hosting — Cloudways, SiteGround, or a local Kenyan provider with SSD servers, typically cuts TTFB by 60–80%.
Every plugin on a WordPress site loads additional code. Every third-party script , Google Analytics, Facebook Pixel, live chat widgets, popup tools , adds requests the browser must complete before the page finishes loading. A site with 25 active plugins and five third-party marketing scripts can add 3–6 seconds to its load time on mobile. The fix is auditing what is actually necessary. If you have a live chat widget that nobody uses, it is slowing your site for every visitor without providing value. If you have two analytics tools running simultaneously, one is redundant. Removing unnecessary scripts is often the fastest performance win after image compression.
Many Kenyan websites use premium WordPress themes marketed as ‘multi-purpose’ , Divi, Avada, WPBakery, which load large amounts of CSS and JavaScript even when those features are not being used. A homepage built with a heavy page builder can require 30+ separate file requests and 2–4MB of data before showing anything. This does not mean you must abandon your theme. But if your PageSpeed score is consistently poor despite fixing images and plugins, the theme itself is often the remaining ceiling. Switching to a lightweight theme like Generatepress or Kadence, or having a developer implement critical CSS loading, can dramatically improve LCP and INP.
Caching stores a pre-built version of your pages so that when a visitor requests them, the server doesn’t have to rebuild everything from scratch each time. Without caching, every page load is a fresh database query, slower and more server-intensive. With caching properly configured, returning visitors and search engine bots see near-instant page delivery.
On WordPress, caching plugins like WP Rocket or the free W3 Total Cache handle this. Most quality hosting providers also offer server-level caching. If your site has no caching configured, enabling it is one of the highest-impact changes you can make in under an hour.
| Not sure what’s slowing your site down , or where to start? We run a free performance audit for service business websites in Kenya. You’ll get a clear report of your Core Web Vitals scores, what’s causing the problems, and which fixes will move the needle most. |
The honest answer depends on two things: which specific problems your site has, and how comfortable you are in your site’s backend. Some fixes are genuinely doable by a non-technical site owner in an afternoon. Others require a developer.
| Fix | DIY or Developer? | Estimated Time |
| Compress and resize existing images | DIY — use Squoosh or TinyPNG | 1–3 hours |
| Install a caching plugin on WordPress | DIY — install WP Rocket or W3 Total Cache | 30–60 minutes |
| Audit and remove unnecessary plugins | DIY — deactivate one at a time, test after each | 1–2 hours |
| Upgrade hosting to VPS or managed WordPress | DIY — account setup, developer to migrate | Half day |
| Switch to a lightweight WordPress theme | Developer recommended — risk of layout breakage | 1–3 days |
| Fix layout shift from missing image dimensions | Developer — requires code edits | 2–4 hours |
| Optimise JavaScript loading order (defer/async) | Developer — requires theme/plugin knowledge | Half day |
| Implement critical CSS / above-the-fold loading | Developer — significant performance gain | 1–2 days |
The most important thing is to start with the DIY fixes before calling a developer. Compressed images and caching alone can take a site from a PageSpeed score of 35 to 65 without touching code. Only bring in a developer after you’ve done what you can yourself — because then you’re paying for expertise on the genuinely complex problems, not for things you could have handled.
Worth it compared to what , that’s the right question. Compared to running Facebook ads to a slow site, fixing your page speed first is always the better investment. You’re paying to send traffic to a page that loses the majority of visitors before they engage. The ad spend is wasted. Compared to investing in new content, the answer depends on your starting point. If your PageSpeed score is below 50 on mobile, fixing performance will have a more direct impact on traffic and conversion than a new blog post. If your score is already above 70, content investment pays more.
A 100-millisecond improvement in page load time correlates with a 7% improvement in conversion rate. That is a well-documented finding across multiple industry studies. For a service business getting 10 inquiries a month, a 7% improvement means less than one extra inquiry. But a site moving from 8 seconds load time to 2 seconds is not a 100ms improvement — it is a 6,000ms improvement, and the conversion impact is proportionally larger.
More directly for Kenya: only 33–47% of websites globally pass all three Core Web Vitals thresholds. In a competitive local search — ‘web designer Nairobi,’ ‘accountant Westlands,’ ‘marketing consultant Mombasa’ , if your competitors’ sites are in the majority that fail these thresholds and yours passes, you hold a measurable ranking advantage that does not require ongoing spend to maintain. It is a one-time investment that continues paying.
If your site has fewer than 50 organic visitors per month, fixing Core Web Vitals will produce minimal ranking improvement — there is not enough field data for Google to register your scores. At that traffic level, your priority is visibility: content, local SEO, Google Business Profile optimisation. Come back to performance once traffic is established.
If your site has zero conversions despite good traffic, the problem may be messaging and structure rather than speed. Test your site’s load time on mobile first. If it loads in under three seconds and still doesn’t convert, the issue is likely what the page says and how it’s organised, not how fast it appears.
The article how to get more clients with a high-converting website in Kenya covers the messaging and structure side of that problem in detail — starting with the diagnostic framework for identifying whether speed or conversion is your primary issue.
There are two separate timelines to understand: the timeline for your scores to improve, and the timeline for that improvement to show in rankings. Score improvement is immediate. The moment you compress your images, install caching, and remove unnecessary scripts, your PageSpeed Insights score changes. That happens the next time anyone runs the test.
Ranking improvement takes longer. Google collects field data from real Chrome users over a rolling 28-day window. After you make changes, it takes approximately four to eight weeks for your updated real-world scores to be fully reflected in the data Google uses for ranking. Then ranking adjustments follow , typically over one to three months, depending on how competitive your keywords are and how significant the performance improvement was.
The honest expectation: if your site goes from poor to good across all three metrics, expect to see meaningful ranking movement within two to four months. If your site was already acceptable and you’re making marginal improvements, ranking movement may be minimal because you’re already getting the benefit of passing the thresholds.
This confusion is common and worth clearing up precisely, because they measure different things and acting on the wrong one wastes effort. Your PageSpeed Insights score (0–100) is a lab score , it measures performance on a simulated device under controlled conditions, using Google’s Lighthouse tool. It is useful as a diagnostic, it tells you what’s slowing your site and gives you a standardised comparison point. But it is not directly what Google uses for ranking.
Core Web Vitals field data, drawn from real Chrome users on real devices on real networks — is what Google uses for ranking. A site can have a PageSpeed score of 55 but passing Core Web Vitals field data if its real-world visitors happen to be mostly on fast connections. A site can have a PageSpeed score of 80 but failing field data if its visitors are predominantly on slow mobile connections. The practical implication: check both. Use PageSpeed Insights to find and fix problems. Use Google Search Console’s Core Web Vitals report to verify your field data status , that’s the number that determines your ranking treatment.
Yes , and this is a dimension most guides on Core Web Vitals ignore entirely.
AI-powered search tools , Google’s AI Overviews, Perplexity, ChatGPT with search — increasingly surface web pages in their answers. When an AI tool is deciding which pages to cite or summarise, it is not just evaluating content quality. It is also evaluating whether the page is accessible, crawlable, and reliably deliverable. A page that times out, delivers errors, or is blocked by scripts that prevent clean content extraction is less likely to be cited.
More directly: AI systems deprioritise pages that deliver poor user experiences. A 2024 analysis noted that pages failing Core Web Vitals may be deprioritised in AI-generated summaries even if their content quality is high — because user experience has become a credibility signal that indicates whether a source deserves citation. This means your Core Web Vitals now affect not just your position in the blue-link results, but your visibility in the AI-generated answers that are appearing above those results.
For a full picture of how to position your business to appear in AI-generated search recommendations, read how to make your business appear in AI-generated search recommendations — the MarginsEye GEO Playbook — it covers the content and technical signals that AI search engines use to select which pages to surface and cite.
Use this checklist against your own PageSpeed Insights report. The DO FIRST items have the highest impact for the least technical effort. Do not move to later items until the earlier ones are done.
| ☐ | DO FIRST | Run PageSpeed Insights on your homepage — mobile score. Note which Core Web Vitals are failing |
| ☐ | DO FIRST | Compress all images on your site — use Squoosh or TinyPNG, target under 200KB per image |
| ☐ | DO FIRST | Check your Google Search Console Core Web Vitals report — identify which pages are in ‘Poor’ status |
| ☐ | DO FIRST | Install a caching plugin if using WordPress — WP Rocket (paid) or W3 Total Cache (free) |
| ☐ | DO FIRST | Test your site on your phone on mobile data — note load time and any layout shift |
| ☐ | DO NEXT | Audit your WordPress plugins — deactivate anything you don’t actively use and test performance |
| ☐ | DO NEXT | Review your hosting — if TTFB is above 600ms in PageSpeed, consider upgrading from shared hosting |
| ☐ | DO NEXT | Remove or defer non-essential third-party scripts — Facebook Pixel, chat widgets, unnecessary tracking |
| ☐ | DO NEXT | Add explicit width and height attributes to all images — prevents layout shift (CLS fix) |
| ☐ | DO NEXT | Enable a CDN (Content Delivery Network) — Cloudflare’s free tier significantly improves delivery speed in Kenya |
| ☐ | WHEN READY | Evaluate your theme — if scores remain poor after the above, the theme is the bottleneck |
| ☐ | WHEN READY | Implement lazy loading for images and videos below the fold |
| ☐ | WHEN READY | Work with a developer on JavaScript optimisation — defer non-critical scripts |
| ☐ | WHEN READY | Set up ongoing monitoring in Google Search Console — review Core Web Vitals monthly |
Google’s Core Web Vitals field data requires a meaningful volume of Chrome user visits to generate. If your site has very low organic traffic — fewer than 50 sessions per month — Google may not have enough field data to assign you a Core Web Vitals status. In that case, fixing your performance scores matters less than fixing your visibility: content, local SEO, and Google Business Profile completeness are the priority.
A fast site with content that doesn’t match what people are searching for will not rank well. If your PageSpeed score is already above 70 on mobile and you are still not ranking for your target keywords, the problem is content relevance, not performance. Adding more content that directly answers the questions your clients are searching for — specific, structured, useful — will do more for ranking than optimising from 72 to 85 on PageSpeed.
If your site loads fast and still doesn’t get inquiries, page speed is not the issue. A fast page that doesn’t communicate clearly who it’s for and what it does for them will still lose visitors. Verify load time first — under three seconds on mobile data. If that’s met and conversion is still poor, the problem is messaging, structure, and trust signals.
| The Critical Distinction Core Web Vitals affect two things: how Google ranks your pages, and how visitors experience your site. They do not affect whether your messaging is clear, whether your offer is compelling, or whether your prices are right. Do not let a focus on technical performance distract from the commercial fundamentals. |
Page speed and Core Web Vitals are not the most important factor in your website’s ability to rank and convert — but they are the floor everything else sits on. A fast, stable, responsive site doesn’t guarantee clients. A slow, unstable one actively loses them at every stage: before they read a word, while they’re evaluating you, and at the moment they’re about to contact you.
In Kenya’s specific context — 4G networks, mid-range Android devices, a market where trust is hard-won and easily lost — performance is more consequential than most guides written for Western audiences acknowledge. Your PageSpeed score on mobile data, on a KSh 15,000 handset, is the performance environment that determines your ranking and your visitor’s experience.
The fix sequence is clear:
If you can do steps one through four yourself, do them this week. The sites that rank consistently in Kenya are not always the ones with the best content. They are frequently the ones where someone made the effort to fix what their competitors didn’t bother to fix.
If you want a clear picture of where your site stands — and exactly which fixes will move the needle most — that’s the starting point of every performance project we take on.
| You now know what Core Web Vitals are and which ones your site is likely failing. If you want to know specifically what’s slowing your site, which fixes are worth your time, and how your performance compares to competitors ranking above you in Kenya — book a free 20-minute session. We’ll look at your actual scores, tell you what they mean, and give you a prioritised action plan. |
That question usually means the structure decision hasn’t been made clearly yet , and building before that clarity is where most website budgets get wasted. Book a free 30-minute strategy call. We’ll map exactly which structure your business needs right now and why.
FAQ
Core Web Vitals are three metrics used by Google to measure how your website feels to real users:
- How fast it loads (LCP)
- How quickly it responds (INP)
- How stable it is while loading (CLS)
They exist because ranking content alone wasn’t enough , user experience had to be measurable.
Yes , but as a tiebreaker, not the main driver.
If two websites have similar content quality and authority, the one with better Core Web Vitals will usually rank higher.
They don’t replace content , they decide between equals.
You’re aiming for:
LCP: under 2.5 seconds
INP: under 200 milliseconds
CLS: under 0.1
Anything outside that range starts costing you rankings and user trust.
Start with two tools:
- Google PageSpeed Insights → shows what’s slowing your site
- Google Search Console → shows real user data (what Google actually uses)
Check mobile first. That’s what matters.
Because you’re testing in the wrong environment.
Your users are on:
- 4G (not fibre)
- Mid-range Android devices
- Variable network conditions
What feels fast in your office isn’t what they experience. That gap is where you lose clients.
Three things, consistently:
- Large, uncompressed images
- Cheap shared hosting
- Too many plugins/scripts
Fixing just these can move a site from “poor” to “usable” without touching code.
Kenya’s Leading AI SEO & Website Design Agency | Fast, Personalized Results for Local Businesses
(254) 745 521670
Copyright © 2026 MD – AI-Powered Digital Growth in Nairobi, Kenya. All Rights Reserved.