Website review, no card needed
carmenboutique.it website review
Visit site (opens in a new tab)Reviewed 9 November 202641 issues · 90 checks
This review found 41 issues worth fixing on carmenboutique.it, 21 of them high impact, across 90 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
65D- #117,032 of 126,333 reviewed websitesbeats 6%
- #67,918 of 70,435 online storesbeats 3%
- #62,064 of 63,941 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 7.0 s |
| May 30, 2026 | 6.8 s |
| Jun 6, 2026 | 6.8 s |
| Jun 13, 2026 | 6.8 s |
| Jun 20, 2026 | 6.7 s |
| Jun 27, 2026 | 6.7 s |
| Jul 4, 2026 | 6.5 s |
| Jul 11, 2026 | 6.2 s |
| Jul 18, 2026 | 6.1 s |
| Jul 25, 2026 | 6.2 s |
| Aug 1, 2026 | 6.3 s |
| Aug 8, 2026 | 6.6 s |
| Aug 15, 2026 | 6.8 s |
| Aug 22, 2026 | 6.8 s |
| Aug 29, 2026 | 6.8 s |
| Sep 5, 2026 | 6.9 s |
| Sep 12, 2026 | 7.0 s |
| Sep 19, 2026 | 7.0 s |
| Sep 26, 2026 | 7.2 s |
| Oct 3, 2026 | 7.1 s |
| Oct 10, 2026 | 6.8 s |
| Oct 17, 2026 | 6.7 s |
| Oct 24, 2026 | 6.7 s |
| Oct 31, 2026 | 6.8 s |
| Nov 7, 2026 | 6.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 213 ms |
| May 30, 2026 | 214 ms |
| Jun 6, 2026 | 221 ms |
| Jun 13, 2026 | 235 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 279 ms |
| Jul 4, 2026 | 297 ms |
| Jul 11, 2026 | 313 ms |
| Jul 18, 2026 | 306 ms |
| Jul 25, 2026 | 305 ms |
| Aug 1, 2026 | 303 ms |
| Aug 8, 2026 | 309 ms |
| Aug 15, 2026 | 317 ms |
| Aug 22, 2026 | 315 ms |
| Aug 29, 2026 | 310 ms |
| Sep 5, 2026 | 293 ms |
| Sep 12, 2026 | 282 ms |
| Sep 19, 2026 | 278 ms |
| Sep 26, 2026 | 283 ms |
| Oct 3, 2026 | 291 ms |
| Oct 10, 2026 | 287 ms |
| Oct 17, 2026 | 289 ms |
| Oct 24, 2026 | 293 ms |
| Oct 31, 2026 | 295 ms |
| Nov 7, 2026 | 307 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.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
Reduce unused JavaScript
7.0 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Use efficient cache lifetimes
2.5 s · 503 KiB22 files are served with short cache lifetimes, so returning visitors download them again (503 KiB).
hcaptcha.com adds 1.8 s
1.8 shcaptcha.com costs a phone 1.8 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 12.3 s
A phone's processor spends 12.3 s on main-thread work while loading, 5.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.2 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,564 HTML elements
The page has 8,564 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, Shopify and PayPal and others), adding 3.3 MB and 3.6 s of main-thread time.
Shopify adds 944 ms
944 msShopify costs a phone 944 ms of main-thread work and 1.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.
Improve image delivery
550 ms · 220 KiB8 images could be 220 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 522 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Duplicated JavaScript
150 ms · 28 KiB28 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
Minify CSS
9 KiB9 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: 22 ms
22 msYour server sent the HTML in 22 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 LCP: 6.6 s
6.6 sReal visitors wait 6.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.8 s
6.8 sReal visitors see the first content after 6.8 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 27.9 s
27.9 sYour largest element takes 27.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 33.1 s
33.1 sThe page becomes fully interactive after 33.1 s. Good is under 3.8 s.
Speed Index: 14.6 s
14.6 sVisually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.5 s
5.5 sThe first text or image appears after 5.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user INP: 225 ms
225 msReal visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 213 ms to 307 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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
-2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 7.0 s to 6.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 664 ms
664 msReal visitors wait 664 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 15.5 MB in 486 requests
15.5 MBYour homepage downloads 15.5 MB in 486 requests on a phone: media 9.2 MB (4), scripts 3.0 MB (151) and other files 1.5 MB (285). Under 2 MB keeps phones on slow connections fast.
About 4.4 g of CO₂ per visit
4.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.39 g of CO₂e: 527.1 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
Unlabelled dropdowns
1 dropdown has no label.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 7 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
51 H1 headlines
There are 51 <h1> headlines (“Carmenboutique.it”, “PT Denim” and “Lu Lu Girl”). One clear main headline is easier for people and search engines.
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
1,103 internal links, 12 external
The homepage links to 1,103 pages on carmenboutique.it and 12 external pages.
6 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “Carmen Boutique | Moda lusso donna, uomo e bambino”.
Canonical URL set
The canonical URL is https://www.carmenboutique.it/.
Structured data in place
Structured data found: BreadcrumbList, 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.carmenboutique.it/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (4,793 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.carmenboutique.it/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://www.carmenboutique.it/policies/refund-policy, https://www.carmenboutique.it/pages/klarna, https://www.carmenboutique.it/pages/donna, https://www.carmenboutique.it/pages/uomo, https://www.carmenboutique.it/pages/bambini and https://www.carmenboutique.it/pages/contatti and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://www.carmenboutique.it/pages/contatti, https://www.carmenboutique.it/pages/swym-wishlist, https://www.carmenboutique.it/collections/collezione-nuovi-arrivi-uomo, https://www.carmenboutique.it/collections/nuovi-arrivi-abbigliamento-uomo, https://www.carmenboutique.it/collections/nuovi-arrivi-calzature-uomo and https://www.carmenboutique.it/collections/nuovi-arrivi-accessori-uomo have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.carmenboutique.it/collections/collezione-nuovi-arrivi-uomo and https://www.carmenboutique.it/collections/nuovi-arrivi-abbigliamento-uomo took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 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.
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.
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
149 small tap targets
149 of 275 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'loadFeatures')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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,160 words of copy
The homepage carries about 1,160 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Informativa Privacy Servizi Shop Online”.
15 short forms
15 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 1 of them by other companies (measured from a US location before any click).
41 other companies contacted
Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) loads with the page.
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 carmenboutique.it, 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 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wrapped · Frequently Bought · Inbox · Xb Countdown Timer · Scalapay On Site Messaging · Whatsapp Chat Button · Pushowl · Event Promotion Bar · Scalapay Widget Installer Prod · Watchlist · Fatture Italia · Sidekick · Ecomsend · Swym Wishlist Plus · returngo.ai · trustpilot.com · hextom.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
- Analytics
- Google Analytics
- Hosting
- Shopify
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 carmenboutique.it, including 22 speed issues, 2 SEO issues 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.