Amazon Affiliate Site Speed: What Actually Matters for Rankings and What Doesn't
Speed is the part of SEO where affiliate site owners spend the most time for the least return. A score of 62 on PageSpeed Insights looks like a problem, a week goes into plugins and caching, the score reaches 94, and the rankings don't move, because they were never about the score.
What Google measures is narrower than the tools suggest, and what slows affiliate sites in particular is a short list.
This post sets out what Google measures and how much it counts, the three things that slow affiliate sites, the fixes in order of payoff, what's not worth doing, and when speed is the problem rather than a distraction from it. It's the speed entry in the not-ranking post, expanded.
The short answer
Google measures three things on real visitors: how fast the main content appears (LCP, under 2.5 seconds), how quickly the page responds to a tap (INP, under 200 milliseconds), and whether things jump around while loading (CLS, under 0.1).
Pass those and speed is done. On affiliate sites the failures come from oversized images, product-box plugins and third-party scripts, in that order. Fix those three, confirm green in Search Console, and go back to writing.
What Google actually measures
| Metric | Plain English | Pass | Affiliate-site cause when it fails |
|---|---|---|---|
| LCP | How long until the biggest thing on screen appears | ≤ 2.5 s | Hero or first product image too large; slow host |
| INP | How long the page takes to react to a tap or click | ≤ 200 ms | Heavy scripts: ad networks, trackers, table plugins |
| CLS | How much the layout jumps while loading | ≤ 0.1 | Images and ad slots without set dimensions; late-loading product boxes |
These are measured on your real visitors over 28 days (the "field data" in PageSpeed Insights and the Core Web Vitals report in Search Console), not on the lab run that produces the score. A page can have a lab score of 60 and pass all three in the field; that page is fine.
How much it counts: Google has said page experience is a ranking signal and that relevance matters more. In practice it's a tie-breaker between pages of similar quality. It won't lift a thin guide, and it won't sink a good one unless it's badly broken.
The three things that slow affiliate sites
1. Images
The single biggest cause of a failed LCP. A buyer guide has ten product images plus a cover, and if any of them are served at 2,000 pixels wide for a 400-pixel slot, that's the metric gone.
Your own photos need resizing to the display size, compression, and a modern format (WebP or AVIF); WordPress does the format conversion in recent versions and most image plugins do the rest. Amazon product images should load from Amazon at display time rather than being saved to your site, which keeps them small and keeps you inside the image rules.
Give every image a width and height attribute so the browser reserves the space; that's most of CLS on an affiliate page.
2. Product-box and table plugins
The plugins that draw product boxes, comparison tables and star ratings often load their scripts and stylesheets on every page, whether or not the page uses them, and some fetch product data on each load. They're the usual cause of a failed INP and a slow first paint.
Check what the plugin loads with the browser's network tab on a post that has no product boxes; if the plugin's files are there anyway, it's loading globally. Some plugins have a setting for this; otherwise a lighter plugin, or hand-built boxes, is the fix.
3. Third-party scripts
Ad networks, analytics, heatmaps, chat widgets, social embeds, font loaders. Each one is a request to another server before the page is interactive, and ad scripts in particular are heavy.
Keep analytics, drop anything you don't look at monthly, and load ads so they don't block the page (most networks offer an async or lazy option). Amazon's Native Shopping Ads are a script too; use them on pages where they earn and not site-wide.
Fixes in order of payoff
- Resize and compress your own images; keep Amazon's on Amazon. An afternoon, and it fixes LCP on most sites.
- Set width and height on every image and ad slot. Fixes CLS.
- Remove scripts you don't use. Ten minutes per script. Each one removed improves INP.
- Make the product-box plugin load only where needed, or replace it.
- Turn on page caching (most hosts have it; otherwise one caching plugin). Helps LCP on shared hosting.
- Change host, only if LCP is still red after the above and the server response time in PageSpeed is over 600 ms.
What's not worth doing
- Chasing the score from 85 to 100. The field metrics are what count, and they're already green.
- Stacking optimisation plugins. Two caching plugins break things; one is enough.
- Minifying everything by hand. Minor gains, real breakage risk.
- A CDN for a site with 2,000 visits a month. Fine to have, not a fix for anything.
- Removing the comparison table because it's "heavy". The table converts; a lighter table is the answer, not no table.
When speed is the real problem
Three signs. Search Console's Core Web Vitals report shows red on most pages, not amber on some. Mobile pages take more than four seconds to show the first product. Or the site's rankings dropped in step with adding a plugin or an ad network, which the Search Console post shows how to date. In those cases the fixes above are urgent; otherwise they're maintenance.
Doing it with AffSERP
Guides written by AffSERP's X Best Review tool publish as plain HTML: the product boxes and comparison table are markup and styles in the post, with no plugin script to load, and product images are referenced from Amazon rather than saved to your media library, with width and height set.
That takes causes one and two off the table for those pages. Cause three, the scripts you add to the site, stays with you, and the fixes above apply to every page whatever wrote it.
FAQ
Does site speed affect affiliate site rankings?
A little. Google uses page experience, including Core Web Vitals, as a signal, but it's a small one next to content and links, and it mostly works as a tie-breaker between similar pages. A slow site with the best guide still outranks a fast site with a thin one. Fix speed when it's red; don't expect it to move rankings on its own.
What is a good PageSpeed score for an affiliate site?
Stop thinking in scores. The things Google measures are the Core Web Vitals thresholds: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1, measured on real visitors. A page that passes those is fine whether its lab score is 70 or 95. Chasing from 85 to 100 is time that belongs in content.
Why is my affiliate site slow?
Almost always one of three things: product images served at full size, a product-box or table plugin that loads scripts and styles on every page, or ad and tracking scripts. Run PageSpeed Insights on one buyer guide and look at the largest items in the 'Diagnostics' section; the culprit is usually obvious.
Do Amazon product images slow the site down?
Images loaded from Amazon's CDN at display time are usually fine; they're already sized and cached. The slow case is images saved to your own media library at full resolution, which also breaks the Associates image rules. Your own photos need resizing and modern formats; Amazon's need to stay on Amazon.
Keep reading
