Skip to main content
Blog

Landing pages

Page speed optimization

The fixes that make an ecommerce page load fast, in the order to do them, and the Core Web Vitals scores to aim for.

Start for free

Page speed optimization is the work of making your pages load, respond and stay steady faster. On an ecommerce site, start with the biggest files. Compress and resize images, lazy load what sits below the first screen, and delay scripts a shopper doesn't need to buy. Then check Google's Core Web Vitals in PageSpeed Insights and aim for LCP under 2.5 seconds, INP under 200 ms and CLS under 0.1.

Takeaways: Faster pages convert more visitors and lose fewer to the back button. Fix images and scripts first, then check the gains with Core Web Vitals and an A/B test. Recheck PageSpeed Insights each month, because new apps and images slow pages down again. Replo pages are server-side rendered, so they start fast.

Swappie, a seller of refurbished iPhones, shows what speed is worth. In 2016, Sami Marttinen paid upfront for a used phone online, and it never arrived (Aalto University). He started Swappie with Jiri Heinonen, and in the early days he sometimes delivered phones by bike. By 2020, Swappie made 98 million euros in sales.

After a few years of building new features first, its mobile sales lagged behind desktop. The team spent about three months on speed (web.dev). Largest Contentful Paint fell 55%, and mobile revenue rose 42%. We use Swappie's fixes as examples in the steps below.

Swappie ads with purple panels on a tram stop at Damrak in Amsterdam, a tram pulling in on the right
Swappie's ads send shoppers to its site on their phones, where three months of speed work lifted mobile revenue 42%. Photo: Wikimedia Commons, CC BY-SA 4.0, by Sep Verduin (Out of Home Masters)

What is page speed optimization?

Page speed optimization is the set of fixes that cut how long a page takes to show, react and settle. It covers image weight, script timing, caching and how files travel over the network. The easiest fixes use your platform's built-in features, theme patterns and a few targeted changes.

Your platform can slow you down before you change anything. Shopify themes, for example, have a reputation for speed problems outside a store owner's control. Pages built on Replo don't run inside a Shopify theme, so those problems don't apply. Read our support guide to Shopify page speed to learn more.

Why does page speed matter for ecommerce?

Faster pages let shoppers browse, add to cart and check out with less waiting. On ad traffic, that turns more paid clicks into sales. Faster landing pages improve ad conversion rate, which lowers what each sale costs.

Speed also helps search. Google counts user experience signals and Core Web Vitals in its rankings. When pages are slow, visitors leave sooner and spend less.

Bar chart titled Half of phone taps on a landing page land in its top fifth: 48% in the top fifth, then 15%, 11%, 11% and 15%, from landing pages on 99 live stores over 14 days of Replo heatmaps
Most taps happen at the top of the page, so that part has to show first; a slow first screen loses them

A Semrush study found bounce rate can nearly triple once a page takes more than three seconds to load. Aim well under that. Page speed moves three things:

  • Revenue: faster pages convert more visitors.
  • Search: Google favors fast pages in its results.
  • Ad costs: a better landing page experience grade lowers what you pay per click.

What are Core Web Vitals?

Core Web Vitals are Google's measures of loading, responsiveness and visual stability. Four numbers matter to a store.

First Contentful Paint (FCP) is the time until the first text, logo or image shows after a click. It answers the shopper's first question: is this site working? A faster FCP keeps paid visitors from bouncing.

Largest Contentful Paint (LCP) is the time until the biggest element on the first screen appears. On a product page, that's usually the hero image.

Interaction to Next Paint (INP) measures how fast the page reacts when someone taps or clicks. It doesn't average every tap. It reports the slowest ones, so one sluggish widget can drag the score down. Google explains the metric in depth on web.dev.

Cumulative Layout Shift (CLS) measures how much the page jumps around as it loads. It multiplies how much of the screen moves by how far it moves. A buy button that slides down as a banner loads is a layout shift.

What page speed scores should you aim for?

Aim for LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less. These targets follow Finsweet's guidelines, which match Google's:

  • FCP: good at 1.8 seconds or less, poor above 3 seconds.
  • LCP: good at 2.5 seconds or less, needs work up to 4 seconds, poor beyond.
  • INP: good at about 200 milliseconds, needs work up to about half a second, poor beyond.
  • CLS: good at 0.1 or less, needs work up to 0.25, poor above 0.25.

PageSpeed Insights checks all of them. Type in your page's address, and it shows lab results plus real-visitor data from Chrome over 28 days. It gives a Core Web Vitals pass or fail and lists what's slowing the page.

To test our own pages, we rebuilt a product page for the skincare brand Nivie on Replo. Then we ran both versions through PageSpeed Insights. The Replo-built page scored 95 on Performance, against 76 for the original.

PageSpeed Insights Performance results for the Replo-built version of Nivie's product detail page
The Replo-built version scores 95, against 76 for the original, with 0 ms of Total Blocking Time.

How do you optimize page speed on an ecommerce site?

Fix the heaviest things first, then check each gain with the same test. Treat speed as a monthly routine, not a one-off project. These are the best practices in the order we'd do them.

1. Compress images and convert them to WebP

Big images are usually the biggest drag on a page, especially on phones. Save product and lifestyle photos as WebP or AVIF, resize them to the size they show, and compress them before upload. Keep the originals in case you need a new crop later.

Here is the difference on one real photo. Summer Fridays' original upload of its Jet Lag Mask photo is a 2000px JPEG of 443 KB. We saved it as a 1200px WebP, and it weighs 67 KB, about 85% less. It looks the same at the width a blog column shows.

A woman with her hair pulled back and Summer Fridays Jet Lag Mask spread across her face, against a blue sky
This photo is the 67 KB WebP version; the original JPEG upload weighs 443 KB. Photo: Summer Fridays

For graphics with a clear background, try WebP before PNG. Replace heavy GIFs with SVG or Lottie files where you can.

2. Serve each image at the size it shows

A phone that's 400px wide shouldn't download a 1920px banner. Give the browser several sizes and let it pick. Spot & Tango does this on its homepage: the hero below comes in seven widths, from 440 to 1920 pixels. Swappie's team also sized its images properly as part of its speed work.

Spot & Tango's homepage hero: a dog lying beside a bowl of fresh dog food surrounded by carrots, meat and greens
Spot & Tango serves this hero in seven widths, so a phone gets the 440px file, not the 1920px one. Photo: Spot & Tango

3. Lazy load media below the first screen

Lazy loading waits to load an image or video until the visitor scrolls near it. Only the hero image, the key copy and the main button should load right away. Use light placeholders for videos, and load the player when someone taps. Swappie lazy loads images outside the first screen.

4. Delay scripts a shopper doesn't need to buy

Add the defer attribute, or load scripts on a timer, so they don't block the page from showing. Load what makes the page usable first. Push the rest until after the first paint or the first tap.

Chat widgets, social widgets and extra analytics are common candidates. Swappie reviewed every third-party script and widget and cut the ones it didn't need.

5. Preload the hero image and headline font

Tell the browser to fetch the hero image and the headline font first, since they're the first things a visitor sees. That shortens LCP. Swappie preloads its LCP image, and it renders that element on the server where it can.

Lemme's Debloat page on a phone, first screen: the product photo, 4.7 stars from over 2,500 reviews, the headline Jeans Tight After Dinner? Lemme Debloat Has Your Back and three checkmarked benefits
On Lemme's Debloat page, the product photo is the largest element on the first screen, so it is the image to preload.

Replo uses server-side rendering (SSR) for every page. The server builds the page and sends it ready-made, instead of the shopper's browser building it. That shortens First Contentful Paint (FCP) and LCP, which matters most when a shopper is deciding whether to add to cart.

6. Prefetch the pages people click next

Prefetching loads a linked page in the background before the visitor clicks it. When they do click, the page shows almost at once. Use it for links from collection pages to product pages, and from listicle pages to the product they sell.

7. Load tracking tags through Google Tag Manager

Every tracking pixel you add can slow how fast the page reacts. Remove pixels you don't use. Some pixels can wait until the visitor acts without hurting your data.

Google Tag Manager (GTM) puts your pixels in one place and loads many of them in the background. You control when each fires, for example only after the page loads with its page view trigger.

GTM can also move scripts from the visitor's browser to a server, called server-side tagging. Fewer heavy scripts run on the phone, so pages feel lighter.

GTM also listens for a consent switch. Until a visitor agrees to ad and analytics tracking, many tags stay quiet or run in a light mode. Less code runs up front, so the page appears sooner. If the visitor agrees later, GTM fires your pixels then.

Replo lets you add pixels or tags from a range of analytics tools. It also connects directly with Google Tag Manager. Move scattered scripts into GTM and fire each one only when you need it.

Which tools test page speed?

Use PageSpeed Insights for Google's view, GTmetrix or WebPageTest for detail, and a monthly check to catch slowdowns. Test before and after every big release.

Check pages in Google PageSpeed Insights

Run your key templates through PageSpeed Insights on both mobile and desktop. Watch FCP closely, since it decides when shoppers first see anything. Read the Core Web Vitals Assessment for real-visitor data. Then read the Diagnose Performance Issues section for what to fix.

PageSpeed Insights Performance results for Nivie's original product detail page: a score of 76, with First Contentful Paint 0.7 s, Largest Contentful Paint 1.1 s, Total Blocking Time 400 ms in red, Cumulative Layout Shift 0.075 and Speed Index 2.0 s
How to read a result: Nivie's original page scores 76, and the one red metric, 400 ms of Total Blocking Time, is the first thing to fix.

Dig deeper with GTmetrix and WebPageTest

For a closer breakdown, use GTmetrix or WebPageTest. They show which files block the page, which requests wait on others and which downloads are too big. Test from the regions where your customers live.

Recheck speed every month

Set targets for FCP, LCP, INP and CLS that fit your goals. Analyze and iterate over time so gains hold across campaigns and seasons. Note each change you make to a landing page as you A/B test. Then run a monthly audit:

  1. Record your current scores.
  2. Fix the biggest slowdown on one key template.
  3. Check the gain with your tool of choice.
  4. Check weekly and log changes next to score shifts. Scores move a few points on their own, so a small drop doesn't always mean something broke.

Swappie tracked its mobile conversion rate and page load time every day in Google Analytics. That's how its team tied each speed fix to sales.

The fastest page isn't always the best seller, so test elements one at a time with our tips to optimize your pages for conversions. Run each A/B test until it's significant, and keep what you learn in a shared doc. Our full guide covers A/B testing landing pages.

How does Replo keep pages fast?

Replo pre-builds pages on its edge network and renders every page on the server. If you wonder whether a visual page builder slows a site, this is how we avoid it. Pages are built with Next.js on Cloudflare Workers, with server-side rendering on every load and link prefetching.

That means a shorter Time To First Byte, the time from a request to the first byte of the reply. Replo pages ship less JavaScript by default and cache the full HTML of pre-built pages. They carry fewer third-party scripts than a typical Liquid theme on Shopify, and they fetch data only when it's needed.

When you're ready to build more pages for your campaigns, see our guide to create product pages with Replo.

Start building faster pages today.

Frequently asked questions

Why does page speed matter for revenue, SEO, and ads?
Faster pages let shoppers move from browsing to cart to checkout with less waiting, so more of them buy. That makes paid traffic cheaper per sale. Google also uses Core Web Vitals in search rankings, and slow pages lose visitors before they load.
What Core Web Vitals should I aim for?
Aim for LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less. Also keep FCP at 1.8 seconds or less. These measure loading, how fast the page responds to taps and how steady the layout stays.
How does Replo help me get faster pages?
Replo pre-builds pages and serves them from its edge network with server-side rendering. Pages ship less JavaScript and send their first byte sooner. When we rebuilt a Nivie product page on Replo, it scored about 20 points higher in PageSpeed Insights than the original.

Build a page for every ad

Replo builds a landing page that matches each ad, so every click lands on the promise it made.