cabledered.es website review

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

13 images could be 460 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 1.4 MB and 792 ms of main-thread time.

About 738 KiB of JavaScript is downloaded but never used on this page.

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

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

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

Google Tag Manager costs a phone 299 ms of main-thread work and 526 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.

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

Shopify costs a phone 79 ms of main-thread work and 413 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.

15 KiB could be saved by minifying CSS.

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

6 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.

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

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

Visually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 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 4.3 MB in 342 requests on a phone: scripts 1.8 MB (90), other files 1.1 MB (186) and images 666 KiB (39). Under 2 MB keeps phones on slow connections fast.

journi-hero-photo.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images are downloaded at several times the size a phone draws them, for example 46da7ecd-6be6-4f79-a896-aeed165b7b31.png at 1,422 px wide, shown at 350 px. Resized copies would save about 295 KiB.

1 image (375 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.22 g of CO₂e: 145.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

11 buttons have no accessible name, so screen readers announce just “button”.

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 107 characters, so Google will cut it off around 60: “¿Comprar un cable de red? (¡CONSEJO!) - Cables de red al mejor precio en los Países Bajos…”.

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//cabledered.es/cdn/shop/files/bbpt3-2dtks.svg?v=171343…”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 368 pages on cabledered.es and 7 external pages.

https://cabledered.es/collections/cables-de-red, https://cabledered.es/collections/ultra-delgado-cables-de-red, https://cabledered.es/collections/cat8-rollo and https://cabledered.es/collections/buitennetwerkkabels have no meta description, so Google writes the search snippet from whatever text it finds.

https://cabledered.es/pages/b2b-aanvraag-empresarial-account, https://cabledered.es/collections/cables-de-red, https://cabledered.es/collections/cat5e-cables, https://cabledered.es/collections/cat6-cables-1, https://cabledered.es/collections/cat6a-cables-1 and https://cabledered.es/collections/cat7-cables-1 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=5947616&tm=gtm002&Ver=2&mid=b0bca0e1-ea7a-4510-bc70-3fd81f874b3e&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=%C2%BFComprar%20un%20cable%20de%20red%3F%20(%C.

6 errors were logged to the browser console while the page loaded, for example “Unexpected token '--'”.

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

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.

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

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.

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 650 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 1 more (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 21 cookies (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 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.