Website review, no card needed
sourceforsports.ca website review
Visit site (opens in a new tab)Reviewed 4 November 202627 issues · 78 checks
This review found 27 issues worth fixing on sourceforsports.ca, 5 of them high impact, across 78 checks. The most urgent: aRIA attributes must conform to valid values (1 element). 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
86B- #9,909 of 98,971 reviewed websitesbeats 86%
- #5,902 of 54,142 online storesbeats 84%
- #5,720 of 49,115 Shopify storesbeats 83%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 907 ms |
| May 23, 2026 | 893 ms |
| May 30, 2026 | 883 ms |
| Jun 6, 2026 | 874 ms |
| Jun 13, 2026 | 868 ms |
| Jun 20, 2026 | 868 ms |
| Jun 27, 2026 | 857 ms |
| Jul 4, 2026 | 849 ms |
| Jul 11, 2026 | 839 ms |
| Jul 18, 2026 | 831 ms |
| Jul 25, 2026 | 824 ms |
| Aug 1, 2026 | 818 ms |
| Aug 8, 2026 | 820 ms |
| Aug 15, 2026 | 827 ms |
| Aug 22, 2026 | 837 ms |
| Aug 29, 2026 | 856 ms |
| Sep 5, 2026 | 871 ms |
| Sep 12, 2026 | 879 ms |
| Sep 19, 2026 | 886 ms |
| Sep 26, 2026 | 882 ms |
| Oct 3, 2026 | 873 ms |
| Oct 10, 2026 | 868 ms |
| Oct 17, 2026 | 866 ms |
| Oct 24, 2026 | 859 ms |
| Oct 31, 2026 | 863 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 88 ms |
| May 23, 2026 | 88 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 89 ms |
| Jun 13, 2026 | 90 ms |
| Jun 20, 2026 | 91 ms |
| Jun 27, 2026 | 92 ms |
| Jul 4, 2026 | 92 ms |
| Jul 11, 2026 | 93 ms |
| Jul 18, 2026 | 93 ms |
| Jul 25, 2026 | 94 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 98 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 105 ms |
| Aug 29, 2026 | 109 ms |
| Sep 5, 2026 | 110 ms |
| Sep 12, 2026 | 108 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 104 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
Reduce unused JavaScript
900 ms · 182 KiBAbout 182 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Render-blocking requests
350 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
2,039 HTML elements
The page has 2,039 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
245 KiB12 images could be 245 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 176 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Shopify and Adobe TypeKit and others), adding 327 KiB and 105 ms of main-thread time.
Use efficient cache lifetimes
5 KiB4 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 690 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.6 s
7.6 sYour largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 7.8 s
7.8 sThe page becomes fully interactive after 7.8 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
53 images without width and height
53 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 88 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 91 ms
91 msReal visitors wait 91 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.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 339 ms
339 msReal visitors wait 339 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 146 ms
146 msScripts block the page for only 146 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.5 MB in 212 requests
2.5 MBYour homepage downloads 2.5 MB in 212 requests on a phone: images 1.0 MB (59), other files 835 KiB (109) and scripts 552 KiB (35). Under 2 MB keeps phones on slow connections fast.
13 images below the first screen load straight away
13 images further down the page (477 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 83.4 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
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 46 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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 H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
45 internal links, 7 external
The homepage links to 45 pages on sourceforsports.ca and 7 external pages.
6 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Shop Sports Equipment Online At Source for Sports, Canada's Largest Locally Owned Sporting Goods Stores. We Carry The B…”.
Title: 48 characters
Your title is a healthy 48 characters: “Source for Sports Equipment Stores | Shop Online”.
Canonical URL set
The canonical URL is https://www.sourceforsports.ca/.
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.sourceforsports.ca/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 (510 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.sourceforsports.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://www.sourceforsports.ca/collections/mini-sticks/brand_bauer, https://www.sourceforsports.ca/collections/clearance, https://www.sourceforsports.ca/collections/hockey-equipment, https://www.sourceforsports.ca/collections/baseball-softball-equipment, https://www.sourceforsports.ca/collections/shoes-footwear and https://www.sourceforsports.ca/collections/womens-clothing-footwear-accessories and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.sourceforsports.ca/collections/mini-sticks/brand_bauer, https://www.sourceforsports.ca/collections/clearance, https://www.sourceforsports.ca/collections/hockey-equipment, https://www.sourceforsports.ca/collections/baseball-softball-equipment, https://www.sourceforsports.ca/collections/shoes-footwear and https://www.sourceforsports.ca/collections/womens-clothing-footwear-accessories and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 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
7 small tap targets
7 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 786 words of copy
The homepage carries about 786 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: “Learn more.”.
10 calls to action
The homepage has 10 calls to action, for example “Shop Now”, “Learn More” and “Get a Quote”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
8 other companies contacted
Loading the homepage contacts 8 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 sourceforsports.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Employees
- 250
- Headquarters
- Burlington
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on sourceforsports.ca, including 10 speed issues, 3 SEO issues and 2 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.