sp-connect.es website review

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

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

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

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

8 third-party services load with your homepage (Cookiebot, Google Tag Manager and cloudfront.net and others), adding 937 KiB and 654 ms of main-thread time.

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

Cookiebot costs a phone 265 ms of main-thread work and 171 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.

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

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

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

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

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

8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

66 KiB could be saved by minifying CSS.

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

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 10.3 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 14.4 s. Good is under 3.8 s.

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

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

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

Your homepage downloads 3.0 MB in 296 requests on a phone: scripts 1.2 MB (95), other files 1,023 KiB (161) and images 552 KiB (26). Under 2 MB keeps phones on slow connections fast.

11 images (779 KiB) are 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.

3 images are downloaded at several times the size a phone draws them, for example moto-mount-pro-moto-mount-pro-53138-view01.webp at 390 px wide, shown at 116 px. Resized copies would save about 37 KiB.

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

23 tap targets are too small or too close together to hit reliably with a finger.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate 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.

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

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

Your title is 66 characters, so Google will cut it off around 60: “SP Connect | Montaje rápido y seguro de smartphones – SP United EU”.

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

Structured data found (Organization and WebSite) but with 3 problems, for example “Organization: url points at a different host (https://sp-connect.eu)”.

The homepage links to 224 pages on sp-connect.es and 9 external pages.

https://sp-connect.es/collections/iphone-18-series and https://sp-connect.es/collections/protectors have no meta description, so Google writes the search snippet from whatever text it finds.

https://sp-connect.es/products/phone-case-apple and https://sp-connect.es/products/phone-case-samsung use the same meta description. A description written for each page earns more clicks.

https://sp-connect.es/collections/phone-cases, https://sp-connect.es/products/phone-case-apple and https://sp-connect.es/products/phone-case-samsung have no <h1> headline, so visitors and search engines get no clear main topic.

https://sp-connect.es/collections/accessories, https://sp-connect.es/collections/protectors and https://sp-connect.es/collections/spare-parts took over 3 s to send their HTML from our server.

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

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

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

Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.