Website review, no card needed

bloon-paris.fr logo

bloon-paris.fr website review

Visit site (opens in a new tab)Reviewed 19 November 202642 issues · 89 checks

This review found 42 issues worth fixing on bloon-paris.fr, 12 of them high impact, across 89 checks. The most urgent: page weight: 16.5 MB in 398 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.6 s1.4 sMay 30Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.7 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.7 s
Aug 15, 20261.9 s
Aug 22, 20262.2 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Nov 7, 20262.1 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
177 ms122 msMay 30Nov 14134 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026140 ms
Jun 6, 2026153 ms
Jun 13, 2026162 ms
Jun 20, 2026171 ms
Jun 27, 2026162 ms
Jul 4, 2026158 ms
Jul 11, 2026155 ms
Jul 18, 2026147 ms
Jul 25, 2026139 ms
Aug 1, 2026132 ms
Aug 8, 2026128 ms
Aug 15, 2026128 ms
Aug 22, 2026135 ms
Aug 29, 2026137 ms
Sep 5, 2026137 ms
Sep 12, 2026143 ms
Sep 19, 2026146 ms
Sep 26, 2026149 ms
Oct 3, 2026145 ms
Oct 10, 2026137 ms
Oct 17, 2026133 ms
Oct 24, 2026133 ms
Oct 31, 2026136 ms
Nov 7, 2026137 ms
Nov 14, 2026134 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 bloon-paris.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bloon-paris.fr at 1.1 s1.1 s
  2. bloon-paris.fr at 2.1 s2.1 s
  3. bloon-paris.fr at 3.2 s3.2 s
  4. bloon-paris.fr at 4.2 s4.2 s
  5. bloon-paris.fr at 5.3 s5.3 s
  6. bloon-paris.fr at 6.3 s6.3 s
  7. bloon-paris.fr at 7.4 s7.4 s
  8. bloon-paris.fr at 8.4 s8.4 s

Speed

11 to fix59
  • Main-thread work: 7.3 s

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

  • Improve image delivery

    650 ms · 2.6 MB

    16 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • Reduce unused JavaScript

    300 ms · 808 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hotjar, bloon-paris.eu and Klaviyo and others), adding 1.4 MB and 913 ms of main-thread time.

  • Mobile performance score: 59

    59/100

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

  • Use efficient cache lifetimes

    931 KiB

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

  • Render-blocking requests

    750 ms

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

  • Hotjar adds 402 ms

    402 ms

    Hotjar costs a phone 402 ms of main-thread work and 281 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.

  • bloon-paris.eu adds 240 ms

    240 ms

    bloon-paris.eu costs a phone 240 ms of main-thread work and 568 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.

  • 2,263 HTML elements

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

  • Klaviyo adds 138 ms

    138 ms

    Klaviyo costs a phone 138 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.

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    45 KiB

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

  • Reduce unused CSS

    14 KiB

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

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

  • Time to Interactive: 21.2 s

    21.2 s

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

  • Speed Index: 12.5 s

    12.5 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Total Blocking Time: 317 ms

    317 ms

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

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

  • Tap response (INP) held steady for real visitors

    -8%

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

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

    +16%

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

5 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user TTFB: 487 ms

    487 ms

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

  • Cumulative Layout Shift: 0.048

    0.048

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

Images and page weight

5 to fix25
  • Page weight: 16.5 MB in 398 requests

    16.5 MB

    Your homepage downloads 16.5 MB in 398 requests on a phone: media 8.8 MB (1), images 4.0 MB (39) and scripts 1.9 MB (85). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    banniere_post_kids_mobile.jpg weighs 517 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    banniere_post_kids_mobile.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).

  • 3 images in older formats

    3 images (633 KiB) 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.

  • 2 images far larger than shown

    257 KiB

    2 images are downloaded at several times the size a phone draws them, for example banniere_post_kids_mobile.jpg at 1,500 px wide, shown at 390 px. Resized copies would save about 257 KiB.

  • About 4.7 g of CO₂ per visit

    4.67 g

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

Accessibility

8 to fixGoogle 9691
  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 30 images without alt text

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

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 6 form fields without a label

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

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 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 9291
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (240 characters)

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

  • 158 internal links, 7 external

    The homepage links to 158 pages on bloon-paris.fr and 7 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Bloon Paris”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Siège ballon | Siège ergonomique – Bloon Paris”.

  • Canonical URL set

    The canonical URL is https://bloon-paris.fr/.

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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,426 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://bloon-paris.fr/blogs/le-journal has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://bloon-paris.fr/pages/la-marque, https://bloon-paris.fr/blogs/le-journal and https://bloon-paris.fr/pages/programme-de-parrainage have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://bloon-paris.fr/collections/les-capsules and https://bloon-paris.fr/collections/siege-bloon-kids took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 77 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=343075661&tm=gtm002&Ver=2&mid=864118c1-42c7-40a8-b232-69937aefa951&bo=1&sid=995a3980e45311f196969bc391b92c3c&vid=995a5c70e45311f193675543dbb35529&vids=1&msclkid=N&pi=9.

  • 43 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

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

  • No opening hours

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

  • 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 1,082 words of copy

    The homepage carries about 1,082 words of visible text.

6 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 10 short forms

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

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 40 cookies set on arrival

    40

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

  • 45 other companies contacted

    Loading the homepage contacts 45 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 bloon-paris.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
10 Shopify Products;Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on bloon-paris.fr, including 18 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