Website review, no card needed

gnoce.fr logo

gnoce.fr website review

Visit site (opens in a new tab)Reviewed 9 November 202655 issues · 96 checks

This review found 55 issues worth fixing on gnoce.fr, 19 of them high impact, across 96 checks. The most urgent: page weight: 29.5 MB in 366 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.9 s1.6 sMay 23Nov 72.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.3 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.7 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.7 s
Oct 31, 20262.8 s
Nov 7, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
342 ms127 msMay 23Nov 7312 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026172 ms
May 30, 2026175 ms
Jun 6, 2026178 ms
Jun 13, 2026174 ms
Jun 20, 2026171 ms
Jun 27, 2026162 ms
Jul 4, 2026157 ms
Jul 11, 2026152 ms
Jul 18, 2026165 ms
Jul 25, 2026194 ms
Aug 1, 2026219 ms
Aug 8, 2026262 ms
Aug 15, 2026271 ms
Aug 22, 2026269 ms
Aug 29, 2026280 ms
Sep 5, 2026274 ms
Sep 12, 2026271 ms
Sep 19, 2026271 ms
Sep 26, 2026260 ms
Oct 3, 2026265 ms
Oct 10, 2026271 ms
Oct 17, 2026282 ms
Oct 24, 2026298 ms
Oct 31, 2026317 ms
Nov 7, 2026312 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of gnoce.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gnoce.fr at 1.0 s1.0 s
  2. gnoce.fr at 2.1 s2.1 s
  3. gnoce.fr at 3.1 s3.1 s
  4. gnoce.fr at 4.1 s4.1 s
  5. gnoce.fr at 5.2 s5.2 s
  6. gnoce.fr at 6.2 s6.2 s
  7. gnoce.fr at 7.2 s7.2 s
  8. gnoce.fr at 8.2 s8.2 s

Speed

14 to fix36
  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 8.1 s

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

  • 3,649 HTML elements

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

  • Improve image delivery

    14.0 MB

    90 images could be 14.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (cincopa.com, Facebook and Google CDN and others), adding 17.9 MB and 1.4 s of main-thread time.

  • cincopa.com adds 603 ms

    603 ms

    cincopa.com costs a phone 603 ms of main-thread work and 6.7 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.

  • Reduce unused JavaScript

    300 ms · 919 KiB

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

  • cloudfront.net adds 118 ms

    118 ms

    cloudfront.net costs a phone 118 ms of main-thread work and 9.9 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.

  • Reduce unused CSS

    450 ms · 315 KiB

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

  • Use efficient cache lifetimes

    637 KiB

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

  • 20 long tasks on the main thread

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

  • Facebook adds 312 ms

    312 ms

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

  • Other Google APIs/SDKs adds 78 ms

    78 ms

    Other Google APIs/SDKs costs a phone 78 ms of main-thread work and 533 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.

  • Legacy JavaScript

    56 KiB

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

  • Font display

    50 ms

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 28.5 s

    28.5 s

    Your largest element takes 28.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday Gets Personal - Buy 2 Get 2 Free”.

  • Speed Index: 16.8 s

    16.8 s

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

  • Time to Interactive: 70.8 s

    70.8 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Real-user INP: 316 ms

    316 ms

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

  • Tap response (INP) got 81% slower for real visitors

    +81%

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

  • Largest content (LCP) got 53% slower for real visitors

    +53%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 31 images without width and height

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 337 ms

    337 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 29.5 MB in 366 requests

    29.5 MB

    Your homepage downloads 29.5 MB in 366 requests on a phone: images 19.3 MB (273), other files 6.4 MB (40) and scripts 3.3 MB (32). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

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

  • 32 images far larger than shown

    3.4 MB

    32 images are downloaded at several times the size a phone draws them, for example 6aab92654848egif.gif at 1,080 px wide, shown at 163 px. Resized copies would save about 3.4 MB.

  • 37 images in older formats

    37 images (9.2 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.

  • 5 images below the first screen load straight away

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

  • About 8.4 g of CO₂ per visit

    8.37 g

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

Accessibility

11 to fixGoogle 7384
  • 25 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • 204 images without alt text

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

  • Malformed lists

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (90 elements)

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

  • 64 links without text

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

  • 2 form fields without a label

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

1 checks passed
  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8576
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 67 links crawlers can't follow

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

  • Meta description is long (236 characters)

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

  • Structured data has 2 problems

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

  • No XML sitemap

    No XML sitemap at https://www.gnoce.fr/gz/sitemap.xml, so Google discovers your pages only by following links.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 381 internal links, 4 external

    The homepage links to 381 pages on gnoce.fr and 4 external pages.

3 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Gnoce Officiel | 2+2 OFFERTS | Bijoux Charms”.

  • Canonical URL set

    The canonical URL is https://www.gnoce.fr/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.gnoce.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,655 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 5 pages share a meta description

    https://www.gnoce.fr/top-picks/best-sellers-sales.html, https://www.gnoce.fr/catalogsearch/advanced, https://www.gnoce.fr/new-sales/collections/japonism-series.html, https://www.gnoce.fr/new-sales/gothic-aesthetics.html and https://www.gnoce.fr/all-product.html use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.gnoce.fr/oneday/wishlist has no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://www.gnoce.fr/top-picks/best-sellers-sales.html, https://www.gnoce.fr/new-sales/collections/japonism-series.html, https://www.gnoce.fr/new-sales/gothic-aesthetics.html, https://www.gnoce.fr/product-halloween-ghost-fairy-light-bead-cid4-knc006-b.html, https://www.gnoce.fr/product-gnoce-pink-christmas-series-pink-christmas-tree-clasp-dangle-charm-platinum-plated-silver-blend-cid0-llc076-b.html and https://www.gnoce.fr/product-multi-sided-photo-custom-bead-cid8-jsc047-c-s.html and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static.gnoce.com/css/cookieconsent.css' from origin 'https://www.gnoce.fr' has bee…”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    44 of 44 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 2,094 words of copy

    The homepage carries about 2,094 words of visible text.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop Now” and “Pocket Mirror ~ Goldener Traum Shop Now”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 24 cookies set on arrival

    24

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

  • No consent tool detected

    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.

  • 33 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at gnoce.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Tag Manager
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on gnoce.fr, including 25 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25