padelkiwi.com website review

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

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

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

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

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

Shopify costs a phone 124 ms of main-thread work and 361 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 third-party services load with your homepage (Shopify, Google Tag Manager and Trust Pilot and others), adding 821 KiB and 340 ms of main-thread time.

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

About 69 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.

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

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

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

17 KiB JavaScript is shipped twice across bundles.

10 KiB could be saved by minifying CSS.

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.

5 KiB could be saved by minifying JavaScript.

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 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black”.

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

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

Real visitors wait 226 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your homepage downloads 4.3 MB in 344 requests on a phone: images 2.1 MB (55), other files 902 KiB (111) and scripts 745 KiB (152). Under 2 MB keeps phones on slow connections fast.

23 images (2.6 MB) 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.

4 images are downloaded at several times the size a phone draws them, for example home-cat-calzado.webp at 1,000 px wide, shown at 308 px. Resized copies would save about 310 KiB.

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 3 <h1> headlines (“Padel Kiwi”, “BLACK NOVEMBER” and “UP TO 60% OFF”). One clear main headline is easier for people and search engines.

The homepage links to 340 pages on padelkiwi.com and 10 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.padelkiwi.com/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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.padelkiwi.com/pages/devoluciones, whose canonical is https://www.padelkiwi.com/en-us/pages/devoluciones. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.padelkiwi.com/pages/devoluciones, https://www.padelkiwi.com/en-us/collections/pallas-babolat-3 and https://www.padelkiwi.com/en-us/collections/pallas-nox-1 have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 154 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 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 598 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (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 7 cookies, 1 of them by other companies (measured from a US location before any click).

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