Nike Loads 8.9MB of JavaScript on Every Page — Here’s What It’s Costing Them

Because every second costs you real money. This isn't a vanity metric. Google, Deloitte, and Akamai have all studied this, and the numbers are brutal:

Nike gets this. They’re a $46.3B company (FY2025, per SEC filings) that built their entire digital platform from scratch on AWS — custom Next.js frontend, Akamai CDN, GraphQL APIs. But even with that investment, nike.com still loads 8.9MB of JavaScript on every page. Let’s look at why.

Speed gets visitors to the page. But do you know who they are? LeadMaxxing identifies your anonymous visitors and scores them so you know which ones are worth chasing.

Google doesn't care about your Lighthouse score. Seriously. Lighthouse is a lab test — it's a simulation. What Google actually uses for rankings are Core Web Vitals: real data from real Chrome users visiting your real site over the last 28 days. Three numbers:

Nike's CrUX field data was unavailable during our audit (Google PageSpeed Insights returned 429 rate-limiting errors). However, lab profiling by Request Metrics paints a concerning picture: 5.6-second total load time, multiple layout shifts during rendering, and 70% of load time consumed by script execution. With 87 JavaScript requests totaling 8.9MB, Nike’s INP and LCP are almost certainly under pressure. Core Web Vitals are a confirmed SEO ranking signal, which means slow sites lose twice: visitors leave AND Google ranks you lower.

Users are 24% less likely to abandon a page when it passes all three. For a site with ~90M monthly visits (estimated via SimilarWeb), even a 1% abandonment reduction could represent significant revenue recovery.

Run a live PageSpeed test on nike.com right now → — you'll see their real CrUX field data.

Nike didn’t buy an off-the-shelf ecommerce platform. They built their own. While most DTC brands run on Shopify or BigCommerce, Nike’s engineering team constructed a custom stack on AWS with Next.js for the frontend, Akamai for CDN, and GraphQL/REST APIs powering everything from product pages to checkout. Per Nike Engineering’s own writing, they “re-imagined their entire technology stack using observability, security, reliability, availability, and performance as core principles.”

The DTC pivot drove this. When Nike shifted to direct-to-consumer — cutting wholesale accounts and investing in nike.com and the Nike App — the digital platform had to handle the load. NIKE Direct revenue hit $18.8B in FY2025 (per SEC filings), which is roughly 41% of total Nike Brand revenue flowing through their own digital and retail channels. That’s why the architecture looks like this:

What This Architecture Actually Does

The Akamai CDN layer is fast. Nike’s initial HTML document arrives in just 143ms (per Request Metrics profiling). That’s Akamai’s edge network serving cached content from a server physically close to the user. DNS records confirm this: nike.com CNAME-resolves to ev-cn.nike.com.edgekey.net — that’s Akamai’s infrastructure. Cache-Control headers show strategic refresh rates: max-age=646 for the homepage, max-age=899 for product pages.

The problem is everything that happens after. Once the HTML lands, the browser has to parse and execute 87 JavaScript files totaling 8.9MB. Script execution alone consumes 70% of total page load time. Nike’s engineering team uses Redux for state management, Emotion CSS-in-JS, and a custom design system (@nike/nike-design-system-components) with 100+ feature flags controlling everything from recommendations to gift messaging. (See our full tech stack analysis for the complete breakdown.)

Nike loads at least 9 identified third-party services on every page. That’s on top of their own massive JavaScript bundles. The total JS footprint is 8.9MB uncompressed across 87 requests — most of that is Nike’s own code, but external scripts add roughly ~500KB of additional weight and critically, they block the main thread. (See our full tracking and privacy audit for the complete picture of what runs on every pageview.)

Most of these scripts exist because Nike needs 9+ disconnected tools to do what a single platform could handle. LeadMaxxing combines visitor tracking, lead scoring, email automation, and A/B testing in one script — so you don't need to stack tools and tank your PageSpeed.

Images are typically 50-70% of total page weight on an ecommerce site. Nike runs their image pipeline through Akamai’s Image Manager — the same CDN that serves their HTML — with automatic format negotiation and responsive sizing built in:

The Simple Stuff You Can Copy Today

• Switch every image to WebP. If you're still serving JPEGs, you're wasting 30% of your bandwidth. Most CDNs and platforms do this automatically now.
• Add loading="lazy" to every image below the fold. One HTML attribute. Stops the browser from downloading images the user hasn't scrolled to yet.
• Set explicit width and height on images. This prevents CLS (layout shift). The browser reserves space before the image loads, so nothing jumps around.
• Use responsive images. A phone doesn't need the 2000px desktop version. Use srcset to serve the right size for each device.

Nike’s speed story proves that even a $46B company can't buy their way out of JavaScript bloat. Their Akamai CDN is blazing fast, their Next.js architecture is modern, and their tech stack is enterprise-grade — but 8.9MB of JavaScript still takes 5.6 seconds to parse and execute. The lesson? Speed wins come from removing things, not adding them. Audit your scripts, optimize your images, and monitor real user data. The 20% of effort that gets you 80% of the speed advantage is accessible to any brand at any scale — and it starts with understanding what your tracking pixels and ad scripts are actually costing you.

You don't need Nike's budget. Here's the 20% of effort that gets you 80% of their speed:

Frequently Asked Questions

How fast is Nike's website?

Nike.com takes approximately 5.6 seconds to fully load per Request Metrics profiling, with 283 total network requests and 8.9MB of uncompressed JavaScript. The initial server response is fast at 143ms thanks to Akamai CDN edge caching, but heavy JavaScript execution — consuming 70% of total load time — significantly delays the interactive experience for visitors.

What technology stack does Nike use for their website?

Nike.com runs on a custom-built platform using Next.js with server-side rendering (SSR) and static site generation (SSG), Redux for state management, Emotion CSS-in-JS for styling, and a proprietary Nike Design System. The backend uses GraphQL and REST APIs hosted on AWS, with Akamai Technologies serving as the CDN provider (confirmed via Akamai-Grn response headers and CNAME records pointing to edgekey.net).

What third-party scripts run on Nike's website?

Nike.com loads at least 9 identified third-party services: Google Tag Manager (tag management), Optimizely (A/B testing, account ID 6194110778), Adobe Target (personalization via abt.nike.com), Nike Analytics (custom analytics at analytics.nike.com), Meta Pixel (advertising), The Trade Desk (programmatic ads), New Relic (error monitoring), Singular (mobile attribution), and DeviceAtlas (device detection). Combined, the site makes 87 JavaScript requests totaling 8.9MB uncompressed.

Does Nike pass Google's Core Web Vitals?

Nike's Core Web Vitals field data from CrUX (Chrome User Experience Report) was not available during our audit window due to API rate limiting. However, lab testing via Request Metrics revealed a 5.6-second total load time, multiple layout shifts during rendering, and 70% of load time consumed by script execution — all warning signs for LCP and CLS performance. You can run a live test at pagespeed.web.dev to check Nike's current CrUX field data.

How does Nike's site speed compare to competitors?

Nike's 5.6-second load time and 8.9MB JavaScript payload are significantly heavier than typical DTC athletic brands. For comparison, competitors running headless Shopify architectures typically load in 1–3 seconds with under 1MB of JavaScript. Nike's custom-built platform trades raw speed for enterprise-grade features like 100+ feature flags, sophisticated personalization via Adobe Target, and multi-region i18n support.

Why is Nike's website slow despite being a $46B company?

Nike.com is slow primarily because of JavaScript bloat: 87 JS requests totaling 8.9MB uncompressed, with script execution consuming 70% of total load time. This stems from Nike's enterprise architecture — multiple internal teams contribute scripts independently, creating fragmentation. Third-party tools like Optimizely, Adobe Target, and Google Tag Manager add further weight. The trade-off is intentional: Nike prioritizes personalization, A/B testing, and analytics over raw page speed.

What CDN does Nike use?

Nike uses Akamai Technologies as their primary CDN provider. This was confirmed via the Akamai-Grn response header and DNS CNAME records pointing to ev-cn.nike.com.edgekey.net. Akamai's edge network delivers Nike's initial HTML document in approximately 143 milliseconds, though subsequent JavaScript execution adds several seconds to the total load time.

How does Nike optimize images on their website?

Nike serves images through Akamai's Image Manager with automatic format negotiation (WebP/AVIF), quality optimization, and responsive sizing. The Next.js Image component adds native lazy loading and responsive srcset generation. Nike also uses their custom CDN infrastructure for product photography and marketing assets, with cache-control headers showing strategic refresh rates (e.g., max-age=899 for product pages).