siberzone.es website review

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

62 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).

Your mobile performance score is 57 (desktop: 77). Pages that score under 90 lose visitors before the first paint.

6 images could be 798 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 third-party services load with your homepage (Hotjar, Google Tag Manager and Hubspot and others), adding 524 KiB and 592 ms of main-thread time.

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

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

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

About 146 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

About 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 210 ms faster on a phone.

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

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.

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

The layout shifts by 0.869 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (1.6 s).

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 75 requests on a phone: images 1.8 MB (46), media 782 KiB (1) and scripts 591 KiB (16). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 66a8a3da97fc9siber_one.png at 2,703 px wide, shown at 228 px. Resized copies would save about 451 KiB.

1 image further down the page (482 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

All page content should be contained by landmarks: 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 tap target is too small or too close together to hit reliably with a finger.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 143 pages on siberzone.es and 11 external pages.

https://www.siberzone.es/empresa and https://www.siberzone.es/empresa/sobre-nosotros all use the title “Sobre nosotros · Historia y misión | Siberzone”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.siberzone.es/empresa/sellos and https://www.siberzone.es/trabaja-con-nosotros have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.siberzone.es/empresa and https://www.siberzone.es/empresa/sobre-nosotros 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.siberzone.es/empresa, whose canonical is https://www.siberzone.es/empresa/sobre-nosotros. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.siberzone.es/empresa/normativa, https://www.siberzone.es/empresa/sostenibilidad, https://www.siberzone.es/trabaja-con-nosotros, https://www.siberzone.es/servicios and https://www.siberzone.es/servicios/herramientas-digitales have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.siberzone.es/servicios, https://www.siberzone.es/servicios/apoyo-a-la-prescripcion and https://www.siberzone.es/servicios/instaladores-y-distribuidores took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Content security policy”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 201 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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