Website review, no card needed
shoptheboutique.com website review
Visit site (opens in a new tab)Reviewed 9 November 202641 issues · 82 checks
This review found 41 issues worth fixing on shoptheboutique.com, 17 of them high impact, across 82 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
66D- #110,438 of 120,865 reviewed websitesbeats 7%
- #65,426 of 68,427 online storesbeats 4%
- #60,079 of 62,354 Shopify storesbeats 3%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 915 ms |
| May 30, 2026 | 911 ms |
| Jun 6, 2026 | 865 ms |
| Jun 13, 2026 | 846 ms |
| Jun 20, 2026 | 820 ms |
| Jun 27, 2026 | 837 ms |
| Jul 4, 2026 | 867 ms |
| Jul 11, 2026 | 896 ms |
| Jul 18, 2026 | 974 ms |
| Jul 25, 2026 | 997 ms |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 979 ms |
| Sep 5, 2026 | 959 ms |
| Sep 12, 2026 | 941 ms |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 131 ms |
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 132 ms |
| Jun 13, 2026 | 133 ms |
| Jun 20, 2026 | 134 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 143 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 144 ms |
| Oct 17, 2026 | 140 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 108 ms |
| Nov 7, 2026 | 104 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.8 s
1.5 s
2.3 s
3.0 s
3.8 s
4.5 s
5.3 s
6.0 s
Speed
Reduce unused JavaScript
1.4 s · 463 KiBAbout 463 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Improve image delivery
1.2 s · 316 KiB7 images could be 316 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.2 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,596 HTML elements
The page has 3,596 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
700 ms · 248 KiB15 files are served with short cache lifetimes, so returning visitors download them again (248 KiB).
Reduce unused CSS
300 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Attentive, shiptection.com and Klaviyo and others), adding 884 KiB and 328 ms of main-thread time.
Minify JavaScript
150 ms · 21 KiB21 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 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.
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: 7 ms
7 msYour server sent the HTML in 7 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.
Real-user CLS: 0.55
0.55For real visitors the layout shifts by 0.55 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 1.84
1.84The layout shifts by 1.84 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 12.7 s
12.7 sYour largest element takes 12.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: 13.2 s
13.2 sThe page becomes fully interactive after 13.2 s. Good is under 3.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
48 images without width and height
48 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
6 checks passed
Real-user INP: 152 ms
152 msReal visitors wait 152 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 570 ms
570 msReal visitors wait 570 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 131 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 74 ms
74 msScripts block the page for only 74 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.5 MB in 322 requests
3.5 MBYour homepage downloads 3.5 MB in 322 requests on a phone: scripts 1.3 MB (95), images 1.1 MB (43) and other files 922 KiB (158). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
189 KiB1 image is downloaded at several times the size a phone draws it, for example DESKTOP-HEADER-2024.png at 2,000 px wide, shown at 306 px. Resized copies would save about 189 KiB.
1 image below the first screen load straight away
1 image further down the page (111 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 119.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Hidden but focusable
10 elements hidden from screen readers can still receive keyboard focus.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
33 images without alt text
33 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
15 form fields without a label
15 form fields have no label, so screen readers announce an empty box and autofill guesses.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
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.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (12 elements).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
43 links crawlers can't follow
43 links have no real href, so search engines can't follow them.
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Online Trendy Boutique Clothing for Women - Free Shipping - Shop Now – The Boutique”.
150 internal links, 14 external
The homepage links to 150 pages on shoptheboutique.com and 14 external pages.
6 checks passed
Meta description: 111 characters
Your meta description is 111 characters: “The latest in women's fashion. With New Arrivals daily, there's no better place to shop women's clothes online!”.
Canonical URL set
The canonical URL is https://www.shoptheboutique.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://www.shoptheboutique.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
60%The HTML your server sends has 636 of the 1,063 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://www.shoptheboutique.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.shoptheboutique.com/collections/under-20, which answers with an error. Visitors hit a dead end and search engines drop it.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
Best practices
70 small tap targets
70 of 121 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'global_config')”.
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
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 1,063 words of copy
The homepage carries about 1,063 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: “SHOP” and “SHOP DRESSES”.
13 calls to action
The homepage has 13 calls to action, for example “Shop”, “Subscribe” and “Order Status”.
29 short forms
29 short forms (4 fields at most) are right on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before 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
22Opening 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.
33 other companies contacted
Loading the homepage contacts 33 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 shoptheboutique.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Okendo · Attentive · Klaviyo Email Marketing Sms · Countdown Timer · Pushowl · automizely.com · avada.io · one.store · yottaa.com · attn.tv · shiptection.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
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Company
- Headquarters
- Miami
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on shoptheboutique.com, including 17 speed issues, 3 SEO issues 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.