How Caching Quietly Decides Whether Your Site Feels Instant
Caching decides whether return visitors get an instant page or a slow reload, and misconfiguring it quietly hurts rankings and conversions.
Caching is the single setting most likely to make your site feel fast or slow to repeat visitors, and most Indian businesses never look at it. Get it wrong and your site can score badly on speed tests even if the code itself is fine. Get it right and you remove exactly the kind of repeated network round-trips that variable Indian mobile networks handle worst.
This post explains what caching actually does, why it matters more on second visits than first, what it costs you if it's misconfigured, and why it matters even more in India specifically.
What caching actually does
At its core, HTTP caching means a browser or an intermediary server stores a copy of a response and reuses it instead of fetching it again. As MDN's caching documentation puts it, "since there is no need to deliver the request to the origin server, the closer the client and cache are, the faster the response will be." It also cuts server load, because "when a response is reusable, the origin server does not need to process the request" — no routing, no session lookup, no database query.
MDN describes two kinds of caches that matter for any business site:
- Private caches — tied to one browser on one device. This is what most people mean by "browser cache."
- Shared caches — proxies and CDNs sitting between the browser and your server, serving many users.
Both are controlled through the Cache-Control HTTP header, which "holds directives in both requests and responses that control caching in browsers and shared caches (e.g., Proxies, CDNs)."
One thing site owners often get wrong: assuming that if they never set a caching header, nothing gets cached. Google's own performance guidance corrects this directly — "leaving out the Cache-Control response header does not disable HTTP caching — instead, browsers effectively guess what type of caching behavior makes the most sense for a given type of content," per web.dev's HTTP cache guide. Google's recommendation is to configure headers explicitly rather than let each browser guess differently.
Why caching affects second visits, not first
This is the part that trips people up when they look at their own analytics. Caching's biggest payoff shows up on repeat visits, not the very first load. Web.dev's explainer on service worker and HTTP caching is explicit: "the first time a browser loads a web page and related resources, it stores these resources in its HTTP cache" — the saving comes on the next visit.
That has a direct consequence for how you should read your own Core Web Vitals scores. Per web.dev's guide on caching and Core Web Vitals, "performance metrics like Core Web Vitals include all loads, not just the 1st load — when users load a site a second time, their browser will use resources inside its HTTP cache to help make that load faster." So a site can look mediocre in aggregate speed scores purely because caching is misconfigured for returning visitors — a subscriber checking their account, a customer coming back to complete checkout, someone re-reading a page you emailed them — even though the underlying code is perfectly fine.
There's a security wrinkle here too, for anything personalized: logged-in dashboards, account pages, saved carts. Google's guidance on this is specific: for personalized pages, "set Cache-Control: private" so that intermediary caches — shared proxies or CDNs — don't accidentally serve one user's personal data to another, according to web.dev's HTTP cache security guide. This is a question worth asking any developer building a logged-in area for you directly.
How caching connects to rankings and conversions
Google confirmed in 2018 that page speed became a mobile search ranking factor, starting that July. But the scope is narrower than most people assume — Google was clear that the change "will only affect pages that deliver the slowest experience to users and will only affect a small percentage of queries," and that strong, relevant content can still outrank a slower page.
On conversions, the industry data tells a consistent direction but disagrees badly on exact numbers, which is worth knowing before you repeat any of these stats to a client or a boss.
| Claim | Figure | Source |
|---|---|---|
| Walmart, load time vs. conversion | 2% conversion increase per 1-second improvement | Colorlib |
| Core Web Vitals pass rate | 33% of sites pass all three | Colorlib |
| Core Web Vitals pass rate (2025, CrUX data) | 48% mobile, 56% desktop | HTTP Archive Web Almanac, via Christoph Olivier Consulting |
| Core Web Vitals pass rate (alternate report) | 49.1% | Mean.ceo |
| Core Web Vitals pass rate (alternate report) | 55.9% | Big Red Jelly |
| Amazon, latency vs. sales | 1% sales loss per 100ms latency | Rework resources |
| Portent, load time vs. conversion rate | 3.05% at 1 second, down to 0.41% at 5 seconds | Mean.ceo |
Notice the spread — Core Web Vitals pass rates alone range from 33% to 56% depending on which report you read, which likely comes down to different CrUX data vintages and device mixes rather than any single source being wrong. Christoph Olivier Consulting flags a more fundamental caveat directly: "those conversion studies are correlational — they observe relationships between speed and behavior, not controlled causal experiments." So treat the Walmart and Amazon figures as directionally useful, not as numbers you can plug into your own revenue model.
The honest summary: everyone agrees speed (and caching, as a major lever on speed) affects rankings and conversions in the same direction. Nobody agrees on the exact magnitude, and most of the underlying studies are observational.
Why this matters more in India specifically
Indian mobile networks have improved fast, but they are still uneven, and that unevenness is exactly what caching is designed to compensate for.
Government data shows the baseline has shifted substantially. According to India's Ministry of Communications, via the public broadcaster, "more than 95 percent of villages in India have internet access with 3G or 4G mobile connectivity," and India's global rank for average download speed "improved by 114 ranks, from 130 in 2014 to 16 [in 2024], with an average download speed of 105.85 Megabits per second."
But the mobile picture (as opposed to fixed broadband) has moved in fits and starts as 5G rolled out. Ookla's Speedtest Global Index showed India climbing 72 spots to reach 47th position from 119th. Around the same period, another report using Ookla data found median download speeds rose 115% since before the 5G launch, from 13.87 Mbps in September 2022 to 29.85 Mbps in January 2023. By August 2024, one tracker put India's median mobile download speed at 96.38 Mbps, against a global median of 55.80 Mbps — notably above the global median, even as India's rank slipped a few places that quarter. These numbers don't fully agree with each other, but that's less a contradiction and more a sign of how quickly conditions have shifted year to year.
Scale matters too. As of 2025, India has over 1 billion internet users, at 70% penetration. And speeds vary a great deal by carrier and region — one India-focused tracker reports Jio delivering the fastest average mobile speeds at 122.94 Mbps, with other carriers trailing well behind. For a business whose customers are spread across metros, tier-2 towns, and rural areas on different carriers, that variance is the whole argument for a properly configured CDN and edge cache: it flattens out the worst-case experience rather than only optimizing for whoever tests your site from a fast urban connection.
A practical checklist for your next website review
If you're about to commission, fix, or replace a site, ask your developer or agency these specific questions:
- Is
Cache-Controlset explicitly on static assets (images, CSS, JS), or is the site relying on browser guesswork, per web.dev's guidance? - Are logged-in or personalized pages marked
private, so a shared cache or CDN can't leak one user's data to another, per Google's cache security guidance? - Does the site use a CDN with edge caching, so users on Jio, Airtel, or a rural connection all get served from a nearby node rather than a single origin server?
- What do your Core Web Vitals look like specifically on repeat visits, not just first load, since that's where caching's benefit shows up?
- Is speed being tested on a representative Indian mobile connection, not just office Wi-Fi, given how much network speed varies here?
Questions people also ask
Does caching help first-time visitors at all?
Mostly no. Caching's main benefit is on the second and subsequent loads, since the browser only has something to reuse after it has already fetched a resource once. First-time speed depends more on server response time, image sizes, and code efficiency.
Will fixing caching actually move my Google ranking?
Only at the margin. Google has confirmed speed is a ranking factor for mobile search, but it only affects the slowest pages and a small share of queries — strong content still beats a slightly slower page.
Is it worth setting up a CDN just for an Indian audience?
Given how much mobile speeds vary by carrier and region in India — Jio alone averaging over 120 Mbps while national medians are lower — a CDN with edge caching is one of the more reliable ways to flatten that variance for users outside major metros.