Website review, no card needed
hayabusafight.ca website review
Visit site (opens in a new tab)Reviewed 16 November 202640 issues · 90 checks
This review found 40 issues worth fixing on hayabusafight.ca, 17 of them high impact, across 90 checks. The most urgent: shopify adds 2.4 s. 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
70C- #98,292 of 117,615 reviewed websitesbeats 14%
- #60,175 of 66,923 online storesbeats 8%
- #55,783 of 61,018 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 206 ms |
| Jun 27, 2026 | 209 ms |
| Jul 4, 2026 | 206 ms |
| Jul 11, 2026 | 207 ms |
| Jul 18, 2026 | 211 ms |
| Jul 25, 2026 | 212 ms |
| Aug 1, 2026 | 212 ms |
| Aug 8, 2026 | 212 ms |
| Aug 15, 2026 | 216 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 219 ms |
| Sep 5, 2026 | 213 ms |
| Sep 12, 2026 | 205 ms |
| Sep 19, 2026 | 198 ms |
| Sep 26, 2026 | 202 ms |
| Oct 3, 2026 | 203 ms |
| Oct 10, 2026 | 205 ms |
| Oct 17, 2026 | 209 ms |
| Oct 24, 2026 | 205 ms |
| Oct 31, 2026 | 206 ms |
| Nov 7, 2026 | 212 ms |
| Nov 14, 2026 | 217 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
1.4 s
2.8 s
4.3 s
5.7 s
7.1 s
8.5 s
9.9 s
11.4 s
Speed
Shopify adds 2.4 s
2.4 sShopify costs a phone 2.4 s of main-thread work and 1.2 MB 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.
Reduce unused JavaScript
1.6 s · 762 KiBAbout 762 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Main-thread work: 11.0 s
A phone's processor spends 11.0 s on main-thread work while loading, 6.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
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,986 HTML elements
The page has 6,986 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, Facebook and TikTok and others), adding 2.2 MB and 3.5 s of main-thread time.
Render-blocking requests
850 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 440 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
390 KiB11 files are served with short cache lifetimes, so returning visitors download them again (390 KiB).
Facebook adds 354 ms
354 msFacebook costs a phone 354 ms of main-thread work and 223 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 217 ms
217 msKlaviyo costs a phone 217 ms of main-thread work and 317 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
74 KiBPolyfills for old browsers add 74 KiB JavaScript that modern phones do not need.
Improve image delivery
20 KiB1 image could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
13 KiBAbout 13 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.
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: 58 ms
58 msYour server sent the HTML in 58 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Speed Index: 18.3 s
18.3 sVisually, the page fills in at 18.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 26.7 s
26.7 sThe page becomes fully interactive after 26.7 s. Good is under 3.8 s.
Largest Contentful Paint: 9.1 s
9.1 sYour largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Video thumbnail”.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Real-user INP: 229 ms
229 msReal visitors wait 229 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
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.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 187 ms to 217 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.024
0.024The layout barely moves while loading (CLS 0.024, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 399 requests
5.4 MBYour homepage downloads 5.4 MB in 399 requests on a phone: images 2.5 MB (196), scripts 2.1 MB (121) and fonts 308 KiB (14). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
collabs_wrestling_nav_image.png 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 1.5 g of CO₂ per visit
1.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 184.2 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
Elements must only use permitted ARIA attributes (71 elements)
Elements must only use permitted ARIA attributes: 71 elements on the page fail this check, rated serious by axe-core.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
51 form fields without a label
51 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), 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. (4 elements).
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 3 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.
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Hayabusa • Boxing Gloves, Equipment & Jiu Jitsu Gis | Hayabusa Canada”.
Meta description is long (176 characters)
Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
179 internal links, 6 external
The homepage links to 179 pages on hayabusafight.ca and 6 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.hayabusafight.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://www.hayabusafight.ca/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
42%The HTML your server sends has 727 of the 1,747 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.hayabusafight.ca/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.
2 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 contact details; sameAs (social profiles) and description would complete it.
Other pages
1 page without an H1
https://www.hayabusafight.ca/pages/wholesale-information has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.hayabusafight.ca/collections/hybrid-and-mma-gloves, https://www.hayabusafight.ca/collections/bag-gloves, https://www.hayabusafight.ca/collections/sparring-gloves and https://www.hayabusafight.ca/collections/glove-deodorizers took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 122 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
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=283007090&tm=gtm002&Ver=2&mid=16f78685-776b-40da-8974-c6a1fded4573&bo=1&sid=ac15d870e21511f18ae7dd9256d5afd9&vid=ac15bb70e21511f1b5eacdcb62cd1769&vids=1&msclkid=N&pi=9.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Loading the font 'https://cdn-static.okendo.io/reviews-widget-plus/fonts/oke-widget-icons.fbb067ad.ttf' violates the fo…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
169 of 176 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 1,747 words of copy
The homepage carries about 1,747 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL”.
19 calls to action
The homepage has 19 calls to action, for example “Learn More”, “Shop All” and “Shop Now”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: PostHog.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Klaviyo, Meta Pixel and Microsoft Ads 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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
35 other companies contacted
Loading the homepage contacts 35 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 hayabusafight.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on hayabusafight.ca, including 21 speed issues, 4 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.