Website review, no card needed

purpleleafshop.fr logo

purpleleafshop.fr website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 80 checks

This review found 33 issues worth fixing on purpleleafshop.fr, 7 of them high impact, across 80 checks. The most urgent: page weight: 29.2 MB in 91 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
1.7 s1.1 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
210 ms151 msMay 16Oct 31203 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026161 ms
May 23, 2026158 ms
May 30, 2026162 ms
Jun 6, 2026163 ms
Jun 13, 2026162 ms
Jun 20, 2026167 ms
Jun 27, 2026175 ms
Jul 4, 2026177 ms
Jul 11, 2026183 ms
Jul 18, 2026185 ms
Jul 25, 2026183 ms
Aug 1, 2026188 ms
Aug 8, 2026186 ms
Aug 15, 2026185 ms
Aug 22, 2026188 ms
Aug 29, 2026185 ms
Sep 5, 2026185 ms
Sep 12, 2026183 ms
Sep 19, 2026179 ms
Sep 26, 2026179 ms
Oct 3, 2026184 ms
Oct 10, 2026193 ms
Oct 17, 2026203 ms
Oct 24, 2026202 ms
Oct 31, 2026203 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 purpleleafshop.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. purpleleafshop.fr at 0.5 s0.5 s
  2. purpleleafshop.fr at 1.0 s1.0 s
  3. purpleleafshop.fr at 1.4 s1.4 s
  4. purpleleafshop.fr at 1.9 s1.9 s
  5. purpleleafshop.fr at 2.4 s2.4 s
  6. purpleleafshop.fr at 2.9 s2.9 s
  7. purpleleafshop.fr at 3.4 s3.4 s
  8. purpleleafshop.fr at 3.8 s3.8 s

Speed

5 to fix97
  • Improve image delivery

    8.4 MB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Shopify, codeblackbelt.com and Google Tag Manager and others), adding 28.3 MB and 5 ms of main-thread time.

  • Shopify adds 5 ms

    5 ms

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

  • Render-blocking requests

    650 ms

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

  • 1,747 HTML elements

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    27 KiB

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

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

  • Use efficient cache lifetimes

    4 KiB

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

3 checks passed
  • Mobile performance score: 97

    97/100

    Your mobile performance score is 97. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 43 ms of it running JavaScript. That is comfortably low.

  • Server response: 14 ms

    14 ms

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

Core Web Vitals

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

  • Real-user INP: 261 ms

    261 ms

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

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

    +27%

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

  • 24 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

10 checks passed
  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (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: 533 ms

    533 ms

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

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

    -19%

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

  • Speed Index: 2.9 s

    2.9 s

    Visually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Time to Interactive: 2.0 s

    2.0 s

    The page is fully interactive after 2.0 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix25
  • Page weight: 29.2 MB in 91 requests

    29.2 MB

    Your homepage downloads 29.2 MB in 91 requests on a phone: media 19.1 MB (3), images 9.4 MB (52) and scripts 493 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    42e6756e4b73e7a7107f98ef99a66485.gif weighs 19.8 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (19.8 MB) 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.

  • An image on the first screen is lazy-loaded

    42e6756e4b73e7a7107f98ef99a66485.gif 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).

  • 5 images far larger than shown

    75 KiB

    5 images are downloaded at several times the size a phone draws them, for example 2026_-1250x1800_8ec1f00d-b37c-4818-9357-1e7dfb6aeac5.jpg at 1,250 px wide, shown at 390 px. Resized copies would save about 75 KiB.

  • About 8.3 g of CO₂ per visit

    8.28 g

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

Accessibility

7 to fixGoogle 8191
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 22 images without alt text

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

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

    All page content should be contained by landmarks: 14 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.

  • 1 form field without a label

    1 form field has 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.

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • Meta description is long (320 characters)

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

  • No social preview image

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

  • 368 internal links, 21 external

    The homepage links to 368 pages on purpleleafshop.fr and 21 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “PURPLE LEAF France”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Purple Leaf France - #1 Fournisseur de meubles de jardin modernes”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://purpleleafshop.fr/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing logo, 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 (1,263 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://purpleleafshop.fr/pages/parasol-de-terrasse, https://purpleleafshop.fr/collections/parasol-droit, https://purpleleafshop.fr/collections/parasol-de-2-5-x-2-5-m and https://purpleleafshop.fr/collections/parasol-de-2-7-x-2-7-m have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://purpleleafshop.fr/collections/promotion, https://purpleleafshop.fr/collections/parasol-et-pied, https://purpleleafshop.fr/pages/parasol-de-terrasse, https://purpleleafshop.fr/collections/parasol-classique, https://purpleleafshop.fr/collections/motif-bois-parasol and https://purpleleafshop.fr/collections/parasol-avec-led and 9 others have 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 117 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 9285
  • 8 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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.

  • 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 290 words of copy

    The homepage carries about 290 words of visible text.

4 checks passed
  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 5 cookies set on arrival

    5

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 purpleleafshop.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 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Boost Ai Search Filter · One Ai Email Sms Marketing · Pagefly Ai Page Builder · Variant Image Wizard Swatch · Ryviu Product Reviews · Inbox · Frequently Bought · Popup Sign Up Sales Banner · Countdown Timer · Gdpr Backpack · one.store · pwztag.com · expertvillagemedia.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 Analytics | Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on purpleleafshop.fr, including 10 speed issues, 2 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