Website review, no card needed
erbolario.com website review
Visit site (opens in a new tab)Reviewed 1 November 202639 issues · 83 checks
This review found 39 issues worth fixing on erbolario.com, 17 of them high impact, across 83 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
67D- #108,482 of 120,920 reviewed websitesbeats 9%
- #64,728 of 68,447 online storesbeats 4%
- #59,530 of 62,371 Shopify storesbeats 4%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 330 ms |
| May 16, 2026 | 334 ms |
| May 23, 2026 | 337 ms |
| May 30, 2026 | 344 ms |
| Jun 6, 2026 | 351 ms |
| Jun 13, 2026 | 358 ms |
| Jun 20, 2026 | 364 ms |
| Jun 27, 2026 | 369 ms |
| Jul 4, 2026 | 373 ms |
| Jul 11, 2026 | 372 ms |
| Jul 18, 2026 | 368 ms |
| Jul 25, 2026 | 365 ms |
| Aug 1, 2026 | 357 ms |
| Aug 8, 2026 | 352 ms |
| Aug 15, 2026 | 351 ms |
| Aug 22, 2026 | 349 ms |
| Aug 29, 2026 | 349 ms |
| Sep 5, 2026 | 354 ms |
| Sep 12, 2026 | 359 ms |
| Sep 19, 2026 | 355 ms |
| Sep 26, 2026 | 353 ms |
| Oct 3, 2026 | 339 ms |
| Oct 10, 2026 | 320 ms |
| Oct 17, 2026 | 317 ms |
| Oct 24, 2026 | 320 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.3 s
2.5 s
3.8 s
5.0 s
6.3 s
7.5 s
8.8 s
10.1 s
Speed
Reduce unused JavaScript
3.0 s · 603 KiBAbout 603 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
1.9 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Main-thread work: 11.7 s
A phone's processor spends 11.7 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,174 HTML elements
The page has 6,174 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 (Google Tag Manager, Shopify and Accessibe Accessibility Overlay and others), adding 2.3 MB and 1.4 s of main-thread time.
Improve image delivery
850 ms · 415 KiB14 images could be 415 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.
Use efficient cache lifetimes
800 ms · 158 KiB19 files are served with short cache lifetimes, so returning visitors download them again (158 KiB).
Reduce unused CSS
600 ms · 157 KiBAbout 157 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.
Google Tag Manager adds 699 ms
699 msGoogle Tag Manager costs a phone 699 ms of main-thread work and 540 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 188 ms
188 msShopify costs a phone 188 ms of main-thread work and 1.2 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.
Minify JavaScript
150 ms · 17 KiB17 KiB could be saved by minifying JavaScript.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 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).
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: 25 ms
25 msYour server sent the HTML in 25 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 INP: 1.4 s
1.4 sReal visitors wait 1.4 s for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 24.0 s
24.0 sYour largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Il sito www.erbolario.com utilizza cookie tecnici per conse…”.
Time to Interactive: 24.7 s
24.7 sThe page becomes fully interactive after 24.7 s. Good is under 3.8 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 330 ms to 320 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 742 ms
742 msReal visitors wait 742 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.071
0.071The layout barely moves while loading (CLS 0.071, good is under 0.1).
Images and page weight
Page weight: 10.6 MB in 245 requests
10.6 MBYour homepage downloads 10.6 MB in 245 requests on a phone: media 5.4 MB (1), images 2.5 MB (88) and scripts 1.6 MB (75). Under 2 MB keeps phones on slow connections fast.
About 3.0 g of CO₂ per visit
3.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.01 g of CO₂e: 361.0 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
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (10 elements)
ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 181 images in the HTML carry an alt attribute.
42 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: 42 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
797 internal links, 4 external
The homepage links to 797 pages on erbolario.com and 4 external pages.
6 checks passed
One H1 headline
Your main headline reads: “L’Erbolario, dalla natura i cosmetici per la tua bellezza”.
Title: 49 characters
Your title is a healthy 49 characters: “L’Erbolario - Cosmetici per una bellezza naturale”.
Canonical URL set
The canonical URL is https://www.erbolario.com/.
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.erbolario.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,721 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.erbolario.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.erbolario.com/pages/punti-vendita has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.erbolario.com/collections/bundle, whose canonical is https://www.erbolario.com/collections/tutte-le-idee-regalo. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages without an H1
https://www.erbolario.com/collections/novita, https://www.erbolario.com/collections/edizioni-limitate, https://www.erbolario.com/collections/formati-da-viaggio, https://www.erbolario.com/collections/waterless, https://www.erbolario.com/collections/biologico and https://www.erbolario.com/collections/bundle 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 198 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=25016546&tm=gtm002&Ver=2&mid=c6b598a6-f6fd-4e58-ac4a-777efa4a17f2&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=L%E2%80%99Erbolario%20-%20Cosmetici%20per%20u.
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
101 of 113 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.
Thin social proof
Social proof on the homepage: 24 testimonial or review blocks. 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 1,051 words of copy
The homepage carries about 1,051 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
24 short forms
24 short forms (0 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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 Microsoft Ads (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 erbolario.com, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on erbolario.com, including 21 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.