Website review, no card needed
naturasi.it website review
Visit site (opens in a new tab)Reviewed 29 October 202649 issues · 73 checks
This review found 49 issues worth fixing on naturasi.it, 23 of them high impact, across 73 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
50FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 293 ms |
| May 16, 2026 | 286 ms |
| May 23, 2026 | 288 ms |
| May 30, 2026 | 289 ms |
| Jun 6, 2026 | 292 ms |
| Jun 13, 2026 | 308 ms |
| Jun 20, 2026 | 317 ms |
| Jun 27, 2026 | 325 ms |
| Jul 4, 2026 | 330 ms |
| Jul 11, 2026 | 326 ms |
| Jul 18, 2026 | 323 ms |
| Jul 25, 2026 | 322 ms |
| Aug 1, 2026 | 322 ms |
| Aug 8, 2026 | 318 ms |
| Aug 15, 2026 | 310 ms |
| Aug 22, 2026 | 295 ms |
| Aug 29, 2026 | 283 ms |
| Sep 5, 2026 | 277 ms |
| Sep 12, 2026 | 279 ms |
| Sep 19, 2026 | 278 ms |
| Sep 26, 2026 | 275 ms |
| Oct 3, 2026 | 272 ms |
| Oct 10, 2026 | 265 ms |
| Oct 17, 2026 | 263 ms |
| Oct 24, 2026 | 262 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.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.3 s
9.5 s
Speed
Reduce unused JavaScript
4.3 s · 820 KiBAbout 820 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Font display
1.2 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.2 s).
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 15
15/100Your mobile performance score is 15. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
770 ms · 169 KiBAbout 169 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 770 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Cookiebot and feedaty.com and others), adding 3.9 MB and 355 ms of main-thread time.
Improve image delivery
390 KiB5 images could be 390 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 353 ms. During a long task the page ignores taps.
Vimeo adds 0 ms
0 msVimeo costs a phone 0 ms of main-thread work and 3.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.
Google Tag Manager adds 296 ms
296 msGoogle Tag Manager costs a phone 296 ms of main-thread work and 324 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,342 HTML elements
The page has 2,342 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
41 KiB12 files are served with short cache lifetimes, so returning visitors download them again (41 KiB).
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: 1 ms
1 msYour server sent the HTML in 1 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: 5.3 s
5.3 sReal visitors wait 5.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.02
1.02For real visitors the layout shifts by 1.02 (75th percentile). Good is under 0.1.
First Contentful Paint: 8.6 s
8.6 sThe first text or image appears after 8.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 11.9 s
11.9 sYour largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Utilizziamo i cookie per personalizzare contenuti ed annunc…”. Most of its time is element render delay (8.7 s).
Speed Index: 16.0 s
16.0 sVisually, the page fills in at 16.0 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.934
0.934The layout shifts by 0.934 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Total Blocking Time: 640 ms
640 msScripts block taps and scrolling for 640 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 310 ms
310 msReal visitors wait 310 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
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
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 293 ms to 262 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user TTFB: 497 ms
497 msReal visitors wait 497 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.0 MB in 62 requests
6.0 MBYour homepage downloads 6.0 MB in 62 requests on a phone: media 3.3 MB (2), scripts 1.4 MB (13) and fonts 568 KiB (4). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
194 KiB2 images are downloaded at several times the size a phone draws them, for example caa2c50a-19d6-41eb-9ff3-4dc6b6c1f7ea.png at 3,589 px wide, shown at 143 px. Resized copies would save about 194 KiB.
5 images below the first screen load straight away
5 images further down the page (458 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (458 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 1.7 g of CO₂ per visit
1.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 204.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 5 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (8 characters)
Your title is only 8 characters: “NaturaSì”. 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.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
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.naturasi.it/category.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 1,302 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://www.naturasi.it/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.
1 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.
Best practices
16 small tap targets
16 of 69 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,302 words of copy
The homepage carries about 1,302 words of visible text.
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 (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 naturasi.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Hosting
- Asn Debis
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on naturasi.it, including 25 speed issues, 8 SEO issues and 5 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.