Website review, no card needed
zimeo.it website review
Visit site (opens in a new tab)Reviewed 11 November 202620 issues · 75 checks
This review found 20 issues worth fixing on zimeo.it, 4 of them high impact, across 75 checks. The most urgent: render-blocking 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
89B- #3,216 of 100,692 reviewed websitesbeats 95%
- #1,636 of 55,522 online storesbeats 95%
- #1,587 of 50,436 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 217 ms |
| May 30, 2026 | 218 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 205 ms |
| Jun 27, 2026 | 199 ms |
| Jul 4, 2026 | 214 ms |
| Jul 11, 2026 | 208 ms |
| Jul 18, 2026 | 214 ms |
| Jul 25, 2026 | 217 ms |
| Aug 1, 2026 | 224 ms |
| Aug 8, 2026 | 241 ms |
| Aug 15, 2026 | 241 ms |
| Aug 22, 2026 | 247 ms |
| Aug 29, 2026 | 247 ms |
| Sep 5, 2026 | 240 ms |
| Sep 12, 2026 | 248 ms |
| Sep 19, 2026 | 252 ms |
| Sep 26, 2026 | 261 ms |
| Oct 3, 2026 | 263 ms |
| Oct 10, 2026 | 271 ms |
| Oct 17, 2026 | 276 ms |
| Oct 24, 2026 | 277 ms |
| Oct 31, 2026 | 272 ms |
| Nov 7, 2026 | 271 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
Render-blocking requests
1.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Use efficient cache lifetimes
300 ms · 231 KiB8 files are served with short cache lifetimes, so returning visitors download them again (231 KiB).
Improve image delivery
267 KiB10 images could be 267 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
6 third-party services on the page
6 third-party services load with your homepage (Facebook, Hotjar and Shopify and others), adding 532 KiB and 473 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 205 ms. During a long task the page ignores taps.
Reduce unused JavaScript
125 KiBAbout 125 KiB of JavaScript is downloaded but never used on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93. That is in Google's “good” band (90 and up).
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 909 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 217 ms to 271 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 7.0 s
7.0 sThe page becomes fully interactive after 7.0 s. Good is under 3.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 93 ms
93 msReal visitors wait 93 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 475 ms
475 msReal visitors wait 475 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 191 ms
191 msScripts block the page for only 191 ms while loading. Good is under 200 ms.
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Questi prodotti sono attualmente particolarmente apprezzati”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 162 requests
2.1 MBYour homepage downloads 2.1 MB in 162 requests on a phone: other files 902 KiB (101), scripts 533 KiB (38) and images 477 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 70.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
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (273 characters)
Your meta description is 273 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
57 internal links, 3 external
The homepage links to 57 pages on zimeo.it and 3 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Zimeo IT”.
Title: 53 characters
Your title is a healthy 53 characters: “Zimeo IT | Crea regali unici per la Festa della Mamma”.
Canonical URL set
The canonical URL is https://zimeo.it/.
Structured data in place
Structured data found: BreadcrumbList, 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://zimeo.it/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (338 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://zimeo.it/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://zimeo.it/collections/all-canvases, https://zimeo.it/collections/tutti-i-poster, https://zimeo.it/collections/tutte-le-coperte, https://zimeo.it/collections/regali-di-san-valentino, https://zimeo.it/collections/tutte-le-felpe and https://zimeo.it/pages/aiuto-e-contatti and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://zimeo.it/products/poster-personalizzato-ti-amo-con-foto and https://zimeo.it/products/poster-personalizzato-lovestory use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://zimeo.it/pages/aiuto-e-contatti 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
6 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.
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 15 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: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
24 of 28 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: 12 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 295 words of copy
The homepage carries about 295 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Meta Pixel and Hotjar.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, Meta Pixel and TikTok Pixel (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (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.
17 other companies contacted
Loading the homepage contacts 17 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 zimeo.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Teeinblue Product Personalizer · Delm · Judge Me Reviews
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
- Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on zimeo.it, including 7 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.