Website review, no card needed
busybeessmocks.com website review
Visit site (opens in a new tab)Reviewed 9 November 202627 issues · 76 checks
This review found 27 issues worth fixing on busybeessmocks.com, 8 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
83B- #28,143 of 123,862 reviewed websitesbeats 72%
- #18,424 of 69,698 online storesbeats 67%
- #17,844 of 63,406 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 794 ms |
| May 30, 2026 | 718 ms |
| Jun 6, 2026 | 675 ms |
| Jun 13, 2026 | 664 ms |
| Jun 20, 2026 | 669 ms |
| Jun 27, 2026 | 691 ms |
| Jul 4, 2026 | 682 ms |
| Jul 11, 2026 | 671 ms |
| Jul 18, 2026 | 678 ms |
| Jul 25, 2026 | 667 ms |
| Aug 1, 2026 | 683 ms |
| Aug 8, 2026 | 671 ms |
| Aug 15, 2026 | 668 ms |
| Aug 22, 2026 | 645 ms |
| Aug 29, 2026 | 637 ms |
| Sep 5, 2026 | 638 ms |
| Sep 12, 2026 | 648 ms |
| Sep 19, 2026 | 643 ms |
| Sep 26, 2026 | 655 ms |
| Oct 3, 2026 | 654 ms |
| Oct 10, 2026 | 621 ms |
| Oct 17, 2026 | 639 ms |
| Oct 24, 2026 | 595 ms |
| Oct 31, 2026 | 600 ms |
| Nov 7, 2026 | 612 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 64 ms |
| May 30, 2026 | 68 ms |
| Jun 6, 2026 | 62 ms |
| Jun 13, 2026 | 68 ms |
| Jun 20, 2026 | 70 ms |
| Jun 27, 2026 | 70 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 70 ms |
| Jul 18, 2026 | 70 ms |
| Jul 25, 2026 | 70 ms |
| Aug 1, 2026 | 70 ms |
| Aug 8, 2026 | 70 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 69 ms |
| Aug 29, 2026 | 70 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 71 ms |
| Sep 19, 2026 | 71 ms |
| Sep 26, 2026 | 71 ms |
| Oct 3, 2026 | 71 ms |
| Oct 10, 2026 | 71 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 79 ms |
| Oct 31, 2026 | 79 ms |
| Nov 7, 2026 | 79 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
0.5 s
1.0 s
1.5 s
2.0 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Use efficient cache lifetimes
3.6 s · 818 KiB14 files are served with short cache lifetimes, so returning visitors download them again (818 KiB).
Reduce unused JavaScript
2.6 s · 524 KiBAbout 524 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (route.com, Shopify and smile.io and others), adding 1.5 MB and 432 ms of main-thread time.
Improve image delivery
412 KiB14 images could be 412 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
400 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
route.com adds 272 ms
272 msroute.com costs a phone 272 ms of main-thread work and 717 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,705 HTML elements
The page has 1,705 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 63 ms
63 msShopify costs a phone 63 ms of main-thread work and 350 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 long task on the main thread
1 long task block the main thread while loading, the longest for 233 ms. During a long task the page ignores taps.
Duplicated JavaScript
104 KiB104 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
Minify CSS
13 KiB13 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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 773 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.5 s
13.5 sYour largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.7 s
13.7 sThe page becomes fully interactive after 13.7 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 64 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 92 ms
92 msScripts block the page for only 92 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 299 requests
3.4 MBYour homepage downloads 3.4 MB in 299 requests on a phone: scripts 1.3 MB (92), other files 1.0 MB (153) and images 741 KiB (19). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
7_70cf1e94-2d15-4324-bff2-71ea6624de2d.png 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).
About 1.0 g of CO₂ per visit
0.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 114.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
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.
2 checks passed
Every image has alt text
All 17 images in the HTML carry an alt attribute.
50 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: 50 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
92 internal links, 4 external
The homepage links to 92 pages on busybeessmocks.com and 4 external pages.
7 checks passed
Meta description: 101 characters
Your meta description is 101 characters: “From Casual to Classic and everything in between! We love to dress your little ones from head to toe!”.
One H1 headline
Your main headline reads: “Busy Bee Smocks!”.
Title: 36 characters
Your title is a healthy 36 characters: “Busy Bees Smocks! – Busy Bee Smocks!”.
Canonical URL set
The canonical URL is https://www.busybeessmocks.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.busybeessmocks.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,138 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.busybeessmocks.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 pages without a meta description
https://www.busybeessmocks.com/collections/halloween/BOO, https://www.busybeessmocks.com/collections/pre-sale-141/Pre-Order-141, https://www.busybeessmocks.com/collections/autumn/FALL, https://www.busybeessmocks.com/collections/shop-christmas, https://www.busybeessmocks.com/collections/sale/SALE and https://www.busybeessmocks.com/collections/exclusive-bbs-graphic-tees-by-jax-james/GRAPHIC-TEES and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 links to non-canonical URLs
Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://www.busybeessmocks.com/collections/summer-2/Preorder-152, whose canonical is https://www.busybeessmocks.com/collections/summer-2. 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 39 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.
Titles are unique
Every page we checked has its own title.
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 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
20 of 24 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 286 words of copy
The homepage carries about 286 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Pre Order 152: Summer 2” and “Shop Christmas.”.
21 calls to action
The homepage has 21 calls to action, for example “Pre Order 152: Summer 2, The Finale'.”, “Shop Ready to Ship” and “Shop Everything”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Amplitude, Google Analytics, Google Tag Manager 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
25 other companies contacted
Loading the homepage contacts 25 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 busybeessmocks.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Ez Terms And Conditions Checkbox · route.com · nfcube.com · merchantyard.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on busybeessmocks.com, including 14 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.