Nike.com

How often should I refresh the YourWebsiteScore report for Nike.com?

The latest audit was captured on October 1, 2025.

Re-run the analysis after major deployments or at least once a month so you can spot Core Web Vitals, snippet, or security regressions before they affect rankings or conversions.

Which Lighthouse performance improvements should Nike.com tackle first?

Total Blocking Time (desktop) at 1.5s: reclaim ≈30 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.

Largest Contentful Paint (desktop) at 3.4s: reclaim ≈19 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.

Speed Index (desktop) at 3.7s: reclaim ≈9 points. Trim render-blocking resources, preconnect to critical domains, and focus on above-the-fold rendering to accelerate visual completion.

Which Lighthouse SEO audits should Nike.com fix first?

Links do not have descriptive text (desktop) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how Nike.com appears in search.

Which Lighthouse Best Practices should Nike.com fix first?

Uses deprecated APIs (desktop) is missing roughly 19 points. Fixing it will raise the Best Practices score and keep Nike.com aligned with modern browser expectations.

Uses third-party cookies (desktop) is missing roughly 19 points. Fixing it will raise the Best Practices score and keep Nike.com aligned with modern browser expectations.

Browser errors were logged to the console (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep Nike.com aligned with modern browser expectations.

Which Lighthouse Accessibility audits should Nike.com fix first?

Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make Nike.com easier to use.

`[role]`s are not contained by their required parent element (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make Nike.com easier to use.

Links do not have a discernible name (desktop) is missing roughly 3 points. Fixing it will raise the Accessibility score and make Nike.com easier to use.

Which Website Quality issues should Nike.com fix first?

Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift Nike.com's Website Quality score.

Meta Description: missing ≈6 points. 80 chars (ideal 120–160). Focus on it to lift Nike.com's Website Quality score.

Headings: missing ≈6 points. Skipped heading levels (use H1 → H2 → H3 in order). Focus on it to lift Nike.com's Website Quality score.

Which Trust & Security fixes should Nike.com tackle first?

MIME Type Protection: missing ≈5 points. Missing (should be: X-Content-Type-Options: nosniff). Close this gap to raise Nike.com's Trust & Security score.