Website review, no card needed

hockeystickman.com logo

hockeystickman.com website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 83 checks

This review found 34 issues worth fixing on hockeystickman.com, 11 of them high impact, across 83 checks. The most urgent: main-thread work: 7.4 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
176 ms140 msMay 16Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026145 ms
May 23, 2026144 ms
May 30, 2026145 ms
Jun 6, 2026147 ms
Jun 13, 2026146 ms
Jun 20, 2026147 ms
Jun 27, 2026151 ms
Jul 4, 2026149 ms
Jul 11, 2026149 ms
Jul 18, 2026145 ms
Jul 25, 2026145 ms
Aug 1, 2026146 ms
Aug 8, 2026145 ms
Aug 15, 2026149 ms
Aug 22, 2026148 ms
Aug 29, 2026146 ms
Sep 5, 2026146 ms
Sep 12, 2026146 ms
Sep 19, 2026149 ms
Sep 26, 2026156 ms
Oct 3, 2026163 ms
Oct 10, 2026168 ms
Oct 17, 2026172 ms
Oct 24, 2026165 ms
Oct 31, 2026154 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

Full-page screenshot of hockeystickman.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hockeystickman.com at 0.9 s0.9 s
  2. hockeystickman.com at 1.9 s1.9 s
  3. hockeystickman.com at 2.8 s2.8 s
  4. hockeystickman.com at 3.7 s3.7 s
  5. hockeystickman.com at 4.7 s4.7 s
  6. hockeystickman.com at 5.6 s5.6 s
  7. hockeystickman.com at 6.5 s6.5 s
  8. hockeystickman.com at 7.5 s7.5 s

Speed

13 to fix51
  • Main-thread work: 7.4 s

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

  • 5,620 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Yotpo and Hubspot and others), adding 1.9 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 821 KiB

    About 821 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 51

    51/100

    Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

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

  • Improve image delivery

    300 ms · 569 KiB

    14 images could be 569 KiB 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.

  • Shopify adds 626 ms

    626 ms

    Shopify costs a phone 626 ms of main-thread work and 761 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.

  • Use efficient cache lifetimes

    481 KiB

    31 files are served with short cache lifetimes, so returning visitors download them again (481 KiB).

  • Yotpo adds 302 ms

    302 ms

    Yotpo costs a phone 302 ms of main-thread work and 412 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.

  • 18 long tasks on the main thread

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

  • Hubspot adds 276 ms

    276 ms

    Hubspot costs a phone 276 ms of main-thread work and 102 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.

  • Klaviyo adds 151 ms

    151 ms

    Klaviyo costs a phone 151 ms of main-thread work and 310 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.

  • Legacy JavaScript

    40 KiB

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

  • Reduce unused CSS

    31 KiB

    About 31 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

  • 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.

1 checks passed
  • Server response: 16 ms

    16 ms

    Your server sent the HTML in 16 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Time to Interactive: 25.5 s

    25.5 s

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

  • Largest Contentful Paint: 6.2 s

    6.2 s

    Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BUILT BY HOCKEY PLAYERS, FOR HOCKEY PLAYERS.”.

  • Total Blocking Time: 868 ms

    868 ms

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

9 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.4 s

    1.4 s

    Real visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 128 ms

    128 ms

    Real visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 612 ms

    612 ms

    Real visitors wait 612 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.039

    0.039

    The layout barely moves while loading (CLS 0.039, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 4.8 MB in 376 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 376 requests on a phone: scripts 1.9 MB (130), images 1.1 MB (40) and other files 1.0 MB (153). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.35 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8591
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Elements must only use permitted ARIA attributes (7 elements)

    Elements must only use permitted ARIA attributes: 7 elements on the page fail this check, rated serious by axe-core.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 4 text elements with low contrast

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • Meta description is long (207 characters)

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

  • 550 internal links, 6 external

    The homepage links to 550 pages on hockeystickman.com and 6 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “BUILT BY HOCKEY PLAYERS, FOR HOCKEY PLAYERS.”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Hockey Equipment - Premium Hockey Gear at Unbeatable Prices”.

  • Canonical URL set

    The canonical URL is https://www.hockeystickman.com/.

  • 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://www.hockeystickman.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

3 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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,440 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.hockeystickman.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without an H1

    https://www.hockeystickman.com/pages/hsm-flyer-features, https://www.hockeystickman.com/collections/pro-blackout, https://www.hockeystickman.com/collections/all-hockey-sticks, https://www.hockeystickman.com/collections/senior-hockey-sticks, https://www.hockeystickman.com/collections/senior-new-pro-stock-hockey-sticks and https://www.hockeystickman.com/collections/senior-blackout-sticks and 9 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 199 found) and read each the way a search engine does.

6 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 7785
  • 9 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • A 17-field form

    Your longest form asks for 17 fields (0 required). Every extra field lowers completion.

  • 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 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 1,128 words of copy

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP PRO BLACKOUTS” and “SHOP FLYER DEALS -->”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “SHOP FLYER DEALS -->”, “SHOP PRO BLACKOUTS” and “Shop By League”.

  • Social proof on the page

    Social proof on the homepage: 71 testimonial or review blocks, a star rating and “22,000+ reviews”.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 2 mores (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.

  • 32 cookies set on arrival

    32

    Opening the homepage sets 32 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.

  • 58 other companies contacted

    Loading the homepage contacts 58 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 hockeystickman.com, 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 23 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Redo · Swatch King · Warnify Pro Warnings · Sc Product Options · Ta Labels Badges · Yotpo Loyalty Rewards · Password Lock Pages · Hulk Form Builder · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Black Crow Ai That Delivers · Yotpo Product Reviews · Hulk Discounts · Variant Image Swatch · Product Warnings · Trustedsite · Volume Discount By Hulkapps · Booster Kit By Qikify · Upcharge Fees · ywxi.net · hockeystickman.com · hubapi.com · Hulk Product Options

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
Hosting
Shopify

Company

Headquarters
Toronto

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on hockeystickman.com, including 17 speed issues, 1 SEO issue and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25