zona.com website review

About 660 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

About 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

22 files are served with short cache lifetimes, so returning visitors download them again (202 KiB).

Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (econcierge.solutions, Klaviyo and Cloudflare CDN and others), adding 1.5 MB and 779 ms of main-thread time.

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

A phone's processor spends 4.0 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

econcierge.solutions costs a phone 207 ms of main-thread work and 712 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.

Klaviyo costs a phone 192 ms of main-thread work and 319 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.

Polyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

11 long tasks block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.

1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

14 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 31.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Zona Plus Series 3 handheld device”.

The page becomes fully interactive after 32.0 s. Good is under 3.8 s.

Visually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.4 s on a phone. Good is under 1.8 s.

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 137 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 416 ms in total while the page loads. Good is under 200 ms.

33 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 6.8 MB in 286 requests on a phone: other files 4.0 MB (110), scripts 1.7 MB (113) and fonts 505 KiB (20). Under 2 MB keeps phones on slow connections fast.

seanzona.webp weighs 888 KiB. On a phone connection a single image that size takes seconds.

1 image (888 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.93 g of CO₂e: 231.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 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: 7 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

6 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h3, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 42 pages on zona.com and 16 external pages.

https://www.zona.com/products/zona-plus-series-3 and https://www.zona.com/collections/zona-store/products/zona-plus-series-3 all use the title “Zona Plus Series 3 Isometric Handgrip Device – Zona.com”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.zona.com/blogs/blog and https://www.zona.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.zona.com/products/zona-plus-series-3 and https://www.zona.com/collections/zona-store/products/zona-plus-series-3 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.zona.com/collections/zona-store/products/zona-plus-series-3, whose canonical is https://www.zona.com/products/zona-plus-series-3. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.zona.com/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26011665&Ver=2&mid=b2bd4366-9384-4d1b-a904-9dd867828e98&bo=1&sid=b40ab4c0db5511f19fdeeb0b8fa1ee42&vid=b40ab7c0db5511f181ab135a21b5f6b7&vids=1&msclkid=N&pi=918639831&lg.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Quiq is not defined”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 736 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 2 mores (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.

Opening the homepage sets 26 cookies, 4 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.