Website Speed for Small Businesses in India: A Plain Guide
Check and speed up your small business website in India: Google's three Core Web Vitals targets, the Search Console report, and what to fix first.
A slow website loses people before they read a single line. Google measures how real visitors experience your pages with three Core Web Vitals, and you can check all three for free. This guide explains the three numbers in plain words, how to find the pages that need work in Search Console, and the fixes that usually help a small business site first. It does not promise rankings. Google says speed is one part of page experience, not the whole story.
The three numbers Google uses
Core Web Vitals are three measurements of what a visitor feels on a page:
- Largest Contentful Paint (LCP) is how soon the main picture or text block appears. Good is 2.5 seconds or less. Poor is over 4 seconds.
- Interaction to Next Paint (INP) is how quickly the page responds after a tap, click or key press. Good is 200 milliseconds or less. Poor is over 500 milliseconds.
- Cumulative Layout Shift (CLS) is how much things jump around while the page loads. Good is 0.1 or less. Poor is over 0.25.
Google judges each number at the 75th percentile of real page loads, and it does this separately for mobile and desktop. In practice, three out of four visitors on a device should get a good experience. One fast visit from the owner on office Wi-Fi does not count.
Older guides still mention First Input Delay. Google replaced it with INP as a Core Web Vital in March 2024, so measure INP today.
Does speed affect rankings?
Google's own page experience guidance says there is no single "page experience signal". Core Web Vitals are one of the things its ranking systems look at, and Google recommends good scores for success in Search and for a good user experience. Google also says that good scores in Search Console or third-party tools do not guarantee top rankings, and that chasing a perfect score just for SEO may not be the best use of your time.
Google further says it always tries to show the most relevant content, even when the page experience is weak. So the order of work is clear: your page must answer the search well, and then it must load and respond quickly enough that people stay, call or send a WhatsApp message. For a shop or service business, the speed fix is mostly about not losing the visitors you already earn.
Find the problem pages in Search Console
Start with the Core Web Vitals report under Experience in Google Search Console. It groups your URLs as Poor, Needs improvement or Good, separately for mobile and desktop. Google's advice for the report is simple:
- Fix everything labelled Poor first.
- Prioritise the issues that affect the most URLs, or the most important URLs such as your homepage and enquiry pages.
- Once a fix is made, open the issue and start tracking it, so you can see whether the field data has recovered.
Google's Search Console guidance also says that URLs in each group are sorted by impressions, so the top URLs affect the group status the most. If your site is new or has little traffic, the report may show little or no data. That is normal for a small site. Then you test the important pages by hand, as described below.
Our Search Console basics guide shows where to find the report if you have not opened it yet.
Test one page at a time in PageSpeed Insights
The Search Console report shows a group of pages. PageSpeed Insights, a free Google tool, tests one page at a time. Test four pages at minimum: your homepage, your main service or product page, one blog post and your contact or booking page.
PageSpeed Insights shows two kinds of data:
- Field data comes from real Chrome users who visited the page. This is the same kind of data Google uses for the Core Web Vitals report.
- Lab data is a test that runs on demand under set conditions. It gives the diagnostics that help you find the cause.
If field data is missing for a page, that page has too few real visits to report. The lab data is still useful. In the diagnostics, look for the "Largest Contentful Paint element". It names the picture or text block that the page waits for, which is usually the first thing to fix.
Ignore the 0 to 100 score as a target. It is a helper. The three Core Web Vitals numbers are the target.
Fix the main picture first (LCP)
Most small business sites are slow to show the first screen because of large images. These fixes usually help the most:
- Resize before you upload. A photo from a phone is often several thousand pixels wide. Upload it at roughly the size it is shown on screen. The file name and alt text steps are in our image SEO guide.
- Compress the file. Most image tools and site builders can reduce file size without a visible drop in quality. Check the logo and product photos closely, because heavy compression can make text and fine details blurry.
- Do not lazy load the first picture. Lazy loading means an image loads only when it nears the screen. It helps for pictures further down the page. Applied to the top banner, it delays the very element that LCP measures.
- Remove the heavy homepage slider. Auto-playing sliders with large videos are a common cause of a slow first screen. A single clear photo with a short headline loads faster and is easier to read on a phone.
Google's Search Console help page gives two useful guidelines for page weight: keep a page and all its resources under about 500 KB where you can, and keep the number of resources on a mobile page to about 50. Treat these as sensible targets, not hard rules.
Stop taps lagging (INP)
INP is high when the page is busy with scripts while a visitor tries to tap a menu or button. Small business sites pick up scripts over the years, and most of them are no longer needed:
- Audit your apps and widgets. Old chat widgets, popups from a campaign that ended, tracking tags nobody uses, and plugins you installed once and forgot can all run on every visit.
- Delay heavy embeds. Map embeds and video players are heavy. Many site builders can load them only when a visitor scrolls near them or clicks to play.
- Test on a real phone. Open the site on mobile data and tap the menu, a button and a form field. A noticeable pause means the page is busy.
Remove one script at a time and test again. If the enquiry form or the WhatsApp button stops working, put back the script that does that job.
Stop things jumping (CLS)
A page jumps when content appears without space reserved for it. The most common cause on small sites is an image without set dimensions:
- Set the width and height for every image and embed, or let your site builder keep the aspect ratio. The browser then knows how much space to leave before the picture arrives.
- Reserve room for banners. A cookie bar, a promotion strip or a late-loading ad pushed into the top of the page after load will move the text under the visitor's finger. Give it a fixed place, or show it at the bottom.
- Avoid late insertions above content. If a button moves just as a visitor taps it, the CLS score takes the hit, and so does trust.
Check the server and the redirects
If the server takes a long time to respond, every other fix waits for it. You can ask your hosting provider how long the first response takes, or check the timing in the diagnostics. A content delivery network (CDN) keeps copies of your static files on servers closer to visitors. Cloudflare offers a free plan for this. Whether it helps your site depends on how the site is built, so test before and after.
Redirects also add time. Each redirect is an extra round trip before the page loads. If your old service pages redirect to new ones, and those redirect again, update the links to point straight to the final page. Our internal links guide covers how to find pages that are hard to reach.
A simple 30-day routine
You do not need a developer for the first round. Work in four short weeks and change one thing at a time, so you know what helped:
- Week 1: Open the Search Console Core Web Vitals report. Write down the Poor URLs for mobile and for desktop.
- Week 2: Test your four key pages in PageSpeed Insights. Note the LCP element and the top two diagnostics for each page.
- Week 3: Fix one thing on each page: resize the largest image, remove one unused script, or set the size of the banner.
- Week 4: Test the same pages again, check the phone experience yourself, and start tracking the fixed issues in Search Console.
Keep a short log with the date, the page and the change. When the numbers move, you will know which change caused it.
Mistakes to avoid
- Chasing a perfect lab score while real visitors on mobile still wait. Field data is the target.
- Compressing images until they look poor. A blurry product photo costs more sales than a slightly slower load.
- Removing the phone number, WhatsApp button or enquiry form to save time. Those are the parts that bring customers. Keep them, and make them fast.
- Changing the theme, the host and the images in the same week. You will not know which change worked.
Frequently asked questions
What is a good speed for a small business website? Google judges the three Core Web Vitals, not one overall score. For most real visitors, aim for LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile.
Will fixing my site speed put me at the top of Google? Not by itself. Google says there is no single page experience signal and that good Core Web Vitals do not guarantee top rankings. Relevant, useful content still matters most. A faster site helps people stay and act once they arrive.
Why does Search Console show no data for my website? The report needs enough real visits from Chrome users. Small sites often have too little traffic to show data. Test your important pages in PageSpeed Insights instead, and use the lab diagnostics to find the cause.
Is First Input Delay still a metric? No. Google replaced First Input Delay with Interaction to Next Paint (INP) as a Core Web Vital in March 2024. Use INP when you check responsiveness.
Do I need a developer to fix this? Many fixes are simple: resizing images, removing unused apps and scripts, and setting the size of banners and pictures. Server settings, theme code and redirect rules may need your developer or your site builder's support team.
Are the free tools enough? Yes for measuring. PageSpeed Insights and the Search Console report are both free. Check each change on a real phone, because fixes depend on your site builder and host.
Next step
Speed is one part of a website that gets found, trusted and used. Start with the free checks in this guide. If you want a simple first step to see how the rest of your digital marketing fits together, look at the free trials. When you want help from our team with your website or your Google profile, see the services. There is no promise of results with any of this, only a clearer plan.
Ready for the next step? Compare services and real prices, then order in a minute.
Browse services