Website review, no card needed
zuiki.it website review
Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 88 checks
This review found 39 issues worth fixing on zuiki.it, 16 of them high impact, across 88 checks. The most urgent: avoid multiple page redirects. 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
75C- #77,383 of 117,441 reviewed websitesbeats 30%
- #49,593 of 66,904 online storesbeats 22%
- #46,883 of 61,009 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 254 ms |
| May 16, 2026 | 219 ms |
| May 23, 2026 | 206 ms |
| May 30, 2026 | 207 ms |
| Jun 6, 2026 | 209 ms |
| Jun 13, 2026 | 211 ms |
| Jun 20, 2026 | 214 ms |
| Jun 27, 2026 | 218 ms |
| Jul 4, 2026 | 220 ms |
| Jul 11, 2026 | 221 ms |
| Jul 18, 2026 | 221 ms |
| Jul 25, 2026 | 220 ms |
| Aug 1, 2026 | 220 ms |
| Aug 8, 2026 | 220 ms |
| Aug 15, 2026 | 222 ms |
| Aug 22, 2026 | 226 ms |
| Aug 29, 2026 | 231 ms |
| Sep 5, 2026 | 232 ms |
| Sep 12, 2026 | 235 ms |
| Sep 19, 2026 | 235 ms |
| Sep 26, 2026 | 235 ms |
| Oct 3, 2026 | 232 ms |
| Oct 10, 2026 | 227 ms |
| Oct 17, 2026 | 222 ms |
| Oct 24, 2026 | 216 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
Avoid multiple page redirects
14.7 sThe page goes through 1 redirect before it starts loading, costing about 14.7 s. Link and advertise the final URL directly.
Reduce unused JavaScript
4.1 s · 568 KiBAbout 568 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
1.4 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
547 KiB7 images could be 547 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, iubenda and Klaviyo and others), adding 1.1 MB and 280 ms of main-thread time.
2,988 HTML elements
The page has 2,988 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 24 ms
24 msShopify costs a phone 24 ms of main-thread work and 765 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 237 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 15 KiB15 KiB could be saved by minifying CSS.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
14 KiB7 files are served with short cache lifetimes, so returning visitors download them again (14 KiB).
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
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: 21 ms
21 msYour server sent the HTML in 21 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: 21.4 s
21.4 sYour largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 25.2 s
25.2 sThe page becomes fully interactive after 25.2 s. Good is under 3.8 s.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Real-user INP: 235 ms
235 msReal visitors wait 235 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.15
0.15The layout shifts by 0.15 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 248 ms
248 msScripts block taps and scrolling for 248 ms in total while the page loads. Good is under 200 ms.
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
-7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 254 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (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: 330 ms
330 msReal visitors wait 330 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.6 MB in 473 requests
5.6 MBYour homepage downloads 5.6 MB in 473 requests on a phone: images 2.4 MB (189), scripts 1.7 MB (126) and other files 822 KiB (131). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 191.1 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
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
48 images without alt text
48 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (61 elements)
All page content should be contained by landmarks: 61 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 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 (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Zuiki - Abbigliamento Femminile Accessibile | Collezione 2026 – Zuiki Italia”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Zuiki - Abbigliamento Femminile Accessibile” and “”). One clear main headline is easier for people and search engines.
27 links crawlers can't follow
27 links have no real href, so search engines can't follow them.
Meta description is long (282 characters)
Your meta description is 282 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
300 internal links, 13 external
The homepage links to 300 pages on zuiki.it and 13 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.zuiki.it/.
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.zuiki.it/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 (1,101 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.zuiki.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://www.zuiki.it/collections/ai26-matching-set, https://www.zuiki.it/collections/ai26-giacche-e-giubbini, https://www.zuiki.it/collections/ai26-gilet-1, https://www.zuiki.it/collections/ai26-shorts, https://www.zuiki.it/collections/ai26-pantaloni and https://www.zuiki.it/collections/ai26-jeans and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 133 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 12 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'Object'”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
113 of 126 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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 512 words of copy
The homepage carries about 512 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “SHOP JEANS →”.
7 short forms
7 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 1 of them by other companies (measured from a US location before any click).
28 other companies contacted
Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) 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 zuiki.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 © 2023.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Naples
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 zuiki.it, including 18 speed issues, 5 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.