Website review, no card needed
shopbabybugboutique.com website review
Visit site (opens in a new tab)Reviewed 19 November 202634 issues · 68 checks
This review found 34 issues worth fixing on shopbabybugboutique.com, 11 of them high impact, across 68 checks. The most urgent: page weight: 17.4 MB in 134 requests. 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
76C- #75,193 of 123,845 reviewed websitesbeats 35%
- #48,193 of 69,695 online storesbeats 26%
- #45,655 of 63,403 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.3 s
3.4 s
4.5 s
5.6 s
6.8 s
7.9 s
9.0 s
Speed
Render-blocking requests
1.6 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Improve image delivery
300 ms · 15.4 MB23 images could be 15.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
800 ms · 12.4 MB60 files are served with short cache lifetimes, so returning visitors download them again (12.4 MB).
Mobile performance score: 81
81/100Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.
Document request latency
800 msThe HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
796 msReduce initial server response time. Google estimates savings of 796 ms on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, Cloudflare and Google Fonts and others), adding 1.2 MB and 149 ms of main-thread time.
Shopify adds 139 ms
139 msShopify costs a phone 139 ms of main-thread work and 1.2 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.
Server response: 896 ms
896 msYour server takes 896 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Reduce unused JavaScript
189 KiBAbout 189 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 223 ms of it running JavaScript. That is comfortably low.
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.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user INP: 335 ms
335 msReal visitors wait 335 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (1.8 s).
Time to Interactive: 6.0 s
6.0 sThe page becomes fully interactive after 6.0 s. Good is under 3.8 s.
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.
4 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 11 ms
11 msScripts block the page for only 11 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 17.4 MB in 134 requests
17.4 MBYour homepage downloads 17.4 MB in 134 requests on a phone: images 16.0 MB (23), other files 768 KiB (38) and scripts 503 KiB (36). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 11.7 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
11.3 MB9 images are downloaded at several times the size a phone draws them, for example DSC_0745.jpg at 3,841 px wide, shown at 173 px. Resized copies would save about 11.3 MB.
11 images in older formats
11 images (12.2 MB) 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.
An image on the first screen is lazy-loaded
DSC_0601.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).
About 4.9 g of CO₂ per visit
4.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.93 g of CO₂e: 591.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
25 text elements with low contrast
25 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.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 29 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
Meta description is long (298 characters)
Your meta description is 298 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
71 internal links, 5 external
The homepage links to 71 pages on shopbabybugboutique.com and 5 external pages.
6 checks passed
Title: 49 characters
Your title is a healthy 49 characters: “Baby Bug Boutique | Baby Clothing and Accessories”.
Canonical URL set
The canonical URL is https://shopbabybugboutique.com/.
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://shopbabybugboutique.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://shopbabybugboutique.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
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 (443 words), so crawlers that don't run JavaScript still read it.
Other pages
15 linked pages are broken
Your homepage links to https://shopbabybugboutique.com/collections/baby-bugs/Girls, https://shopbabybugboutique.com/collections/baby-bugs/Boys, https://shopbabybugboutique.com/collections/big-bugs/Girls, https://shopbabybugboutique.com/collections/big-bugs/Boys, https://shopbabybugboutique.com/collections/seasonal/Girls and https://shopbabybugboutique.com/collections/seasonal/Boys and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
Best practices
8 small tap targets
8 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 207 words
The homepage has only about 207 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Contact information”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 shopbabybugboutique.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Adperfect Marketing Platform · Ecomsend Popups · Inbox
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
- The footer still says © 2024.
Stack
- Framework
- React
- E-commerce
- Shopify
- Hosting
- Cloudflare
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 shopbabybugboutique.com, including 17 speed issues, 2 SEO issues and 4 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.