aigle.com website review

21 images could be 506 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

Your mobile performance score is 24 (desktop: 57). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (alc-crm.com, Google Tag Manager and Google CDN and others), adding 5.1 MB and 946 ms of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Global-e costs a phone 108 ms of main-thread work and 3.5 MB 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.

alc-crm.com costs a phone 345 ms of main-thread work and 891 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.

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

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

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

Google CDN costs a phone 150 ms of main-thread work and 354 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

29 KiB could be saved by minifying JavaScript.

15 KiB could be saved by minifying CSS.

Desktop scores 57 but mobile only 24. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 31.9 s. Good is under 3.8 s.

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The layout shifts by 0.886 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

Your homepage downloads 16.0 MB in 180 requests on a phone: media 7.9 MB (1), fonts 2.8 MB (15) and images 2.2 MB (61). Under 2 MB keeps phones on slow connections fast.

28 images (1.8 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.

1 image is downloaded at several times the size a phone draws it, for example THEM03-SHERPAREVOLUTION_MIXTE_BM172_03.jpg at 4,096 px wide, shown at 390 px. Resized copies would save about 191 KiB.

1 image further down the page (208 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 311 pages on aigle.com and 8 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 /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.

/fr/fr/fr-fr-selection-ventes-privees, /fr/fr/vp-menu-remise-categories/ventes-privees-selection-40, /fr/fr/vp-menu-remise-categories/ventes-privees-selection-30 and /fr/fr/pre-collection are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/fr/fr and /fr/fr/lp-aigle-by-setchu.html all use the title “AIGLE | Ventes privées | Vêtements et chaussures outdoor”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/fr/fr/vp-categories-femme/ventes-privees-femme-parkas, /fr/fr/vp-categories-femme/ventes-privees-femme-polaires, /fr/fr/vp-categories-femme/ventes-privees-femme-vetements, /fr/fr/vp-categories-femme/ventes-privees-femme-pantalons, /fr/fr/vp-categories-homme/ventes-privees-homme-parkas and /fr/fr/vp-categories-homme/ventes-privees-homme-polaires and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/fr/fr/fr-fr-selection-ventes-privees/ventes-privees-femme and /fr/fr/fr-fr-selection-ventes-privees/ventes-privees-homme use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /fr/fr/vp-categories-femme/ventes-privees-femme-polaires, whose canonical is /on/demandware.store/Sites-aigle-fr-Site/fr_FR/Page-Show. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/fr/fr/aigle-lifeproof.html has no <h1> headline, so visitors and search engines get no clear main topic.

/fr/fr/vp-menu-remise-categories/ventes-privees-selection-30 took over 3 s to send its HTML from our server.

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

4 images failed to load on a phone, for example https://www.aigle.com/fr/fr.

111 of 234 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

Large scripts ship without source maps.

http://aigle.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.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be aigle.com is still delivered. Reports are on, so moving to quarantine is the next step.

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