If your business website loads slowly on a mobile phone in Lajpat Nagar or Karol Bagh, you are likely losing customers before they ever read your offer. Google measures this experience through a set of signals called Core Web Vitals, and in 2026 they remain an important part of how search results are ranked and how visitors judge your site. This guide is a practical, prioritised fix list written for small businesses in Delhi NCR, from a kirana store with an online catalogue to a boutique clinic or a local manufacturer.

What Core Web Vitals Actually Measure

Core Web Vitals are three user-experience metrics that Google tracks using real-world data from Chrome users:

• Largest Contentful Paint (LCP): How long it takes for the main content of a page, usually a hero image or a large heading, to become visible. Aim for under 2.5 seconds.
• Interaction to Next Paint (INP): How quickly the page responds when someone taps a button, opens a menu or types into a form. Aim for under 200 milliseconds.
• Cumulative Layout Shift (CLS): How much the page content jumps around while loading. Aim for a score under 0.1.

These numbers are measured at the 75th percentile of your visitors, which means that a good score requires most of your real users, not just your own test on a fast office connection, to have a good experience. That is an important point for Delhi businesses, where many visitors browse on mid-range Android phones over variable 4G or 5G networks.

Start by Measuring, Not Guessing

Before changing anything, record where you stand. Use these free tools:

• PageSpeed Insights gives both lab data and field data from real Chrome users for your URL.
• Google Search Console has a Core Web Vitals report that groups your pages into good, needs improvement and poor categories.
• Chrome DevTools Lighthouse lets you test a page and see exactly which resources are slowing it down.

Note the scores for your homepage, your top service or product page and your contact page. These three pages usually matter most for enquiries and sales. If Search Console shows no field data for a page, it is usually because the page has too little traffic, so focus on the pages people actually visit.

Fix List Part One: Improving Largest Contentful Paint

1. Compress and resize your hero images

The most common cause of poor LCP for small business sites is an oversized banner photo. A 4000-pixel-wide image straight from a phone camera may be several megabytes, yet it is displayed at 800 pixels on screen. Resize images to the maximum width they will actually be shown, then convert them to WebP or AVIF format. Most modern content management systems and free tools can do this in a few clicks.

2. Mark your main image as a priority

Lazy loading is excellent for images further down the page, but it should not be applied to the hero image that appears above the fold. Remove the lazy-loading attribute from that image and, where your platform allows it, add a high fetch priority hint so the browser loads it first.

3. Reduce server response time

If your site is on a cheap shared hosting plan with a server far away from your audience, the first byte of every page can take a long time to arrive. Choose hosting with a server location in India or the wider Asia-Pacific region, enable server-side caching and make sure your site runs on a supported version of PHP or whichever language your platform uses.

4. Remove render-blocking scripts and fonts

Many small business sites load a long list of plugins, chat widgets, tracking pixels and font files before showing anything. Audit your site and remove anything you no longer use. Load non-essential scripts after the main content, and limit yourself to two or three font weights rather than loading every variant of a typeface.

Fix List Part Two: Improving Interaction to Next Paint

5. Trim JavaScript on your pages

INP is often poor because the browser is busy running heavy JavaScript when a visitor taps something. Look at your plugin list. A single website may be loading slider libraries, analytics tools, social feeds and popup builders all at once. Keep only what earns its place, and prefer simple HTML and CSS for static sections like service descriptions.

6. Make menus and forms responsive

Test your mobile menu, enquiry form and WhatsApp or call buttons on an actual budget Android device. If tapping feels delayed, a plugin or a heavy script is likely the cause. Simplify the interaction, or replace a complicated booking widget with a clean form that submits quickly.

7. Break up long tasks

If a page runs a large calculation or a long script on load, the browser cannot respond to input until it finishes. Ask your developer to split long tasks into smaller pieces, or to defer work until the visitor is idle.

Fix List Part Three: Stopping Cumulative Layout Shift

8. Set width and height on images and embeds

When an image loads without reserved space, everything below it jumps downward. Always define the width and height attributes on images, videos and iframes, or use an aspect-ratio setting in your CSS so the browser knows how much room to leave.

9. Reserve space for ads, banners and pop-ups

Cookie banners, promotional strips and late-loading ads are frequent sources of layout shift. Place them in fixed containers with reserved height, or position them as overlays that do not push the main content around.

10. Avoid injecting content above existing content

Notification bars, sticky offers and dynamically inserted testimonials should not push visible text out of place after the page has rendered. Load them in a way that does not move what the visitor is already reading.

Choosing Help in Delhi

Many of these fixes can be handled by a competent in-house team or a freelance developer. If your website runs on a platform you do not fully control, or if the audit reveals structural problems in your theme or codebase, it is sensible to bring in an agency that understands both performance engineering and the search and conversion side of your business. When you speak to any provider, ask them to show you before-and-after PageSpeed data from past work and to explain what they changed, rather than accepting a single screenshot of a high score.

A Realistic Timeline

Start with the measurements this week, then tackle the image and hosting fixes first, since they usually deliver the biggest gains for the least effort. Retest after each change, and allow a few weeks for Search Console's field data to reflect your improvements, because it is based on real visitor experience over a rolling period. Performance is not a one-off project. Review your scores each quarter, especially after adding new plugins, new product pages or new promotional campaigns.

Core Web Vitals will not single-handedly make a Delhi shop or service firm the top result for every search, but a fast, stable and responsive site removes friction for the