Website review, no card needed
carozzi.com website review
Visit site (opens in a new tab)Reviewed 18 October 202635 issues · 75 checks
This review found 35 issues worth fixing on carozzi.com, 16 of them high impact, across 75 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
75C- #77,275 of 117,262 reviewed websitesbeats 30%
- #49,582 of 66,884 online storesbeats 22%
- #1,298 of 2,691 WooCommerce storesbeats 45%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 5.7 s |
| May 2, 2026 | 5.9 s |
| May 9, 2026 | 6.0 s |
| May 16, 2026 | 5.8 s |
| May 23, 2026 | 5.4 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 5.2 s |
| Aug 15, 2026 | 5.6 s |
| Aug 22, 2026 | 5.8 s |
| Aug 29, 2026 | 5.8 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 5.9 s |
| Sep 19, 2026 | 5.9 s |
| Sep 26, 2026 | 5.9 s |
| Oct 3, 2026 | 6.1 s |
| Oct 10, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 107 ms |
| May 2, 2026 | 105 ms |
| May 9, 2026 | 108 ms |
| May 16, 2026 | 110 ms |
| May 23, 2026 | 106 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 99 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 99 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 111 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 118 ms |
| Oct 10, 2026 | 128 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
1.1 s
2.3 s
3.4 s
4.6 s
5.7 s
6.9 s
8.0 s
9.1 s
Speed
Use efficient cache lifetimes
5.0 s · 2.4 MB77 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
Improve image delivery
1.4 s · 927 KiB7 images could be 927 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.6 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Reduce unused JavaScript
900 ms · 156 KiBAbout 156 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58 (desktop: 82). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
3 third-party services on the page
3 third-party services load with your homepage (iubenda, Google Tag Manager and Google Fonts), adding 499 KiB and 175 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 68 ms. During a long task the page ignores taps.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 346 ms of it running JavaScript. That is comfortably low.
Server response: 134 ms
134 msYour server sent the HTML in 134 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.8 s
6.8 sReal visitors wait 6.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.4 s
6.4 sReal visitors see the first content after 6.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 6.2 s
6.2 sReal visitors wait 6.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Formaggi CarozziMODERNI INTERPRETI D…”.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 11.5 s
11.5 sThe page becomes fully interactive after 11.5 s. Good is under 3.8 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 107 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 5.7 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.054
0.054The layout barely moves while loading (CLS 0.054, good is under 0.1).
Total Blocking Time: 18 ms
18 msScripts block the page for only 18 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.9 MB in 94 requests
2.9 MBYour homepage downloads 2.9 MB in 94 requests on a phone: images 2.0 MB (20), scripts 416 KiB (32) and fonts 283 KiB (10). Under 2 MB keeps phones on slow connections fast.
11 images in older formats
11 images (716 KiB) 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.
About 0.8 g of CO₂ per visit
0.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
5 tap targets too small
5 tap targets are 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.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“LA BOTTEGA ONLINE DI CAROZZI FORMAGGI”, “Formaggi di Capra” and “Valsassina”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
26 internal links, 13 external
The homepage links to 26 pages on carozzi.com and 13 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Da oltre 50 anni, Carozzi produce formaggi DOP lombardi portando avanti le tradizioni della Valsassina, con uno sguardo…”.
Title: 61 characters
Your title is a healthy 61 characters: “Formaggi Carozzi - Moderni interpreti di un'antica tradizione”.
Canonical URL set
The canonical URL is https://www.carozzi.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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.carozzi.com/sitemap_index.xml.
AI search readiness
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 (347 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.carozzi.com/feed has no <title>, so Google invents the link text in results.
3 pages without a meta description
https://www.carozzi.com/feed, https://www.carozzi.com/servizio-clienti and https://www.carozzi.com/invest-2021 have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.carozzi.com/taleggio, whose canonical is https://www.carozzi.com/prodotti/taleggio. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.carozzi.com/news, https://www.carozzi.com/feed and https://www.carozzi.com/invest-2021 have no <h1> headline, so visitors and search engines get no clear main topic.
10 pages slow to respond
https://www.carozzi.com/chi-siamo, https://www.carozzi.com/news, https://www.carozzi.com/contatti, https://www.carozzi.com/taleggio, https://www.carozzi.com/prodotti/gorgonzola and https://www.carozzi.com/formaggi-di-capra and 4 others took over 3 s to send their HTML from our server.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
12 pages of 13 loaded without an error (the rest turned automated requests away).
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.
Best practices
11 small tap targets
11 of 24 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 “Bootstrap's JavaScript requires jQuery version 1.9.1 or higher, but lower than version 3”.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 274 words of copy
The homepage carries about 274 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “SHOP ON-LINE” and “VAI ALLO SHOP ONLINE”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
5 other companies contacted
Loading the homepage contacts 5 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 carozzi.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on carozzi.com, including 16 speed issues, 2 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.