Introduction
It's often said that when a page takes three seconds to load, a large share of users leave without waiting. For an EC site, loading speed affects sales as much as design or product lineup does. Most site owners know this, yet as catalogs grow, sites tend to get heavier, and speed work keeps sliding down the priority list.
This article looks at what actually improves when you adopt ISR (the Next.js mechanism that pre-builds pages and refreshes them automatically), from three angles: loading speed, SEO, and operating costs.
Why Pages Get Faster
Pre-Built Pages Served from Nearby Distribution Points
With ISR, pre-built pages are placed on a CDN (Content Delivery Network — a web of distribution servers located around the world). When users open a page, the finished product is returned from the point closest to them, so there is almost no delay from physical distance and no waiting for the page to be assembled.
Users No Longer Wait for Server Processing
With traditional SSR (where the server assembles the page on every visit), users sit in front of the screen while product data is fetched and the page is built. ISR simply returns a page that is already finished, so that entire wait disappears. In practice it feels close to "the page appears the moment you click."
The Difference Shows Most on Mobile Connections
Where this gap becomes most visible is on smartphones with unstable connections. Most EC traffic comes from mobile, often viewed in transit or in places with weak signal. SSR, which needs multiple round trips to the server, suffers under poor connectivity; ISR just receives one finished page from a nearby point, so display stays stable even in rough conditions. Reducing the mismatch of "fast on the office PC, slow on the customer's phone" is a substantial practical win.
Fetch data → assemble page → display: the steps stack up, and users wait through all of them
A finished page is served from a nearby point. No assembly wait at all
In one sentence, the difference is "cook to order, or hand over what's already prepared."
Effects on Core Web Vitals and SEO
What Core Web Vitals Are
Core Web Vitals are Google's metrics for how comfortable a page feels to use, and they influence search rankings. The three main ones are:
- LCP (Largest Contentful Paint): How long the main content takes to appear
- INP (Interaction to Next Paint): How quickly the page responds to clicks and taps
- CLS (Cumulative Layout Shift): How stable the layout stays while displayed
In short, Google rewards pages that are fast, responsive, and visually stable. ISR contributes most directly to the first of these: speed.
The Biggest Gain Is in LCP
Cache delivery through ISR improves LCP the most. The star content of the page — product images, headings — arrives as part of a finished page, so perceived speed goes up and the measured numbers improve with it. Since loading speed is one of the factors in search rankings, keeping pages fast is also groundwork for SEO (attracting visitors through search engines).
The Improvement Can Be Verified with Measurement Tools
Whether pages actually got faster is something you can check with tools, not gut feeling. Enter a URL into Google's PageSpeed Insights (a free page-speed diagnostic tool) and each Core Web Vitals metric appears with a score, so comparing numbers before and after adoption shows the effect directly. It's a diagnostic tool non-engineers can operate, which also makes it handy material for explaining the results of the work inside your company.
The Benefits of Fewer API Calls
Lower Pay-Per-Use Costs
EC sites fetch product information through APIs (the "service window" for receiving data from external services such as Shopify). With SSR, that request fires on every visit; with ISR, no request happens at all while the cache is valid. For services billed by call volume, this translates directly into lower costs.
Resilience During Traffic Spikes
When a mention on social media or in the press sends traffic surging, ISR keeps serving pre-built pages, so the backend servers barely feel the load. The site holds up well even through momentary spikes like the start of a sale. Honestly, this peace of mind only sank in after running the site — not having to worry about servers every time traffic jumps is a bigger deal than it sounds.
Summary
ISR's benefits show up in three places: faster loading, a better SEO foundation via Core Web Vitals, and lower API costs and server load. All of them grow out of one simple idea — serve the pre-built page.
So when and how does that pre-built page get refreshed? The mechanism is covered in the next article.