raidlight.com website review

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

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

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

8 third-party services load with your homepage (speaz.com, Clarity and loox.io and others), adding 1.6 MB and 1.5 s of main-thread time.

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

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

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

speaz.com costs a phone 507 ms of main-thread work and 68 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.

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

Clarity costs a phone 328 ms of main-thread work and 30 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.

Klaviyo costs a phone 222 ms of main-thread work and 342 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.

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

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

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

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

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

19 KiB JavaScript is shipped twice across bundles.

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.

5 KiB could be saved by minifying CSS.

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

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

Your largest element takes 4.7 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.111 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 6.0 MB in 479 requests on a phone: images 2.3 MB (39), other files 1.8 MB (264) and scripts 1.4 MB (126). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example 202602_LANCEMENT_SS26_1080x1080_gilets.jpg at 1,080 px wide, shown at 358 px. Resized copies would save about 126 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

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

Your <h1> is empty.

The homepage links to 441 pages on raidlight.com and 6 external pages.

There is no https://raidlight.com/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.

https://raidlight.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://raidlight.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://raidlight.com/policies/refund-policy, https://raidlight.com/policies/shipping-policy and https://raidlight.com/customer_authentication/redirect 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 https://raidlight.com/policies/refund-policy, whose canonical is https://raidlight.com/en/policies/refund-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://raidlight.com/policies/refund-policy, https://raidlight.com/policies/shipping-policy, https://raidlight.com/pages/notre-histoire and https://raidlight.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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