Website review, no card needed

braceletwatch.fr logo

braceletwatch.fr website review

Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 81 checks

This review found 26 issues worth fixing on braceletwatch.fr, 9 of them high impact, across 81 checks. The most urgent: main-thread work: 9.6 s. 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
1.6 s1.3 sAug 1Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
Aug 1, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
156 ms97 msAug 15Oct 31117 ms
Show as table
DateReal-visitor tap response (INP)
Aug 15, 2026149 ms
Aug 29, 2026131 ms
Sep 5, 2026120 ms
Sep 12, 2026108 ms
Sep 19, 2026104 ms
Sep 26, 2026105 ms
Oct 3, 2026110 ms
Oct 10, 2026110 ms
Oct 17, 2026120 ms
Oct 31, 2026117 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 braceletwatch.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. braceletwatch.fr at 4.4 s4.4 s
  2. braceletwatch.fr at 8.7 s8.7 s
  3. braceletwatch.fr at 13.1 s13.1 s
  4. braceletwatch.fr at 17.4 s17.4 s
  5. braceletwatch.fr at 21.8 s21.8 s
  6. braceletwatch.fr at 26.2 s26.2 s
  7. braceletwatch.fr at 30.5 s30.5 s
  8. braceletwatch.fr at 34.9 s34.9 s

Speed

7 to fix78
  • Main-thread work: 9.6 s

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

  • 6,648 HTML elements

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

  • Mobile performance score: 78

    78/100

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

  • Render-blocking requests

    450 ms

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

  • Reduce unused JavaScript

    334 KiB

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

  • Shopify adds 90 ms

    90 ms

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

  • azurefd.net adds 79 ms

    79 ms

    azurefd.net costs a phone 79 ms of main-thread work and 330 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Shopify and Cookie-Script.com and others), adding 882 KiB and 427 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 27 KiB

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

  • 7 long tasks on the main thread

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

  • Use efficient cache lifetimes

    65 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

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

  • Legacy JavaScript

    5 KiB

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

1 checks passed
  • Server response: 31 ms

    31 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 12.4 s

    12.4 s

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

  • Speed Index: 8.3 s

    8.3 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 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 text “Sélectionnez votre montre pour trouver bracelets & coques”.

  • Largest content (LCP) held steady for real visitors

    +3%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 115 ms

    115 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 594 ms

    594 ms

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

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

  • Total Blocking Time: 123 ms

    123 ms

    Scripts block the page for only 123 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 276 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 276 requests on a phone: scripts 1.1 MB (75), other files 790 KiB (116) and images 398 KiB (49). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.72 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9790
  • 2 text elements with low contrast

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

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

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (7 elements).

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 17 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 20 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Bracelet de montre Smartwatch | ENORME sélection de bracelets de montre”.

  • Meta description is long (165 characters)

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

  • 527 internal links, 6 external

    The homepage links to 527 pages on braceletwatch.fr and 6 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Sélectionnez votre montre pour trouver bracelets & coques”.

  • Canonical URL set

    The canonical URL is https://braceletwatch.fr/.

  • Structured data in place

    Structured data found: OnlineStore and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

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

  • XML sitemap found

    Your XML sitemap is reachable at https://braceletwatch.fr/sitemap.xml.

AI search readiness

100
3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://braceletwatch.fr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://braceletwatch.fr/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://braceletwatch.fr/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://braceletwatch.fr/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://braceletwatch.fr/customer_authentication/redirect, https://braceletwatch.fr/collections/apple, https://braceletwatch.fr/collections/apple-watch-series-11, https://braceletwatch.fr/collections/apple-watch-series-10, https://braceletwatch.fr/collections/apple-watch-series-9 and https://braceletwatch.fr/collections/apple-watch-series-8 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages slow to respond

    https://braceletwatch.fr/collections/apple-watch-series-11-42mm, https://braceletwatch.fr/collections/apple-watch-series-10, https://braceletwatch.fr/collections/apple-watch-series-9-45mm, https://braceletwatch.fr/collections/apple-watch-series-9-41mm, https://braceletwatch.fr/collections/apple-watch-series-9 and https://braceletwatch.fr/collections/apple-watch-series-8-41mm and 3 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 200 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

Google 96100
  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix56
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • Only about 16 words

    The homepage has only about 16 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

3 checks passed
  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks, a star rating, 1 trust badge and “40.000+ clients”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 7 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 braceletwatch.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

X Shield Store Guard · Microsoft Clarity · Multifeeds · Zipchat Ai Chatbot · Trusted Shops Reviews And More · Glo Color Swatch · Stape Remix

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on braceletwatch.fr, including 10 speed issues, 2 SEO issues and 6 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