Website review, no card needed

bugasalt.ca logo

bugasalt.ca website review

Visit site (opens in a new tab)Reviewed 21 November 202634 issues · 85 checks

This review found 34 issues worth fixing on bugasalt.ca, 7 of them high impact, across 85 checks. The most urgent: page weight: 19.8 MB in 459 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

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.1 sMay 30Nov 141.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.4 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.4 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.2 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Nov 7, 20261.3 s
Nov 14, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
136 ms100 msMay 30Nov 14128 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026104 ms
Jun 6, 2026105 ms
Jun 13, 2026107 ms
Jun 20, 2026108 ms
Jun 27, 2026109 ms
Jul 4, 2026112 ms
Jul 11, 2026114 ms
Jul 18, 2026121 ms
Jul 25, 2026127 ms
Aug 1, 2026129 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026128 ms
Aug 29, 2026121 ms
Sep 5, 2026121 ms
Sep 12, 2026122 ms
Sep 19, 2026127 ms
Sep 26, 2026127 ms
Oct 3, 2026128 ms
Oct 10, 2026128 ms
Oct 17, 2026132 ms
Oct 24, 2026130 ms
Oct 31, 2026129 ms
Nov 7, 2026129 ms
Nov 14, 2026128 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 bugasalt.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bugasalt.ca at 4.3 s4.3 s
  2. bugasalt.ca at 8.5 s8.5 s
  3. bugasalt.ca at 12.8 s12.8 s
  4. bugasalt.ca at 17.0 s17.0 s
  5. bugasalt.ca at 21.3 s21.3 s
  6. bugasalt.ca at 25.5 s25.5 s
  7. bugasalt.ca at 29.8 s29.8 s
  8. bugasalt.ca at 34.1 s34.1 s

Speed

10 to fix76
  • Main-thread work: 13.1 s

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

  • Render-blocking requests

    1.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Klaviyo and Shopify and others), adding 17.5 MB and 1.4 s of main-thread time.

  • Shopify adds 130 ms

    130 ms

    Shopify costs a phone 130 ms of main-thread work and 16.3 MB 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.

  • Mobile performance score: 76

    76/100

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

  • Reduce unused JavaScript

    300 ms · 570 KiB

    About 570 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Clarity adds 717 ms

    717 ms

    Clarity costs a phone 717 ms of main-thread work and 30 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

    376 KiB

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

  • Klaviyo adds 178 ms

    178 ms

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

  • 1,992 HTML elements

    The page has 1,992 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    78 KiB

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

  • Font display

    50 ms

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

  • Improve image delivery

    46 KiB

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

  • Legacy JavaScript

    39 KiB

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

  • Minify CSS

    10 KiB

    10 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: 6 ms

    6 ms

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

Core Web Vitals

6 to fix100
  • Speed Index: 20.6 s

    20.6 s

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

  • Time to Interactive: 17.0 s

    17.0 s

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

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

    +23%

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

  • Total Blocking Time: 430 ms

    430 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 6 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

    1.5 s

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

  • Real-user INP: 141 ms

    141 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 381 ms

    381 ms

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “EARLY BLACK FRIDAY: $25 OFF ALL BUG-BEAM COMBOS!”.

  • 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.8 MB in 459 requests

    19.8 MB

    Your homepage downloads 19.8 MB in 459 requests on a phone: media 16.0 MB (1), scripts 1.5 MB (106) and other files 1.5 MB (273). Under 2 MB keeps phones on slow connections fast.

  • About 5.6 g of CO₂ per visit

    5.60 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

2 to fixGoogle 10088
  • Title is short (17 characters)

    Your title is only 17 characters: “Bug-A-Salt Canada”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (211 characters)

    Your meta description is 211 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 43 internal links, 11 external

    The homepage links to 43 pages on bugasalt.ca and 11 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Bug-A-Salt Canada”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage.

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

  • llms.txt published

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

Other pages

4 to fix83
  • 6 pages without a meta description

    https://www.bugasalt.ca/collections/all-range, https://www.bugasalt.ca/pages/meet-bug-a-salt-3-0, https://www.bugasalt.ca/pages/bundles, https://www.bugasalt.ca/pages/where-to-buy, https://www.bugasalt.ca/collections/early-black-friday and https://www.bugasalt.ca/collections/3-0-singles have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.bugasalt.ca/collections/3-0-singles/products/bug-a-salt-3-0-yellow and https://www.bugasalt.ca/collections/3-0-combo/products/bug-a-salt-3-0-yellow-combo-pack use the same meta description. A description written for each page earns more clicks.

  • 8 links to non-canonical URLs

    Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.bugasalt.ca/collections/3-0-singles/products/bug-a-salt-3-0-yellow, whose canonical is https://www.bugasalt.ca/products/bug-a-salt-3-0-yellow. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://www.bugasalt.ca/collections/all-range, https://www.bugasalt.ca/pages/meet-bug-a-salt-3-0, https://www.bugasalt.ca/pages/where-to-buy, https://www.bugasalt.ca/collections/early-black-friday and https://www.bugasalt.ca/collections/3-0-singles 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 29 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136011762&Ver=2&mid=81a7d9c6-9136-44f1-ab08-8116195bada9&bo=1&sid=89833d40e59311f19513fd606500fd4b&vid=898338b0e59311f19ad09bec89442a77&vids=1&msclkid=N&pi=918639831&l.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

2 checks passed
  • Tap targets are thumb-sized

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

  • 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 980 words of copy

    The homepage carries about 980 words of visible text.

  • Urgency cues

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy Now”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “SHOP”, “Where to buy” and “Buy Now”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, a star rating and “53,265+ Happy customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 22 cookies set on arrival

    22

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

  • 38 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Monster Cart Upsell Free Gifts · Okendo · Fbp Fast Bundle · Monster Upsells · therealbugasalt.ca

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
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on bugasalt.ca, including 16 speed issues, 2 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