Website review, no card needed
carpisa.it website review
Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 83 checks
This review found 40 issues worth fixing on carpisa.it, 12 of them high impact, across 83 checks. The most urgent: render-blocking 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
79C- #53,888 of 119,805 reviewed websitesbeats 50%
- #35,616 of 67,930 online storesbeats 42%
- #34,158 of 61,917 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 248 ms |
| May 23, 2026 | 255 ms |
| May 30, 2026 | 277 ms |
| Jun 6, 2026 | 304 ms |
| Jun 13, 2026 | 337 ms |
| Jun 20, 2026 | 348 ms |
| Jun 27, 2026 | 328 ms |
| Jul 4, 2026 | 312 ms |
| Jul 11, 2026 | 300 ms |
| Jul 18, 2026 | 295 ms |
| Jul 25, 2026 | 296 ms |
| Aug 1, 2026 | 295 ms |
| Aug 8, 2026 | 294 ms |
| Aug 15, 2026 | 294 ms |
| Aug 22, 2026 | 295 ms |
| Aug 29, 2026 | 296 ms |
| Sep 5, 2026 | 294 ms |
| Sep 12, 2026 | 290 ms |
| Sep 19, 2026 | 279 ms |
| Sep 26, 2026 | 265 ms |
| Oct 3, 2026 | 255 ms |
| Oct 10, 2026 | 247 ms |
| Oct 17, 2026 | 246 ms |
| Oct 24, 2026 | 246 ms |
| Oct 31, 2026 | 249 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
Speed
Render-blocking requests
1.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (ZenDesk, avacy-cdn.com and Shopify and others), adding 1.4 MB and 686 ms of main-thread time.
Reduce unused JavaScript
150 ms · 510 KiBAbout 510 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
300 ms · 66 KiBAbout 66 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.
ZenDesk adds 271 ms
271 msZenDesk costs a phone 271 ms of main-thread work and 476 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
299 KiB8 images could be 299 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,751 HTML elements
The page has 2,751 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
avacy-cdn.com adds 179 ms
179 msavacy-cdn.com costs a phone 179 ms of main-thread work and 441 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 124 ms
124 msShopify costs a phone 124 ms of main-thread work and 366 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 135 ms. During a long task the page ignores taps.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
12 KiB6 files are served with short cache lifetimes, so returning visitors download them again (12 KiB).
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: 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.
Time to Interactive: 15.0 s
15.0 sThe page becomes fully interactive after 15.0 s. Good is under 3.8 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 357 ms
357 msReal visitors wait 357 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 309 ms
309 msScripts block taps and scrolling for 309 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 248 ms to 249 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.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: 738 ms
738 msReal visitors wait 738 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 247 requests
3.7 MBYour homepage downloads 3.7 MB in 247 requests on a phone: scripts 1.2 MB (78), other files 1.1 MB (136) and images 975 KiB (18). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 125.5 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
Required ARIA attributes must be provided (4 elements)
Required ARIA attributes must be provided: 4 elements on the page fail this check, rated critical 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.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
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.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
57 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 57 passed and 4 failed. 3 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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
177 internal links, 11 external
The homepage links to 177 pages on carpisa.it and 11 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Carpisa, marchio Italiano leader nel settore borse e accessori moda, valigeria e trolley da viaggio. Design italiano da…”.
Title: 50 characters
Your title is a healthy 50 characters: “Carpisa | Trolley, Borse e Portafogli donna e uomo”.
Canonical URL set
The canonical URL is https://www.carpisa.it/it-it.
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.carpisa.it/sitemap.xml.
AI search readiness
Parts of the site are closed to 4 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
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,238 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.carpisa.it/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.carpisa.it/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.carpisa.it/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://www.carpisa.it/it-it/pages/newsletter, https://www.carpisa.it/it-it/pages/carpisa-lovers, https://www.carpisa.it/customer_authentication/redirect and https://www.carpisa.it/it-it/pages/promozioni have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.carpisa.it/it-it/pages/newsletter, https://www.carpisa.it/customer_authentication/redirect and https://www.carpisa.it/it-it/pages/promozioni 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 66 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
6 small tap targets
6 of 29 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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 10 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 312 words of copy
The homepage carries about 312 words of visible text.
2 checks passed
11 short forms
11 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
24 other companies contacted
Loading the homepage contacts 24 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 carpisa.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Founded
- 2001
- Headquarters
- Naples
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on carpisa.it, including 18 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.