Website review, no card needed
verival.it website review
Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 81 checks
This review found 34 issues worth fixing on verival.it, 12 of them high impact, across 81 checks. The most urgent: page weight: 20.1 MB in 383 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
76C- #71,214 of 116,220 reviewed websitesbeats 34%
- #46,376 of 66,750 online storesbeats 26%
- #44,025 of 60,924 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 253 ms |
| May 23, 2026 | 274 ms |
| May 30, 2026 | 275 ms |
| Jun 6, 2026 | 284 ms |
| Jun 13, 2026 | 309 ms |
| Jun 20, 2026 | 319 ms |
| Jun 27, 2026 | 327 ms |
| Jul 4, 2026 | 320 ms |
| Jul 11, 2026 | 313 ms |
| Jul 18, 2026 | 301 ms |
| Jul 25, 2026 | 307 ms |
| Aug 1, 2026 | 328 ms |
| Aug 8, 2026 | 317 ms |
| Aug 15, 2026 | 315 ms |
| Aug 22, 2026 | 294 ms |
| Aug 29, 2026 | 265 ms |
| Sep 5, 2026 | 267 ms |
| Sep 12, 2026 | 259 ms |
| Sep 19, 2026 | 271 ms |
| Sep 26, 2026 | 270 ms |
| Oct 3, 2026 | 269 ms |
| Oct 10, 2026 | 270 ms |
| Oct 17, 2026 | 257 ms |
| Oct 24, 2026 | 262 ms |
| Oct 31, 2026 | 261 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
6,472 HTML elements
The page has 6,472 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
930 ms · 867 KiBAbout 867 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 930 ms faster on a phone.
Use efficient cache lifetimes
900 ms · 169 KiB11 files are served with short cache lifetimes, so returning visitors download them again (169 KiB).
Improve image delivery
1,003 KiB29 images could be 1,003 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, minmaxify.com and Google Tag Manager and others), adding 1.9 MB and 603 ms of main-thread time.
Shopify adds 258 ms
258 msShopify costs a phone 258 ms of main-thread work and 1.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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Minify JavaScript
119 KiB119 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
14 KiB14 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 103 ms
103 msYour server sent the HTML in 103 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.
Largest Contentful Paint: 15.5 s
15.5 sYour largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “In salute durante la stagione fredda: la tua mattinata perf…”.
Time to Interactive: 27.0 s
27.0 sThe page becomes fully interactive after 27.0 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Real-user INP: 259 ms
259 msReal visitors wait 259 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 287 ms
287 msScripts block taps and scrolling for 287 ms in total while the page loads. Good is under 200 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 253 ms to 261 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (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: 660 ms
660 msReal visitors wait 660 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 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: 20.1 MB in 383 requests
20.1 MBYour homepage downloads 20.1 MB in 383 requests on a phone: media 11.6 MB (2), images 5.2 MB (77) and scripts 1.8 MB (112). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
social-media-wiese-verival.jpg weighs 528 KiB. On a phone connection a single image that size takes seconds.
6 images far larger than shown
750 KiB6 images are downloaded at several times the size a phone draws them, for example social-media-wiese-verival.jpg at 1,200 px wide, shown at 300 px. Resized copies would save about 750 KiB.
6 images below the first screen load straight away
6 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (101 KiB) is 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 5.7 g of CO₂ per visit
5.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.69 g of CO₂e: 682.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
166 text elements with low contrast
166 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (6 elements)
ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 165 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (91 characters)
Your title is 91 characters, so Google will cut it off around 60: “Negozio online Verival - Acquista subito online i prodotti biologici per la prima colazio…”.
Meta description is long (190 characters)
Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
422 internal links, 19 external
The homepage links to 422 pages on verival.it and 19 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.verival.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.verival.it/sitemap.xml.
AI search readiness
4 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 (4,058 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.verival.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.verival.it/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.verival.it/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.verival.it/collections/all, https://www.verival.it/customer_authentication/redirect and https://www.verival.it/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://www.verival.it/customer_authentication/redirect, https://www.verival.it/collections/geschenksets-gutscheine, https://www.verival.it/collections/protein-fruehstueck, https://www.verival.it/collections/ballaststoffreiches-fruhstuck, https://www.verival.it/collections/fruehstueck-ohne-zuckerzusatz and https://www.verival.it/collections/low-carb-fruehstueck and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.verival.it/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 135 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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Maximum call stack size exceeded”.
2 checks passed
Tap targets are thumb-sized
33 of 35 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 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 2,596 words of copy
The homepage carries about 2,596 words of visible text.
4 checks passed
11 calls to action
The homepage has 11 calls to action, for example “SHOP” and “Verival Shop Langkampfen”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and PostHog.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
3 cookies set on arrival
3Opening the homepage sets 3 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 verival.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Flyweight Ai Chatbot · Sticky Add To Cart Bar · Judge Me Reviews · Minmaxify Order Limits · Gdpr Cookie Consent · Stape Remix · Event Promotion Bar · Forms · Mailchimp · Deco Labels Badges · Free Gift · chimpstatic.com · hextom.com · sealsubscriptions.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | PostHog
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on verival.it, including 16 speed issues, 3 SEO issues and 2 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.