zositech.es website review

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

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

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

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

8 third-party services load with your homepage (Shopify, avada.io and Clarity and others), adding 5.2 MB and 455 ms of main-thread time.

Shopify costs a phone 211 ms of main-thread work and 4.8 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 images could be 352 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

The page has 1,936 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 25 KiB of CSS is downloaded but never applied on this page.

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

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 7.7 MB in 332 requests on a phone: media 3.6 MB (6), images 1.9 MB (97) and scripts 1.2 MB (71). Under 2 MB keeps phones on slow connections fast.

18 images further down the page (538 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 elements hidden from screen readers can still receive keyboard focus.

1 tap target is too small or too close together to hit reliably with a finger.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

Your title is 68 characters, so Google will cut it off around 60: “4K UHD Security Cameras, CCTV & Smart Surveillance Systems - ZOSI EU”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“ZOSI EU Store” and “ZOSI Smart App”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 75 pages on zositech.es and 24 external pages.

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.

There is no https://zositech.es/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.

https://zositech.es/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 36 found) and read each the way a search engine does.

13 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Requests the notification permission on page load.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 531 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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