lepickleball.fr website review

2 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.4 s faster on a phone.

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

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

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

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

About 38 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 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

4 third-party services load with your homepage (loox.io, gelato.tech and Shopify and others), adding 138 KiB and 111 ms of main-thread time.

1 long task block the main thread while loading, the longest for 54 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.

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

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

The first text or image appears after 1.9 s on a phone. Good is under 1.8 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 164 requests on a phone: images 3.1 MB (4), other files 678 KiB (74) and scripts 350 KiB (73). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example jon-matthews-DqrIPR__wyo-unsplash.jpg at 3,936 px wide, shown at 390 px. Resized copies would save about 2.9 MB.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 68 characters, so Google will cut it off around 60: “Smash in Style | Culture-Driven Pickleball Gear & Apparel – RETROGRD”.

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

The homepage links to 15 pages on lepickleball.fr and 1 external page.

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.

/collections/all and /policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/pickleball-for-clubs-leagues-and-associations-in-the-united-states and /collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/pickleball-rules-in-the-united-states, /pages/pickleball-for-clubs-leagues-and-associations-in-the-united-states, /collections/all and /products/the-pickle-tee took over 3 s to send their HTML from our server.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

retrogrd.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

retrogrd.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

DMARC is set to p=none, so mail pretending to be lepickleball.fr is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 6 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.