Website review, no card needed

sixzerocanada.com logo

sixzerocanada.com website review

Visit site (opens in a new tab)Reviewed 16 November 202639 issues · 87 checks

This review found 39 issues worth fixing on sixzerocanada.com, 15 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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.4 s1.5 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.9 s
Nov 7, 20262.1 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
217 ms119 msMay 30Nov 14196 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026134 ms
Jun 6, 2026130 ms
Jun 13, 2026135 ms
Jun 20, 2026133 ms
Jun 27, 2026142 ms
Jul 4, 2026153 ms
Jul 11, 2026161 ms
Jul 18, 2026170 ms
Jul 25, 2026181 ms
Aug 1, 2026186 ms
Aug 8, 2026183 ms
Aug 15, 2026184 ms
Aug 22, 2026187 ms
Aug 29, 2026187 ms
Sep 5, 2026189 ms
Sep 12, 2026191 ms
Sep 19, 2026196 ms
Sep 26, 2026191 ms
Oct 3, 2026191 ms
Oct 10, 2026194 ms
Oct 17, 2026194 ms
Oct 24, 2026195 ms
Oct 31, 2026203 ms
Nov 7, 2026206 ms
Nov 14, 2026196 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 sixzerocanada.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sixzerocanada.com at 1.9 s1.9 s
  2. sixzerocanada.com at 3.8 s3.8 s
  3. sixzerocanada.com at 5.7 s5.7 s
  4. sixzerocanada.com at 7.6 s7.6 s
  5. sixzerocanada.com at 9.5 s9.5 s
  6. sixzerocanada.com at 11.4 s11.4 s
  7. sixzerocanada.com at 13.3 s13.3 s
  8. sixzerocanada.com at 15.2 s15.2 s

Speed

14 to fix34
  • Reduce unused JavaScript

    2.7 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Google Tag Manager adds 1.7 s

    1.7 s

    Google Tag Manager costs a phone 1.7 s of main-thread work and 519 KiB 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.

  • Main-thread work: 17.9 s

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

  • route.com adds 1.4 s

    1.4 s

    route.com costs a phone 1.4 s of main-thread work and 1.1 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.

  • Shopify adds 1.1 s

    1.1 s

    Shopify costs a phone 1.1 s of main-thread work and 902 KiB 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.

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,349 HTML elements

    The page has 3,349 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 (Google Tag Manager, route.com and Shopify and others), adding 2.9 MB and 5.8 s of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 1.4 MB

    16 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

  • Render-blocking requests

    900 ms

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

  • Duplicated JavaScript

    485 KiB

    485 KiB JavaScript is shipped twice across bundles.

  • Facebook adds 409 ms

    409 ms

    Facebook costs a phone 409 ms of main-thread work and 226 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.

  • minmaxify.com adds 368 ms

    368 ms

    minmaxify.com costs a phone 368 ms of main-thread work and 10 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

    150 ms · 110 KiB

    Polyfills for old browsers add 110 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    103 KiB

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

  • Improve image delivery

    55 KiB

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 33 ms

    33 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 15.0 s

    15.0 s

    Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 19.9 s

    19.9 s

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

  • Total Blocking Time: 4.7 s

    4.7 s

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

  • Time to Interactive: 31.8 s

    31.8 s

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

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

    +52%

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

  • Largest content (LCP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.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.7 s

    1.7 s

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

  • Real-user INP: 146 ms

    146 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 384 ms

    384 ms

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

  • First Contentful Paint: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.048

    0.048

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

Images and page weight

3 to fix60
  • Page weight: 5.3 MB in 319 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 319 requests on a phone: scripts 3.1 MB (102), other files 969 KiB (155) and images 928 KiB (44). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    MOBILE_1_07460fcc-3099-423a-ab30-316d87588996.jpg 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).

  • 2 images far larger than shown

    81 KiB

    2 images are downloaded at several times the size a phone draws them, for example Dale_Workshop_Photo.jpg at 1,263 px wide, shown at 390 px. Resized copies would save about 81 KiB.

  • 2 images in older formats

    2 images (150 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.

  • 1 image below the first screen load straight away

    1 image further down the page (122 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.51 g

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

Accessibility

5 to fixGoogle 9794
  • 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.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 23 links without text

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

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

5 to fixGoogle 8574
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (15 characters)

    Your title is only 15 characters: “Six Zero Canada”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • 269 internal links, 6 external

    The homepage links to 269 pages on sixzerocanada.com and 6 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Six Zero Canada”.

  • Canonical URL set

    The canonical URL is https://sixzerocanada.com/.

  • 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://sixzerocanada.com/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 (2,261 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://sixzerocanada.com/collections/65-off, https://sixzerocanada.com/collections/50-off, https://sixzerocanada.com/collections/25-off and https://sixzerocanada.com/collections/20-off have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://sixzerocanada.com/collections/black-friday-sale, https://sixzerocanada.com/collections/65-off, https://sixzerocanada.com/collections/50-off, https://sixzerocanada.com/collections/25-off, https://sixzerocanada.com/collections/20-off and https://sixzerocanada.com/collections/paddles and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://sixzerocanada.com/collections/paddles, https://sixzerocanada.com/collections/next-gem-series and https://sixzerocanada.com/products/coral-rainbow-edition-16mm took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 87 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

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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,774 words of copy

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop Black Friday”, “Learn More” and “Learn more”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 136 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 1 of them by other companies (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.

  • 49 other companies contacted

    Loading the homepage contacts 49 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 sixzerocanada.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 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Klaviyo Email Marketing Sms · Judge Me Reviews · Eg Auto Add To Cart · Powerful Form Builder · Pagefly Ai Page Builder · Minmaxify Order Limits · Uppromote Affiliate · Notification Pro · Hreflang Tags · Swatch King · Gdpr Cookie Consent · Variant Image Swatch · Restockrocket · Essential Post Purchase Upsell · Tms Prod V Ae290ce · route.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 Tag Manager | 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 39 issues on sixzerocanada.com, including 19 speed issues, 5 SEO issues and 1 conversion gap. 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