Website review, no card needed

blackboxmycar.ca logo

blackboxmycar.ca website review

Visit site (opens in a new tab)Reviewed 19 November 202639 issues · 94 checks

This review found 39 issues worth fixing on blackboxmycar.ca, 18 of them high impact, across 94 checks. The most urgent: reduce unused CSS. 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.2 s1.6 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
185 ms139 msMay 30Nov 14173 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026145 ms
Jun 6, 2026145 ms
Jun 13, 2026144 ms
Jun 20, 2026145 ms
Jun 27, 2026151 ms
Jul 4, 2026154 ms
Jul 11, 2026154 ms
Jul 18, 2026162 ms
Jul 25, 2026164 ms
Aug 1, 2026168 ms
Aug 8, 2026173 ms
Aug 15, 2026177 ms
Aug 22, 2026177 ms
Aug 29, 2026180 ms
Sep 5, 2026176 ms
Sep 12, 2026164 ms
Sep 19, 2026161 ms
Sep 26, 2026159 ms
Oct 3, 2026161 ms
Oct 10, 2026162 ms
Oct 17, 2026164 ms
Oct 24, 2026168 ms
Oct 31, 2026172 ms
Nov 7, 2026175 ms
Nov 14, 2026173 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 blackboxmycar.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. blackboxmycar.ca at 0.8 s0.8 s
  2. blackboxmycar.ca at 1.7 s1.7 s
  3. blackboxmycar.ca at 2.5 s2.5 s
  4. blackboxmycar.ca at 3.4 s3.4 s
  5. blackboxmycar.ca at 4.2 s4.2 s
  6. blackboxmycar.ca at 5.1 s5.1 s
  7. blackboxmycar.ca at 5.9 s5.9 s
  8. blackboxmycar.ca at 6.8 s6.8 s

Speed

15 to fix43
  • Reduce unused CSS

    1.5 s · 406 KiB

    About 406 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Main-thread work: 16.9 s

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

  • Shopify adds 1.1 s

    1.1 s

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

  • Render-blocking requests

    1.4 s

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • POWr adds 1.2 s

    1.2 s

    POWr costs a phone 1.2 s of main-thread work and 13 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: 43

    43/100

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

  • 6,885 HTML elements

    The page has 6,885 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 (POWr, Shopify and Klaviyo and others), adding 5.1 MB and 3.3 s of main-thread time.

  • Improve image delivery

    250 ms · 1.5 MB

    19 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Reduce unused JavaScript

    1.3 MB

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

  • 14 long tasks on the main thread

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

  • Klaviyo adds 313 ms

    313 ms

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

  • Use efficient cache lifetimes

    264 KiB

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

  • rebuyengine.com adds 158 ms

    158 ms

    rebuyengine.com costs a phone 158 ms of main-thread work and 687 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.

  • Google CDN adds 111 ms

    111 ms

    Google CDN costs a phone 111 ms of main-thread work and 298 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.

  • Minify CSS

    150 ms · 38 KiB

    38 KiB could be saved by minifying CSS.

  • Minify JavaScript

    104 KiB

    104 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    62 KiB

    Polyfills for old browsers add 62 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).

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

    21 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 35.4 s

    35.4 s

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

  • Speed Index: 12.3 s

    12.3 s

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

  • Largest Contentful Paint: 7.1 s

    7.1 s

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

  • Total Blocking Time: 994 ms

    994 ms

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

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

    +20%

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

9 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.3 s

    1.3 s

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

  • Real-user INP: 188 ms

    188 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 283 ms

    283 ms

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

  • Largest content (LCP) got 23% faster for real visitors

    -23%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.076

    0.076

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

Images and page weight

3 to fix60
  • Page weight: 9.3 MB in 425 requests

    9.3 MB

    Your homepage downloads 9.3 MB in 425 requests on a phone: images 4.3 MB (68), scripts 2.7 MB (120) and other files 1.3 MB (192). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    BlackboxMyCar_-_Logo_-_Color_-_Canada_48cc6df5-ca4c-4403-bb4 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).

  • 1 image far larger than shown

    117 KiB

    1 image is downloaded at several times the size a phone draws it, for example thinkware-f70-pro-1-channel-full-hd-wifi-dash-cam-dash-cams- at 2,133 px wide, shown at 96 px. Resized copies would save about 117 KiB.

  • 2 images in older formats

    2 images (270 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 (47 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.6 g of CO₂ per visit

    2.63 g

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

Accessibility

6 to fixGoogle 8492
  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (7 elements).

1 checks passed
  • 55 automated accessibility rules passed

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

SEO

Google 92100
  • 286 internal links, 13 external

    The homepage links to 286 pages on blackboxmycar.ca and 13 external pages.

8 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Shop premium dash cams, radar detectors and accessories at BlackboxMyCar Canada. Expert support, free shipping, easy re…”.

  • One H1 headline

    Your main headline reads: “North America's Dash Cam Experts”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “BlackboxMyCar Canada | Dash Cams & Car Accessories”.

  • Canonical URL set

    The canonical URL is https://www.blackboxmycar.ca/.

  • Structured data in place

    Structured data found: 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.blackboxmycar.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 (2,417 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix52
  • 1 linked page is broken

    Your homepage links to https://www.blackboxmycar.ca/customer_authentication/redirect, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages point its canonical at the homepage

    https://www.blackboxmycar.ca/products/blackvue-elite-10-2-channel-4k-hdr-dash-cam, https://www.blackboxmycar.ca/products/viofo-a329s-4k-2k-2-channel-60fps-wi-fi-6-dash-cam, https://www.blackboxmycar.ca/products/viofo-a229-ultra-4k-4k-2-channel-30fps-uhd-dash-cam and https://www.blackboxmycar.ca/products/blackvue-dr970x-2ch-lte-plus-ii-4k-uhd-cloud-dash-cam declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 5 pages share a title

    /, https://www.blackboxmycar.ca/products/blackvue-elite-10-2-channel-4k-hdr-dash-cam, https://www.blackboxmycar.ca/products/viofo-a329s-4k-2k-2-channel-60fps-wi-fi-6-dash-cam, https://www.blackboxmycar.ca/products/viofo-a229-ultra-4k-4k-2-channel-30fps-uhd-dash-cam and https://www.blackboxmycar.ca/products/blackvue-dr970x-2ch-lte-plus-ii-4k-uhd-cloud-dash-cam all use the title “BlackboxMyCar Canada | Dash Cams & Car Accessories”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.blackboxmycar.ca/products/blackvue-elite-10-2-channel-4k-hdr-dash-cam, https://www.blackboxmycar.ca/products/viofo-a329s-4k-2k-2-channel-60fps-wi-fi-6-dash-cam, https://www.blackboxmycar.ca/products/viofo-a229-ultra-4k-4k-2-channel-30fps-uhd-dash-cam and https://www.blackboxmycar.ca/products/blackvue-dr970x-2ch-lte-plus-ii-4k-uhd-cloud-dash-cam use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://www.blackboxmycar.ca/collections/sales-and-deals, https://www.blackboxmycar.ca/products/viofo-a229-plus-2k-qhd-2-channel-dash-cam, https://www.blackboxmycar.ca/products/viofo-a229-pro-4k-uhd-2-ch-dash-cam, https://www.blackboxmycar.ca/products/thinkware-u3000-pro-2ch-4k-30fps-2k-30fps-with-obd-ii-cable, https://www.blackboxmycar.ca/products/blackvue-elite-10-2-channel-4k-hdr-dash-cam and https://www.blackboxmycar.ca/products/viofo-a329s-4k-2k-2-channel-60fps-wi-fi-6-dash-cam and 8 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 111 found) and read each the way a search engine does.

3 checks passed
  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    27 of 28 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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.

  • About 638 words of copy

    The homepage carries about 638 words of visible text.

  • Urgency cues

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

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us” and “Shop Black Friday →”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “Contact” and “Shop Black Friday→”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 257 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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
  • 5 trackers load before any consent

    5

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

  • 22 cookies set on arrival

    22

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

  • 47 other companies contacted

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

Apps your storefront loads

Boost Ai Search Filter · Google Youtube · Judge Me Reviews · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Black Crow Ai That Delivers · Rebuy Personalization Engine · Revenuehunt · Surebright Extended Warranty · powr.io · 9gtb.com · shipinsure.io

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 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 39 issues on blackboxmycar.ca, including 20 speed 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