rossignol.com website review

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

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

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

81 files are served with short cache lifetimes, so returning visitors download them again (3.9 MB).

8 third-party services load with your homepage (Google CDN, Google Tag Manager and guuru.com and others), adding 9.5 MB and 1.5 s of main-thread time.

About 1.6 MB of JavaScript is downloaded but never used on this page.

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

livestory.io costs a phone 201 ms of main-thread work and 6.8 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.

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

Google Tag Manager costs a phone 420 ms of main-thread work and 880 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.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

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

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

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

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Skier carving through powder snow with Rossignol Arcade ski…”.

10 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-31, real Chrome visitors' tap response (inp) went from 209 ms to 229 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.2 MB in 244 requests on a phone: images 7.6 MB (141), scripts 3.3 MB (44) and other files 780 KiB (30). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example 69f0c17219ad4b6f754dd44e.jpg at 2,048 px wide, shown at 159 px. Resized copies would save about 1.8 MB.

69f0c17219ad4b6f754dd44e.jpg weighs 785 KiB. On a phone connection a single image that size takes seconds.

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

9 images (1.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.

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

ARIA dialog and alertdialog nodes should have an accessible name: 10 elements on the page fail this check, rated serious by axe-core.

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

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

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

Your title is 73 characters, so Google will cut it off around 60: “Rossignol | Ski, snowboard, bike | Outdoor clothing, footwear & equipment”.

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://www.rossignol.com/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 392 pages on rossignol.com and 16 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.

/us-en/stores and /us-en/wishlist 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 /us-en/gift-ideas/rossignol-x-ac-milan, whose canonical is /us-en/rossignol-x-ac-milan. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

/us-en/gift-ideas/for-men, /us-en/gift-ideas/for-women, /us-en/gift-ideas/for-kids, /us-en/gift-ideas/equipment, /us-en/gift-ideas/rossignol-x-ac-milan and /us-en/men/new-arrivals took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

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

Opening https://rossignol.com goes through 3 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.

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

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

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

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

The homepage carries about 1,079 words of visible text.

DMARC is set to p=none, so mail pretending to be rossignol.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, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 16 cookies (measured from a US location before any click).

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