Website review, no card needed
swifthockey.com website review
Visit site (opens in a new tab)Reviewed 12 November 202616 issues · 74 checks
This review found 16 issues worth fixing on swifthockey.com, 5 of them high impact, across 74 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
95A- #104 of 120,852 reviewed websitesbeats 100%
- #28 of 68,414 online storesbeats 100%
- #28 of 62,341 Shopify storesbeats 100%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 929 ms |
| Jul 11, 2026 | 825 ms |
| Jul 18, 2026 | 812 ms |
| Jul 25, 2026 | 813 ms |
| Aug 1, 2026 | 812 ms |
| Aug 8, 2026 | 802 ms |
| Aug 15, 2026 | 808 ms |
| Aug 22, 2026 | 826 ms |
| Aug 29, 2026 | 845 ms |
| Sep 5, 2026 | 869 ms |
| Sep 12, 2026 | 878 ms |
| Sep 19, 2026 | 834 ms |
| Sep 26, 2026 | 771 ms |
| Oct 3, 2026 | 682 ms |
| Oct 10, 2026 | 628 ms |
| Oct 17, 2026 | 618 ms |
| Oct 24, 2026 | 615 ms |
| Oct 31, 2026 | 635 ms |
| Nov 7, 2026 | 616 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 141 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 165 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 169 ms |
| Sep 12, 2026 | 172 ms |
| Sep 19, 2026 | 174 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 173 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 180 ms |
| Oct 31, 2026 | 180 ms |
| Nov 7, 2026 | 171 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
6,091 HTML elements
The page has 6,091 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 22 KiB5 files are served with short cache lifetimes, so returning visitors download them again (22 KiB).
Improve image delivery
50 KiB2 images could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
4 third-party services on the page
4 third-party services load with your homepage (Shopify, Klaviyo and shop.app and others), adding 260 KiB and 3 ms of main-thread time.
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
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.
3 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96. That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 82 ms of it running JavaScript. That is comfortably low.
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 141 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
12 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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 155 ms
155 msReal visitors wait 155 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 492 ms
492 msReal visitors wait 492 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 65% faster for real visitors
-65%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.2 s
2.2 sYour largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold.
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
Time to Interactive: 2.2 s
2.2 sThe page is fully interactive after 2.2 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
5 images in older formats
5 images (257 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.
About 0.4 g of CO₂ per visit
0.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.37 g of CO₂e: 44.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.3 MB in 98 requests
1.3 MBYour homepage downloads 1.3 MB in 98 requests on a phone: images 652 KiB (16), scripts 478 KiB (58) and HTML 122 KiB (1). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (109 elements)
All page content should be contained by landmarks: 109 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
49 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: 49 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
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
One H1 headline
Your <h1> is empty.
134 internal links, 12 external
The homepage links to 134 pages on swifthockey.com and 12 external pages.
6 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Swift Hockey offers top-of-the-line hockey sticks at unbeatable prices. Get pro-level performance without the premium p…”.
Title: 58 characters
Your title is a healthy 58 characters: “Swift Hockey - Premium hockey sticks for affordable prices”.
Canonical URL set
The canonical URL is https://swifthockey.com/.
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://swifthockey.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
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,173 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://swifthockey.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://swifthockey.com/collections/main, https://swifthockey.com/pages/hockey, https://swifthockey.com/collections/sticks, https://swifthockey.com/collections/accessories, https://swifthockey.com/pages/pickleball and https://swifthockey.com/collections/paddles and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://swifthockey.com/collections/main, https://swifthockey.com/collections, https://swifthockey.com/pages/hockey, https://swifthockey.com/collections/sticks, https://swifthockey.com/collections/accessories and https://swifthockey.com/pages/pickleball 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 51 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
14 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 803 words of copy
The homepage carries about 803 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “STICKS SHOP”.
20 calls to action
The homepage has 20 calls to action, for example “Shop now”, “Contact Us” and “Loading image: STICKS SHOP”.
7 short forms
7 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 35 testimonial or review blocks, 12 customer or partner logos, a star rating and “2500+ Reviews”.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
5 other companies contacted
Loading the homepage contacts 5 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 swifthockey.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Judge Me Reviews · Aftership Personalization · Microsoft Clarity · Triplewhale · Restockrocket · automizely.com · cloudfront.net · intercom.io · sealsubscriptions.com · hubapi.com · shopbooster.co
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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 16 issues on swifthockey.com, including 5 speed issues and 2 SEO issues. 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.