Website review, no card needed
leone1857.com website review
Visit site (opens in a new tab)Reviewed 25 October 202628 issues · 77 checks
This review found 28 issues worth fixing on leone1857.com, 12 of them high impact, across 77 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
76C- #73,186 of 120,066 reviewed websitesbeats 34%
- #47,139 of 68,040 online storesbeats 26%
- #44,709 of 62,009 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.3 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 178 ms |
| May 9, 2026 | 181 ms |
| May 16, 2026 | 187 ms |
| May 23, 2026 | 189 ms |
| May 30, 2026 | 209 ms |
| Jun 6, 2026 | 221 ms |
| Jun 13, 2026 | 236 ms |
| Jun 20, 2026 | 243 ms |
| Jun 27, 2026 | 237 ms |
| Jul 4, 2026 | 236 ms |
| Jul 11, 2026 | 239 ms |
| Jul 18, 2026 | 236 ms |
| Jul 25, 2026 | 237 ms |
| Aug 1, 2026 | 237 ms |
| Aug 8, 2026 | 238 ms |
| Aug 15, 2026 | 245 ms |
| Aug 22, 2026 | 250 ms |
| Aug 29, 2026 | 248 ms |
| Sep 5, 2026 | 242 ms |
| Sep 12, 2026 | 218 ms |
| Sep 19, 2026 | 109 ms |
| Sep 26, 2026 | 101 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 101 ms |
| Oct 17, 2026 | 103 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
Use efficient cache lifetimes
4.7 s · 6.9 MB33 files are served with short cache lifetimes, so returning visitors download them again (6.9 MB).
Render-blocking requests
3.0 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Improve image delivery
500 ms · 1.1 MB8 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 88). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
420 ms · 127 KiBAbout 127 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 420 ms faster on a phone.
iubenda adds 266 ms
266 msiubenda costs a phone 266 ms of main-thread work and 122 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.
2 third-party services on the page
2 third-party services load with your homepage (iubenda and Cloudflare), adding 132 KiB and 276 ms of main-thread time.
Reduce unused CSS
120 ms · 73 KiBAbout 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 120 ms faster on a phone.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 143 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 88 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 397 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.1 s
15.1 sYour largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “L'ARTE DEL GUSTO DAL 1857”.
Time to Interactive: 15.5 s
15.5 sThe page becomes fully interactive after 15.5 s. Good is under 3.8 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 122 ms
122 msReal visitors wait 122 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 662 ms
662 msReal visitors wait 662 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 43% faster for real visitors
-43%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 178 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 162 ms
162 msScripts block the page for only 162 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.5 MB in 40 requests
10.5 MBYour homepage downloads 10.5 MB in 40 requests on a phone: media 6.6 MB (1), images 3.0 MB (15) and fonts 544 KiB (12). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (569 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.
2 images far larger than shown
20 KiB2 images are downloaded at several times the size a phone draws them, for example galleria cioccolato.62c7a2206d219882619d50d40b064c75.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 20 KiB.
1 image below the first screen load straight away
1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.0 g of CO₂ per visit
2.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.96 g of CO₂e: 355.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (17 characters)
Your title is only 17 characters: “Leone - Corporate”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
31 internal links, 14 external
The homepage links to 31 pages on leone1857.com and 14 external pages.
3 checks passed
One H1 headline
Your main headline reads: “L'Arte del Gusto dal 1857”.
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://leone1857.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://leone1857.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (269 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
https://leone1857.com/corporate, https://leone1857.com/corporate.html, https://leone1857.com/en/corporate.html and https://leone1857.com/corporate/info.html all use the title “Leone - Corporate”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://leone1857.com/corporate.html, https://leone1857.com/en/corporate.html, https://leone1857.com/corporate/brand.html, https://leone1857.com/corporate/brand/la-fabbrica-della-felicita.html, https://leone1857.com/corporate/brand/la-fabbrica-della-felicita-museo.html and https://leone1857.com/corporate/storia.html and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://leone1857.com/youtube.com/@leone1857official has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
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”.
2 checks passed
Tap targets are thumb-sized
14 of 16 tappable elements near the top are at least 24 px.
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.
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 283 words of copy
The homepage carries about 283 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: iubenda
A consent management tool (iubenda) loads with the page.
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 leone1857.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify Hosted
Company
- Employees
- 78
- Headquarters
- Collegno
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on leone1857.com, including 11 speed issues, 5 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.