wild.com website review

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

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 863 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Integral Ad Science and Google/Doubleclick Ads and others), adding 5.6 MB and 3.9 s of main-thread time.

nhle.com costs a phone 597 ms of main-thread work and 1.8 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.

16 images could be 778 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Integral Ad Science costs a phone 709 ms of main-thread work and 433 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.

Google/Doubleclick Ads costs a phone 662 ms of main-thread work and 777 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.

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

site.com costs a phone 450 ms of main-thread work and 1.2 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.

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

About 152 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 25.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LIVE: MIN @ WSH View Gamecenter Watch: Wild+ Listen: Wild+ …”.

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 7.7 MB in 248 requests on a phone: scripts 4.4 MB (80), fonts 1.7 MB (2) and images 1.1 MB (82). Under 2 MB keeps phones on slow connections fast.

vnvkiikine1yaaadyy3y.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images (223 KiB) 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.

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

All page content should be contained by landmarks: 76 elements on the page fail this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

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

Structured data found (Organization and Website) but with 2 problems, for example “Organization: url is not an absolute URL ("/")”.

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

The homepage links to 152 pages on wild.com and 153 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.nhl.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.nhl.com/wild, https://www.nhl.com/wild/news, https://www.nhl.com/wild/news/topic/press-release, https://www.nhl.com/wild/news/topic/transactions and https://www.nhl.com/wild/news/topic/down-on-the-farm all use the title “Official Minnesota Wild Website | Minnesota Wild”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.nhl.com/wild/tickets, https://www.nhl.com/wild/tickets/single-game-tickets, https://www.nhl.com/wild/tickets/flex-plans, https://www.nhl.com/wild/tickets/promotional-nights, https://www.nhl.com/wild/tickets/group-tickets and https://www.nhl.com/wild/tickets/hospitality and 6 others use the same meta description. A description written for each page earns more clicks.

https://www.nhl.com/wild/tickets/flex-plans, https://www.nhl.com/wild/tickets/promotional-nights, https://www.nhl.com/wild/tickets/business, https://www.nhl.com/wild/tickets/group-tickets, https://www.nhl.com/wild/tickets/hospitality and https://www.nhl.com/wild/tickets/youth-hockey and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

16 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 trust badge. 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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,257 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and The Trade Desk (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 14 cookies (measured from a US location before any click).

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