legramme-qa.com website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.4 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Vimeo, Shopify and Clarity and others), adding 16.5 MB and 1.8 s of main-thread time.

Vimeo costs a phone 698 ms of main-thread work and 14.0 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.

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

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

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

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

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

Clarity costs a phone 254 ms of main-thread work and 29 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,526 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

ZenDesk costs a phone 170 ms of main-thread work and 386 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.

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

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

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.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 20.0 MB in 508 requests on a phone: other files 14.1 MB (300), scripts 2.7 MB (122) and images 2.6 MB (53). Under 2 MB keeps phones on slow connections fast.

contactez_nous_le_gramme.gif weighs 2.6 MB. On a phone connection a single image that size takes seconds.

1 image (2.6 MB) is 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.

banner2-homepage-nov26-mob_b2b48549-9385-44ea-b2d6-07d747f36 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).

1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

3 frames have no title, so screen-reader users cannot tell what they contain.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

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

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

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

No meta description, so Google writes its own snippet from whatever text it finds.

Google's crawler is blocked from indexing this page.

Your title is only 14 characters: “legramme-qa-fr”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 93 pages on legramme-qa.com and 11 external pages.

Your homepage links to /collections/jonc, which answers with an error. Visitors hit a dead end and search engines drop it.

/collections/bracelet and /collections/bague are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/collections/bracelet and /collections/bague have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/bracelet and /collections/bague have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187205295&tm=gtm002&Ver=2&mid=e09ed098-e020-49fa-9c84-9b7fa464e78e&bo=1&sid=cc5f1a80db0511f1972d498408b33655&vid=cc5f3c40db0511f1b726c33396d3c404&vids=1&msclkid=N&gtm_.

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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 “An error has been thrown while configuring your widget AbortError: signal is aborted without reason AbortError: signal …”.

Chrome logged issues while loading the page (“Cookie”).

6 links from your homepage to your own site are broken, for example https://legramme-qa.com/collections/jonc (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://legramme-qa.com/customer_authentication/redirect?locale=fr&region_country=FR.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

legramme-qa.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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 14 fields (0 required). Every extra field lowers completion.

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

legramme-qa.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

legramme-qa.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 Tag Manager, Hotjar, Klaviyo and Microsoft Ads and 4 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 31 cookies, 5 of them by other companies (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.