gobelets.com website review

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

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

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

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

14 images could be 317 KiB 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.

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

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

Facebook costs a phone 368 ms of main-thread work and 232 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.

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

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

Google Tag Manager costs a phone 271 ms of main-thread work and 165 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,431 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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 JavaScript.

3 KiB could be saved by minifying CSS.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 179 ms to 190 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.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.6 MB in 246 requests on a phone: images 3.5 MB (50), scripts 1.6 MB (78) and other files 677 KiB (94). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

2 images (3.1 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.

3 images further down the page (72 KiB) 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.87 g of CO₂e: 224.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

32 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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.

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

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

The homepage links to 213 pages on gobelets.com and 10 external pages.

/pages/configurator has no <h1> headline, so visitors and search engines get no clear main topic.

/pages/configurator has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/collections/verres-a-eau-personnalises took over 3 s to send its HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://gobelets.com/cdn/shop/t/11/assets/app.css?v=27792' because its MIME type ('text/ht…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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

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.

gobelets.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.

gobelets.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

DMARC is set to p=none, so mail pretending to be gobelets.com is still delivered. Add a report address, check the reports, then move to quarantine.

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, HubSpot, LinkedIn Insight 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 30 cookies, 8 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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.