Website review, no card needed

paindesucre.uk logo

paindesucre.uk website review

Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 78 checks

This review found 37 issues worth fixing on paindesucre.uk, 13 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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
3.3 s1.0 sMay 23Jul 41.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.0 s
May 30, 20262.1 s
Jun 6, 20261.7 s
Jun 13, 20261.4 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
160 ms73 msMay 30Jun 2083 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026150 ms
Jun 6, 2026129 ms
Jun 13, 202697 ms
Jun 20, 202683 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 paindesucre.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. paindesucre.uk at 0.5 s0.5 s
  2. paindesucre.uk at 0.9 s0.9 s
  3. paindesucre.uk at 1.4 s1.4 s
  4. paindesucre.uk at 1.8 s1.8 s
  5. paindesucre.uk at 2.3 s2.3 s
  6. paindesucre.uk at 2.7 s2.7 s
  7. paindesucre.uk at 3.2 s3.2 s
  8. paindesucre.uk at 3.7 s3.7 s

Speed

10 to fix58
  • Reduce unused JavaScript

    1.1 s · 761 KiB

    About 761 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    1.3 s

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

  • Main-thread work: 4.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (paindesucre.com, Klaviyo and Google Tag Manager and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 528 KiB

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

  • Mobile performance score: 58

    58/100

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

  • Improve image delivery

    100 ms · 531 KiB

    11 images could be 531 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 87 KiB

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

  • paindesucre.com adds 389 ms

    389 ms

    paindesucre.com costs a phone 389 ms of main-thread work and 341 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.

  • Klaviyo adds 265 ms

    265 ms

    Klaviyo costs a phone 265 ms of main-thread work and 550 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

    250 ms · 27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 11 long tasks on the main thread

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

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • Minify JavaScript

    13 KiB

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

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix55
  • Largest Contentful Paint: 14.5 s

    14.5 s

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

  • Time to Interactive: 23.5 s

    23.5 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Total Blocking Time: 415 ms

    415 ms

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

  • Not enough real-visitor data yet

    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.

3 checks passed
  • Tap response (INP) got 35% faster for real visitors

    -35%

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

  • Largest content (LCP) got 49% faster for real visitors

    -49%

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

  • Cumulative Layout Shift: 0.029

    0.029

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

Images and page weight

3 to fix53
  • Page weight: 13.0 MB in 395 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 395 requests on a phone: media 8.6 MB (1), scripts 2.1 MB (151) and images 1.0 MB (33). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    PaindeSucre-Dualvideo-miniature-sarah-sima-4.jpg 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).

  • 4 images far larger than shown

    257 KiB

    4 images are downloaded at several times the size a phone draws them, for example PaindeSucre-entree-categorie-mobile-une-piece-soya-4.jpg at 800 px wide, shown at 189 px. Resized copies would save about 257 KiB.

  • About 3.7 g of CO₂ per visit

    3.68 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8491
  • 6 tap targets too small

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

  • 3 text elements with low contrast

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

  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • Zoom is disabled

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

  • All page content should be contained by landmarks (1 element)

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://paindesucre.com)”.

  • No social preview image

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

  • 65 internal links, 9 external

    The homepage links to 65 pages on paindesucre.uk and 9 external pages.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Find our most beautiful creations in a spring-summer collection mixing: 1-piece swimwear, 2-piece swimwear and beachwea…”.

  • One H1 headline

    Your main headline reads: “Pain de Sucre - French swimwear house since 1985”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Luxury Swimwear, Swimwear and Lingerie - Pain de Sucre”.

  • Canonical URL set

    The canonical URL is https://paindesucre.uk/.

  • 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://paindesucre.uk/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing sameAs (social profiles), 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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 6 pages without a meta description

    https://paindesucre.uk/pages/wishlist, https://paindesucre.uk/collections/idees-cadeaux-noel, https://paindesucre.uk/collections/nouvelle-collection-bodywear, https://paindesucre.uk/collections/best-sellers, https://paindesucre.uk/pages/la-maison and https://paindesucre.uk/collections/collection-bain-ete-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://paindesucre.uk/pages/la-maison has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=22022634&tm=gtm002&Ver=2&mid=e86d27a5-3367-4cec-9f90-9aceb08cdca0&bo=1&sid=a4a6e3c0daf311f1b5fb058e45b0ed06&vid=a4a6ec40daf311f1a0329726681aa8ca&vids=1&msclkid=N&pi=91.

  • 63 small tap targets

    63 of 92 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 470 words of copy

    The homepage carries about 470 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “FIND A SHOP”, “Contact” and “Request a return”.

  • 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

1 to fix
  • 9 trackers load before any consent

    9

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

  • 38 cookies set on arrival

    38

    Opening the homepage sets 38 cookies, 3 of them by other companies (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.

  • 50 other companies contacted

    Loading the homepage contacts 50 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 paindesucre.uk, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Wrapped · Sortd Merchandiser · Cbb Keep Share Cart · Instafeed · Gift Card Hero All In One · Klaviyo Email Marketing Sms · Easylocation

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

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on paindesucre.uk, including 15 speed issues, 2 SEO issues and 3 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