Website review, no card needed
bullybunches.ca website review
Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 87 checks
This review found 43 issues worth fixing on bullybunches.ca, 17 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71C- #100,952 of 125,402 reviewed websitesbeats 17%
- #61,458 of 70,171 online storesbeats 10%
- #56,981 of 63,759 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 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.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 188 ms |
| May 23, 2026 | 194 ms |
| May 30, 2026 | 199 ms |
| Jun 6, 2026 | 208 ms |
| Jun 13, 2026 | 211 ms |
| Jun 20, 2026 | 202 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 197 ms |
| Jul 18, 2026 | 205 ms |
| Jul 25, 2026 | 220 ms |
| Aug 1, 2026 | 227 ms |
| Aug 8, 2026 | 229 ms |
| Aug 15, 2026 | 230 ms |
| Aug 22, 2026 | 230 ms |
| Aug 29, 2026 | 231 ms |
| Sep 5, 2026 | 233 ms |
| Sep 12, 2026 | 237 ms |
| Sep 19, 2026 | 240 ms |
| Sep 26, 2026 | 239 ms |
| Oct 3, 2026 | 241 ms |
| Oct 10, 2026 | 241 ms |
| Oct 17, 2026 | 243 ms |
| Oct 24, 2026 | 245 ms |
| Oct 31, 2026 | 245 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.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.7 s
8.8 s
Speed
Reduce unused JavaScript
4.8 s · 1,019 KiBAbout 1,019 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Use efficient cache lifetimes
4.0 s · 678 KiB26 files are served with short cache lifetimes, so returning visitors download them again (678 KiB).
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,558 HTML elements
The page has 4,558 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
50 ms · 2.2 MB34 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (alia-prod.com, loox.io and rebuyengine.com and others), adding 3.9 MB and 1.1 s of main-thread time.
Reduce unused CSS
760 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.
Legacy JavaScript
450 ms · 77 KiBPolyfills for old browsers add 77 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
alia-prod.com adds 299 ms
299 msalia-prod.com costs a phone 299 ms of main-thread work and 1.8 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.
Render-blocking requests
450 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
loox.io adds 241 ms
241 msloox.io costs a phone 241 ms of main-thread work and 805 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.
rebuyengine.com adds 134 ms
134 msrebuyengine.com costs a phone 134 ms of main-thread work and 359 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.
Shopify adds 102 ms
102 msShopify costs a phone 102 ms of main-thread work and 399 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 102 ms
102 msKlaviyo costs a phone 102 ms of main-thread work and 307 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 155 ms. During a long task the page ignores taps.
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: 8 ms
8 msYour server sent the HTML in 8 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.
Largest Contentful Paint: 25.7 s
25.7 sYour largest element takes 25.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 26.1 s
26.1 sThe page becomes fully interactive after 26.1 s. Good is under 3.8 s.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 245 ms
245 msReal visitors wait 245 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 188 ms to 245 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 416 ms
416 msScripts block taps and scrolling for 416 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 601 ms
601 msReal visitors wait 601 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 463 requests
7.6 MBYour homepage downloads 7.6 MB in 463 requests on a phone: images 3.3 MB (54), scripts 2.5 MB (135) and other files 1.1 MB (220). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.17 g of CO₂e: 260.0 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Elements must only use permitted ARIA attributes (11 elements)
Elements must only use permitted ARIA attributes: 11 elements on the page fail this check, rated serious by axe-core.
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.
Scrollable region must have keyboard access (3 elements)
Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 117 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
155 internal links, 11 external
The homepage links to 155 pages on bullybunches.ca and 11 external pages.
7 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Looking for the best chews for dogs and bully sticks in the industry? Browse our selection of treats and safe chews at …”.
Title: 35 characters
Your title is a healthy 35 characters: “Best Chews for Dogs – Bully Bunches”.
Canonical URL set
The canonical URL is https://bullybunches.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://bullybunches.ca/sitemap.xml.
AI search readiness
4 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 sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,638 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bullybunches.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://bullybunches.ca/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://bullybunches.ca/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://bullybunches.ca/policies/shipping-policy and https://bullybunches.ca/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://bullybunches.ca/pages/product-recommendations-quiz, https://bullybunches.ca/pages/about-us and https://bullybunches.ca/customer_authentication/redirect 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 58 found) and read each the way a search engine does.
3 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.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
26 of 28 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 8-field form
Your longest form asks for 8 fields (0 required). Every extra field lowers completion.
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,200 words of copy
The homepage carries about 1,200 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 now”.
9 calls to action
The homepage has 9 calls to action, for example “Subscribe & Save”, “TRY OUR QUICK QUIZ” and “Buy on Amazon”.
Social proof on the page
Social proof on the homepage: 23 testimonial or review blocks, a star rating, 1 trust badge and “Over 65,000 Reviews”.
Analytics in place
Analytics detected: Microsoft Clarity and Matomo.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 6 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.
35 cookies set on arrival
35Opening the homepage sets 35 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.
60 other companies contacted
Loading the homepage contacts 60 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 bullybunches.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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Tapcart Mobile App · Microsoft Clarity · Rebuy Personalization Engine · Powerful Form Builder · Loyalty Rewards And Referrals · Klaviyo Email Marketing Sms · Hreflang Manager · Attentive · Triplewhale · Orbe Geolocation · Inbox · loox.io · snapchat.com · rechargecdn.com · octaneai.com · goaffpro.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
- E-commerce
- Shopify
- Analytics
- Matomo | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Surrey
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on bullybunches.ca, including 25 speed issues, 1 SEO issue and 2 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.