Website review, no card needed
simoneabordeaux.com website review
Visit site (opens in a new tab)Reviewed 6 November 202631 issues · 82 checks
This review found 31 issues worth fixing on simoneabordeaux.com, 18 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #37,073 of 109,350 reviewed websitesbeats 60%
- #24,698 of 61,859 online storesbeats 54%
- #23,830 of 56,401 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 5.1 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.1 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.0 s |
| Aug 1, 2026 | 5.1 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.2 s |
| Aug 22, 2026 | 5.2 s |
| Aug 29, 2026 | 5.1 s |
| Sep 5, 2026 | 5.1 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 149 ms |
| May 23, 2026 | 148 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 160 ms |
| Jun 20, 2026 | 165 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 172 ms |
| Jul 18, 2026 | 174 ms |
| Jul 25, 2026 | 175 ms |
| Aug 1, 2026 | 178 ms |
| Aug 8, 2026 | 178 ms |
| Aug 15, 2026 | 175 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 165 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 142 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 141 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 149 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
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.1 s
3.9 s
4.7 s
5.5 s
6.3 s
Speed
Use efficient cache lifetimes
2.6 s · 445 KiB33 files are served with short cache lifetimes, so returning visitors download them again (445 KiB).
Improve image delivery
1.8 s · 407 KiB14 images could be 407 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Reduce unused JavaScript
1.8 s · 330 KiBAbout 330 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.2 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,530 HTML elements
The page has 3,530 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Yotpo, Klaviyo and wisepops.net and others), adding 1.1 MB and 578 ms of main-thread time.
Legacy JavaScript
450 ms · 63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Minify JavaScript
300 ms · 12 KiB12 KiB could be saved by minifying JavaScript.
Klaviyo adds 123 ms
123 msKlaviyo costs a phone 123 ms of main-thread work and 347 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.
Duplicated JavaScript
200 ms · 33 KiB33 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 25 KiBAbout 25 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 20.2 s
20.2 sYour largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Les cookies nous permettent de personnaliser le contenu et …”.
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 149 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 150 ms
150 msReal visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 524 ms
524 msReal visitors wait 524 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.5 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 149 ms
149 msScripts block the page for only 149 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 359 requests
4.1 MBYour homepage downloads 4.1 MB in 359 requests on a phone: scripts 1.5 MB (123), images 1.3 MB (70) and other files 809 KiB (122). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
1d6bfe1e-4ee8-49cd-a22b-a8f19c94294c.gif weighs 806 KiB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (806 KiB) 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.
About 1.2 g of CO₂ per visit
1.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 139.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
ARIA attributes must conform to valid names (1 element)
ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Unlabelled dropdowns
1 dropdown has no label.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
244 internal links, 10 external
The homepage links to 244 pages on simoneabordeaux.com and 10 external pages.
8 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Colorful women's jewelry and fancy enameled metal bracelets. Discover the Simone universe in Bordeaux, online and in ou…”.
One H1 headline
Your main headline reads: “Enameled metal costume jewelry”.
Title: 48 characters
Your title is a healthy 48 characters: “Simone à Bordeaux: Costume and emotional jewelry”.
Canonical URL set
The canonical URL is https://www.simoneabordeaux.com/en.
Structured data in place
Structured data found: Organization 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://www.simoneabordeaux.com/sitemap.xml.
AI search readiness
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.
Text is in the HTML
Your server sends the page's text in the HTML (892 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 83 found) and read each the way a search engine does.
7 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.
Every page has an H1
Each page we checked has a main headline.
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
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
49 of 52 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 525 words of copy
The homepage carries about 525 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Christmas Collection” and “START SHOPPING”.
6 calls to action
The homepage has 6 calls to action, for example “Shop Christmas Collection”, “Shop Autumn Winter 2026” and “Join us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
31 cookies set on arrival
31Opening the homepage sets 31 cookies, 1 of them by other companies (measured from a US location before any click).
46 other companies contacted
Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 simoneabordeaux.com, 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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Sami B2b Lock · Klaviyo Email Marketing Sms · Instafeed · Wisepops Popup Builder Cro · Addingwell · Yotpo Product Reviews · Yotpo Loyalty Rewards · Gift Box · Wholesale Lock Hide Price · Swish · mycustomizer.com · trustpilot.com
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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Bordeaux
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on simoneabordeaux.com, including 18 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.