tinwaredirect.fr website review

About 313 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

8 third-party services load with your homepage (FontAwesome CDN, modules4u.biz and Google Tag Manager and others), adding 1.3 MB and 1.0 s of main-thread time.

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

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

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

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

FontAwesome CDN costs a phone 293 ms of main-thread work and 102 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 2,981 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google Tag Manager costs a phone 153 ms of main-thread work and 333 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 94 ms of main-thread work and 335 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.

Feefo.com costs a phone 63 ms of main-thread work and 351 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.

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

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

4 images could be 95 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

3 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Your homepage downloads 2.7 MB in 233 requests on a phone: scripts 1.2 MB (80), other files 801 KiB (104) and images 445 KiB (33). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 link inside paragraphs relies on colour alone to stand out.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Tinware Direct [FR]” and “Grossiste en emballages métal, carton et aluminium”). One clear main headline is easier for people and search engines.

Your meta description is 232 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 198 pages on tinwaredirect.fr and 24 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://tinwaredirect.fr/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://tinwaredirect.fr/collections/boites-metalliques/carr%C3%A9e, whose canonical is https://tinwaredirect.fr/collections/boites-metalliques/carr%c3%a9e. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://register.feefo.com/feefo-widgets-app/css/feefo_widgets_loader.7a1c5cf4d372692b26e3…”.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot 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 11 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.