si.com website review

651 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

Your mobile performance score is 42 (desktop: 67). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.4 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,244 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

17 images could be 11.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

8 third-party services load with your homepage (minutemediacdn.com, Google Tag Manager and mmvideocdn.com and others), adding 32.1 MB and 1.3 s of main-thread time.

minutemediacdn.com costs a phone 375 ms of main-thread work and 30.4 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

mmvideocdn.com costs a phone 180 ms of main-thread work and 500 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Other Google APIs/SDKs costs a phone 129 ms of main-thread work and 445 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

9 long tasks block the main thread while loading, the longest for 211 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

17 KiB could be saved by minifying JavaScript.

Desktop scores 67 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

The first text or image appears after 12.2 s on a phone. Good is under 1.8 s.

Your largest element takes 26.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 36.2 s. Good is under 3.8 s.

Visually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 183 ms to 297 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Scripts block taps and scrolling for 550 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 33.2 MB in 1,207 requests on a phone: images 29.2 MB (202), scripts 2.9 MB (773) and HTML 690 KiB (53). Under 2 MB keeps phones on slow connections fast.

10 images weigh 27.4 MB together. On a phone connection a single image that size takes seconds.

10 images (27.4 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

6 images further down the page (159 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 9.40 g of CO₂e: 1128.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

10 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 18 characters: “Sports Illustrated”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, NewsArticle and WebSite) but with 8 problems, for example “NewsArticle: missing name”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 280 pages on si.com and 38 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.si.com/forums, https://www.si.com/newsletters, https://www.si.com/nfl, https://www.si.com/nba, https://www.si.com/soccer and https://www.si.com/fantasy and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 154 found) and read each the way a search engine does.

10 images failed to load on a phone, for example https://ids4.ad.gt/api/v1/ip_match?id=AU1D-0100-001791757276-YD28A0QS-KVJQ.

24 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 2,046 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 41 cookies (measured from a US location before any click).

Loading the homepage contacts 125 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.