welkit.fr website review

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

56 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Facebook and others), adding 1.7 MB and 915 ms of main-thread time.

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

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

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

About 412 KiB of JavaScript is downloaded but never used on this page.

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

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

Klaviyo costs a phone 190 ms of main-thread work and 505 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 56 ms of main-thread work and 368 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.

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

About 53 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 67 KiB JavaScript that modern phones do not need.

6 KiB could be saved by minifying CSS.

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

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

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

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Welkit”. Most of its time is element render delay (2.4 s).

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

Your homepage downloads 16.1 MB in 426 requests on a phone: media 7.3 MB (2), images 5.9 MB (136) and scripts 1.7 MB (143). Under 2 MB keeps phones on slow connections fast.

Wiley_X_Spear_Dual_809377a8-4a26-4c2c-9100-1c5e99db5600.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

5 tap targets are too small or too close together to hit reliably with a finger.

2 images have 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.

36 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: 40 elements on the page fail this check, rated minor by axe-core.

The homepage links to 764 pages on welkit.fr and 0 external pages.

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

https://welkit.com/products/e-carte-cadeau-welkit declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://welkit.com/pages/wishlist and https://welkit.com/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://welkit.com/products/e-carte-cadeau-welkit all use the title “Welkit | Equipement Militaire, Tactique & Outdoor”. Search engines can't tell which page to show for a search, so each competes with the others.

https://welkit.com/pages/wishlist, https://welkit.com/collections/meilleures-ventes, https://welkit.com/pages/marques-2, https://welkit.com/pages/aide, https://welkit.com/pages/club-welkit and https://welkit.com/customer_authentication/redirect and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://welkit.com/products/e-carte-cadeau-welkit, https://welkit.com/pages/wishlist, https://welkit.com/pages/marques-2, https://welkit.com/customer_authentication/redirect and https://welkit.com/collections/chaussures have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 197 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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,517 words of visible text.

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