pdhsports.com website review

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

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

8 third-party services load with your homepage (Shopify, Yotpo and Clarity and others), adding 1.1 MB and 1.5 s of main-thread time.

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

Yotpo costs a phone 271 ms of main-thread work and 264 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.

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

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

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

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

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

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

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 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nox 27 range just landed”.

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 476 requests on a phone: images 2.7 MB (128), scripts 1.1 MB (107) and other files 799 KiB (201). Under 2 MB keeps phones on slow connections fast.

2027_-_AGUSTIN_TAPIA_-_GENIUS_12K_ALUM_XTREM_-1.jpg 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).

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

1 image is downloaded at several times the size a phone draws it, for example 12SLA12023_01syngutnatural.png at 390 px wide, shown at 40 px. Resized copies would save about 47 KiB.

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

31 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

There are 6 <h1> headlines (“Nox 27 range just landed”, “Shop the new 27 Bullpadel range” and “The Viper Lebron 3.1 has arrived”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("q")”.

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

The homepage links to 547 pages on pdhsports.com and 11 external pages.

https://pdhsports.com/collections/babolat-lebron-27-collection and https://pdhsports.com/collections/bullpadel-2027-collection are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://pdhsports.com/collections/babolat-lebron-27-collection, https://pdhsports.com/pages/lacoste, https://pdhsports.com/collections/bullpadel-2027-collection, https://pdhsports.com/collections/k-swiss-indoor-shoes, https://pdhsports.com/pages/nox and https://pdhsports.com/collections/sale and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://pdhsports.com/collections/padel-rackets, https://pdhsports.com/collections/padel-bags, https://pdhsports.com/collections/padel-balls and https://pdhsports.com/collections/padel-shoes took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97278270&Ver=2&mid=c98fdf15-590d-4d44-bdcf-6ff5c7781757&bo=1&sid=4abc1490d80411f1a0251b5c03aa870a&vid=4abc41e0d80411f18261c37696702370&vids=1&msclkid=N&pi=918639831&lg.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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 2,049 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, Klaviyo and Meta Pixel and 2 mores (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 25 cookies (measured from a US location before any click).

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