Imagine walking into a shop where nobody greets you for ten seconds and the lights flicker on slowly. Many of us would walk out. A slow website creates the same feeling — and online, the competitor is just one tap away. Website speed affects how many visitors stay, how many become customers, and how search engines evaluate your pages.
Google measures part of this experience through Core Web Vitals. Here is what they mean and how to improve them, explained without jargon.
Key takeaways
- Fast websites convert better and provide a better experience, especially on mobile.
- Core Web Vitals measure loading (LCP), responsiveness (INP) and visual stability (CLS).
- Compress and resize images, use modern formats like WebP and lazy-load below-the-fold media.
- Reduce heavy scripts, plugins and third-party widgets.
- Use good hosting, caching and a CDN where appropriate.
Why speed matters in India
Most Indian internet users browse on mobile phones, often mid-range devices on networks whose speed varies by location and time. A website that feels fast on a developer's laptop over office Wi-Fi may feel painfully slow on a phone in a crowded market. Designing for real conditions is essential.
The three Core Web Vitals
Largest Contentful Paint (LCP)
How quickly the main content — usually the biggest image or heading — appears. A good LCP is within about 2.5 seconds. Slow LCP is often caused by large images, slow servers or render-blocking files.
Interaction to Next Paint (INP)
How quickly the page responds when someone taps a button or link. Poor INP is usually caused by heavy JavaScript that keeps the browser busy.
Cumulative Layout Shift (CLS)
How much the page jumps around while loading. You have probably tried to tap a button just as an advert loaded and pushed it down. Good pages keep layout stable.
You can see your scores in Google Search Console and test individual pages with PageSpeed Insights.
Fix 1: Optimise images
Images are the most common cause of slow pages. Practical steps:
- Resize images to the size they are displayed — do not upload a 4000-pixel photo for a 400-pixel space.
- Compress them and use modern formats like WebP.
- Use responsive images so phones download smaller versions.
- Lazy-load images below the first screen.
- Always set width and height attributes to prevent layout shifts.
This website, for example, serves compressed WebP images in multiple sizes.
Fix 2: Reduce JavaScript
Many websites load large scripts for sliders, animations, chat widgets, trackers and page builders. Each adds weight and delays interaction. Ask whether every script is necessary. Remove unused plugins, delay non-essential scripts, and prefer simple CSS effects over heavy JavaScript.
Fix 3: Use lightweight video embeds
Embedding several YouTube videos directly can add a lot of loading weight. A better approach is a "facade": show a thumbnail image with a play button, and load the actual video player only when the visitor clicks. The videos on this website work this way.
Fix 4: Choose good hosting and enable caching
A slow server delays everything. Reasonable hosting, server-side caching, browser caching headers and compression (Gzip or Brotli) make a significant difference. For mostly static websites, serving pre-built HTML pages is extremely fast.
Fix 5: Load fonts efficiently
Custom fonts make sites beautiful but can delay text. Use a small number of font files, host them yourself where possible, preload the most important ones and use font-display settings so text appears immediately.
Fix 6: Prevent layout shifts
Reserve space for images, videos, ads and embeds. Avoid inserting banners above existing content after the page loads. Stable pages feel more professional.
Fix 7: Keep pages focused
Long home pages with dozens of sections, multiple sliders and auto-playing media slow everything down. Prioritise what matters most to visitors and move the rest to separate pages.
How to test properly
- Use PageSpeed Insights for lab and real-user data.
- Check Core Web Vitals reports in Search Console for site-wide patterns.
- Test on a real mid-range phone using mobile data.
Focus first on templates used by many pages — home, service pages, blog posts — because fixes there improve the whole site.
Speed and conversions
Speed is not only about SEO. Faster pages generally see lower bounce rates and higher conversions. For landing pages that receive paid traffic, speed improvements directly reduce your cost per lead. See building a landing page that converts.
Core Web Vitals explained
| Metric | What it measures | Common causes of poor scores | Fixes |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How quickly the main content appears | Large images, slow server, render-blocking files | Optimise hero image, preload it, faster hosting |
| INP (Interaction to Next Paint) | How quickly the page responds to taps and clicks | Heavy JavaScript | Reduce and defer scripts |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | Images without dimensions, late-loading ads or fonts | Set width/height, reserve space, use font-display swap |
Quick wins
Convert images to WebP and serve appropriate sizes, add width and height attributes, preload the main hero image and fonts, remove unused plugins and scripts, enable compression and browser caching, and avoid autoplay videos above the fold. These steps alone often transform mobile performance.
Testing regularly
Test key pages with performance tools after every major change and monitor real-user data in Search Console. Speed tends to degrade gradually as new features are added, so make performance checks part of every update.
A 7-step speed improvement plan
- Test your key pages in PageSpeed Insights and note LCP, INP and CLS for mobile.
- Compress and resize images, convert them to WebP or AVIF and add width and height attributes.
- Preload the main hero image and use fetchpriority high for the largest visible element.
- Remove unused plugins, scripts and third-party widgets that slow the page.
- Defer non-critical JavaScript and inline only the critical CSS.
- Enable caching and a content delivery network where your hosting allows.
- Retest after each change and monitor the Core Web Vitals report over the following weeks.
Frequently asked questions
Does speed affect rankings?
Page experience, including speed, is one of many signals. More importantly, speed affects conversions and user satisfaction.
What is a good LCP?
Generally, loading the main content within about 2.5 seconds is considered good.
Do website builders produce slow sites?
Some do, especially with heavy themes and plugins. Choose lightweight themes and test performance.
Should I use a CDN?
A CDN helps serve files faster to visitors in different regions, which is useful for international audiences.
Does site speed affect conversions?
Yes. Faster pages generally keep visitors engaged and reduce abandonment, especially on mobile.
What is a good LCP score?
Google's guidance treats an LCP of 2.5 seconds or less as good for most visits.
Do Core Web Vitals directly affect rankings?
They are part of Google's page experience signals. Content relevance matters more, but speed improves user experience and conversions.
Is shared hosting too slow?
Not necessarily. A well-optimised site on good shared hosting can perform well; upgrade when traffic or needs grow.
Final thought
Speed is respect for your visitor's time. Compress images, trim scripts, use efficient embeds, host well and keep layouts stable. These changes are usually inexpensive and benefit rankings, user experience and sales together. For a full audit, read the technical SEO checklist or contact DND Teams. More on my approach at the tech expert page.
