Website review, no card needed
coolhockey.ca website review
Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 91 checks
This review found 43 issues worth fixing on coolhockey.ca, 17 of them high impact, across 91 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72C- #97,383 of 125,955 reviewed websitesbeats 20%
- #59,648 of 70,316 online storesbeats 12%
- #55,496 of 63,859 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 101 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 130 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 124 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 132 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 130 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 129 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
1.3 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,452 HTML elements
The page has 6,452 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Help Scout and others), adding 7.9 MB and 498 ms of main-thread time.
Shopify adds 206 ms
206 msShopify costs a phone 206 ms of main-thread work and 7.1 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.
Improve image delivery
697 KiB19 images could be 697 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
671 KiBAbout 671 KiB of JavaScript is downloaded but never used on this page.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 277 ms. During a long task the page ignores taps.
Google Tag Manager adds 160 ms
160 msGoogle Tag Manager costs a phone 160 ms of main-thread work and 322 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.
Reduce unused CSS
150 ms · 37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
126 KiB26 files are served with short cache lifetimes, so returning visitors download them again (126 KiB).
Legacy JavaScript
52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 77 ms
77 msYour server sent the HTML in 77 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 40.4 s
40.4 sThe page becomes fully interactive after 40.4 s. Good is under 3.8 s.
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.323
0.323The layout shifts by 0.323 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 101 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
162 images without width and height
162 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 492 ms
492 msScripts block taps and scrolling for 492 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 93 ms
93 msReal visitors wait 93 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 263 ms
263 msReal visitors wait 263 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 10.7 MB in 398 requests
10.7 MBYour homepage downloads 10.7 MB in 398 requests on a phone: images 7.7 MB (132), scripts 1.7 MB (112) and other files 798 KiB (110). Under 2 MB keeps phones on slow connections fast.
32 images far larger than shown
5.8 MB32 images are downloaded at several times the size a phone draws them, for example closeup-knights.jpg at 1,080 px wide, shown at 78 px. Resized copies would save about 5.8 MB.
37 images below the first screen load straight away
37 images further down the page (6.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
34 images in older formats
34 images (6.2 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.
An image on the first screen is lazy-loaded
CarolinaStanleyCupChampionPatch_a484e4dc-6661-41df-802b-f458 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).
About 3.0 g of CO₂ per visit
3.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.04 g of CO₂e: 365.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
963 images without alt text
963 images have no alt text, which hurts accessibility and image search.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “CoolHockey Canada | Officially Licensed NHL Hockey Jerseys – CoolHockey.ca”.
Meta description is long (212 characters)
Your meta description is 212 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
289 internal links, 10 external
The homepage links to 289 pages on coolhockey.ca and 10 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://coolhockey.ca/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://coolhockey.ca/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,879 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://coolhockey.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://coolhockey.ca/collections/all, https://coolhockey.ca/policies/shipping-policy, https://coolhockey.ca/pages/frequently-asked-questions, https://coolhockey.ca/policies/refund-policy and https://coolhockey.ca/collections/team-canada-2025-jerseys-and-apparels have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://coolhockey.ca/collections/all, https://coolhockey.ca/collections/jersey-patches, https://coolhockey.ca/collections/team-canada-2025-jerseys-and-apparels, https://coolhockey.ca/collections/calgary-flames, https://coolhockey.ca/collections/edmonton-oilers and https://coolhockey.ca/collections/montreal-canadiens and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 75 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187087112&tm=gtm002&Ver=2&mid=f13f1e6c-90fb-4553-93b5-43a96f15a819&bo=1&sid=36155d00d98311f1a41e492c8e7ec2d7&vid=36157890d98311f1a3ce4174686d15f3&vids=1&msclkid=N&pi=9.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “$(...).addEventListener is not a function”.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
44 of 51 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 301 words of copy
The homepage carries about 301 words of visible text.
4 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Order Tracker”, “Shop By Team” and “Shop All”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 32 customer or partner logos and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
39 other companies contacted
Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at coolhockey.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Selecty · Pagefly Ai Page Builder · pwztag.com · avada.io · cloudfront.net · chimpstatic.com · shareasale.com · nice-team.net · amazonaws.com · useamp.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on coolhockey.ca, including 18 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.