ccmhockey.com website review

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

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.6 s.

About 772 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

Signyfyd costs a phone 1.2 s of main-thread work and 259 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.

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

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Facebook and others), adding 2.1 MB and 2.5 s of main-thread time.

15 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Google Tag Manager costs a phone 701 ms of main-thread work and 847 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.

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

Polyfills for old browsers add 107 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

92 KiB could be saved by minifying JavaScript.

10 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 22.4 MB in 205 requests on a phone: images 18.5 MB (82), scripts 2.4 MB (68) and fonts 1.2 MB (12). Under 2 MB keeps phones on slow connections fast.

9 images weigh 17.5 MB together. On a phone connection a single image that size takes seconds.

14 images (18.0 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.

4 images further down the page (8.1 MB) 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 6.34 g of CO₂e: 761.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some list items are not inside a list.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h3 and h2 → h5), 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 are 6 <h1> headlines (“”, “” and “Level up your shot Level up your shot”). One clear main headline is easier for people and search engines.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 250 pages on ccmhockey.com and 13 external pages.

There is no /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.

Your homepage links to /goalie.html, which answers with an error. Visitors hit a dead end and search engines drop it.

/Skates-2 and /Skates/Category/Player all use the title “Player & Goalie Ice Hockey Skates - CCM Hockey”. Search engines can't tell which page to show for a search, so each competes with the others.

/Skates-2 and /Skates/Category/Player use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /Skates/Category/Player, whose canonical is /Skates-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/Skates-2 and /Skates/Category/Player have no <h1> headline, so visitors and search engines get no clear main topic.

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

10 images failed to load on a phone, for example https://us.ccmhockey.com/homepage.html.

3 errors were logged to the browser console while the page loaded, for example “Unexpected end of JSON input JSON.parse (<anonymous>)”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

Large scripts ship without source maps.

1 link from your homepage to your own site is broken, for example https://us.ccmhockey.com/goalie.html (404).

4 links to other sites are dead, for example https://sondage-survey.ccmhockey.com/m3s/AppForm.aspx?lang=12 (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

Opening https://ccmhockey.com goes through 3 redirects before the homepage loads.

2 links go through two or more redirects, for example https://pay.google.com/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ccmhockey.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 335 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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