pylones.com website review

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

33 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Doofinder and others), adding 1.1 MB and 629 ms of main-thread time.

Google Tag Manager costs a phone 496 ms of main-thread work and 684 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 1,814 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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.

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “La vie en Roses”.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 11.3 MB in 156 requests on a phone: media 6.4 MB (1), images 3.1 MB (82) and scripts 1.3 MB (48). Under 2 MB keeps phones on slow connections fast.

12 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

10 images (1.7 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.

5 images are downloaded at several times the size a phone draws them, for example Bols-décoratifs-et-cubes-de-sucre-abondants-MIRROR.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 315 KiB.

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

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://devax.pylones.com/1_index_sitemap.xml, so Google discovers your pages only by following links.

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

Your <h1> is empty.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 250 pages on pylones.com and 6 external pages.

There is no /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.

/en and / all use the title “Pylones - Créateur de sourires - Gift ideas”. Search engines can't tell which page to show for a search, so each competes with the others.

/en/353-small-kitchen-appliances and /en/2923-christmas-table-decoration have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /, whose canonical is /en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/ has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.pylones.com/67445-decli_default/purse-mini-purse.jpg.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

http://pylones.com does not redirect to https, so some visitors land on the insecure version.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Opening https://pylones.com goes through 2 redirects before the homepage loads.

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.

pylones.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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.

The homepage carries about 715 words of visible text.

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

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.

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