objetrama.fr website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Matomo and Facebook and others), adding 1.4 MB and 1.0 s of main-thread time.

About 125 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.

Google Tag Manager costs a phone 382 ms of main-thread work and 591 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.6 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Matomo costs a phone 313 ms of main-thread work and 62 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.

41 KiB could be saved by minifying JavaScript.

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

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

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

Your largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bic 4 Couleurs Rose Octobre Rose”.

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

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

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

Real visitors wait 204 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-17, real Chrome visitors' tap response (inp) went from 159 ms to 202 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 3.7 MB in 123 requests on a phone: images 1.6 MB (44), scripts 1.6 MB (36) and other files 212 KiB (34). Under 2 MB keeps phones on slow connections fast.

17 images (1.3 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.

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

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

4 images have no alt text, which hurts accessibility and image search.

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

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

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

ARIA role should be appropriate for the element: 11 elements on the page fail this check, rated minor by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

14 links have no real href, so search engines can't follow them.

The homepage links to 1,107 pages on objetrama.fr and 12 external pages.

There is no https://www.objetrama.fr/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://www.objetrama.fr/notre-catalogue.html, https://www.objetrama.fr/textile-casquette/t-shirts-personnalises-publicitaires/t-shirt-basique-personnalise.html and https://www.objetrama.fr/textile-casquette/t-shirts-personnalises-publicitaires/t-shirt-premium-personnalise.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

16 of 67 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.”).

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.doofinder.com/livelayer/1.8.209/css/2/common.css?v=1.8.209' from origin 'https…”.

Large scripts ship without source maps.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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