Website review, no card needed

gorillabow.ca logo

gorillabow.ca website review

Visit site (opens in a new tab)Reviewed 8 November 202641 issues · 82 checks

This review found 41 issues worth fixing on gorillabow.ca, 10 of them high impact, across 82 checks. The most urgent: page weight: 19.0 MB in 356 requests. 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

Full-page screenshot of gorillabow.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gorillabow.ca at 0.4 s0.4 s
  2. gorillabow.ca at 0.8 s0.8 s
  3. gorillabow.ca at 1.3 s1.3 s
  4. gorillabow.ca at 1.7 s1.7 s
  5. gorillabow.ca at 2.1 s2.1 s
  6. gorillabow.ca at 2.5 s2.5 s
  7. gorillabow.ca at 2.9 s2.9 s
  8. gorillabow.ca at 3.4 s3.4 s

Speed

11 to fix54
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, zotabox.com and Klaviyo and others), adding 2.3 MB and 1.0 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 54

    54/100

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

  • Use efficient cache lifetimes

    498 KiB

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

  • Main-thread work: 3.3 s

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

  • Render-blocking requests

    300 ms

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

  • 9 long tasks on the main thread

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

  • Google Tag Manager adds 214 ms

    214 ms

    Google Tag Manager costs a phone 214 ms of main-thread work and 303 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.

  • zotabox.com adds 165 ms

    165 ms

    zotabox.com costs a phone 165 ms of main-thread work and 548 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 146 ms

    146 ms

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

  • ZenDesk adds 118 ms

    118 ms

    ZenDesk costs a phone 118 ms of main-thread work and 394 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

    139 KiB

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

  • Improve image delivery

    66 KiB

    3 images could be 66 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    52 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify JavaScript

    35 KiB

    35 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 5 ms

    5 ms

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

Core Web Vitals

6 to fix64
  • Time to Interactive: 28.0 s

    28.0 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

    The first text or image appears after 5.0 s on a phone. Good is under 1.8 s.

  • Speed Index: 8.1 s

    8.1 s

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

  • Largest Contentful Paint: 5.0 s

    5.0 s

    Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ANYWHERE YOU WANT TO BE”. Most of its time is element render delay (2.4 s).

  • Total Blocking Time: 432 ms

    432 ms

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

  • 17 images without width and height

    17 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 19.0 MB in 356 requests

    19.0 MB

    Your homepage downloads 19.0 MB in 356 requests on a phone: media 14.6 MB (1), scripts 2.7 MB (137) and other files 1.0 MB (159). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (36 KiB) is 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 5.4 g of CO₂ per visit

    5.37 g

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

2 checks passed
  • 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

6 to fixGoogle 8492
  • Invalid ARIA attributes

    6 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

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

  • button, link, and menuitem elements do not have accessible names.

    button, link, and menuitem elements do not have accessible names. (1 element).

  • 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
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • Title is long (86 characters)

    Your title is 86 characters, so Google will cut it off around 60: “Upgrade Your Workout with Gorilla Bow Home Gym Equipment | Canada – Gorilla Bow Canada”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “A TOTAL BODY WORKOUT ANYWHERE YOU WANT TO BE”). One clear main headline is easier for people and search engines.

  • 50 internal links, 30 external

    The homepage links to 50 pages on gorillabow.ca and 30 external pages.

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Gorilla Bow workouts are Resistance Training that improves your balance, reduces joint pain, tones, and builds muscle. …”.

  • Canonical URL set

    The canonical URL is https://gorillabow.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://gorillabow.ca/sitemap.xml.

AI search readiness

1 to fix88
  • 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 (429 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://gorillabow.ca/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 4 pages share 2 titles

    https://gorillabow.ca/collections/bows and https://gorillabow.ca/collections/the-bow all use the title “Resistance Bar with Bands | Collection | Gorilla Bow – Gorilla Bow Ca…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://gorillabow.ca/collections/thebows, https://gorillabow.ca/products/gorilla-bow-lite, https://gorillabow.ca/collections/on-demand-training, https://gorillabow.ca/pages/reviews-1, https://gorillabow.ca/pages/gorilla-gang and https://gorillabow.ca/blogs/news and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://gorillabow.ca/collections/bows and https://gorillabow.ca/collections/the-bow use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://gorillabow.ca/pages/reviews-1, whose canonical is https://gorillabow.ca/pages/community-reviews. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

5 to fixGoogle 7369
  • 2 broken images

    2 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0236/0325/files/banner-button_600x.png?v=1571319561.

  • 12 small tap targets

    12 of 28 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.”).

  • 2 JavaScript errors while loading

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

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • Thin social proof

    Social proof on the homepage: 36 testimonial or review blocks. 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.

  • About 343 words of copy

    The homepage carries about 343 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Get Started”, “Contact Us” and “Register Your Bow”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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, Klaviyo and Meta Pixel 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.

  • 25 cookies set on arrival

    25

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

  • 51 other companies contacted

    Loading the homepage contacts 51 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 gorillabow.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

jsdelivr.net · klaviyo.com · icyhill.com · zotabox.com · automizely.com · loox.io · web.app · personalizer.io · spicegems.org · hextom.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 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 41 issues on gorillabow.ca, including 17 speed issues, 3 SEO issues 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