Website review, no card needed

homesport.shop logo

homesport.shop website review

Visit site (opens in a new tab)Reviewed 12 November 202637 issues · 83 checks

This review found 37 issues worth fixing on homesport.shop, 13 of them high impact, across 83 checks. The most urgent: page weight: 24.2 MB in 360 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
3.3 s2.8 sOct 10Nov 72.9 s
Show as table
DateReal-visitor load time (LCP)
Oct 10, 20263.3 s
Oct 17, 20263.2 s
Oct 24, 20263.1 s
Oct 31, 20263.0 s
Nov 7, 20262.9 s

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 homesport.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. homesport.shop at 0.9 s0.9 s
  2. homesport.shop at 1.9 s1.9 s
  3. homesport.shop at 2.8 s2.8 s
  4. homesport.shop at 3.8 s3.8 s
  5. homesport.shop at 4.7 s4.7 s
  6. homesport.shop at 5.6 s5.6 s
  7. homesport.shop at 6.6 s6.6 s
  8. homesport.shop at 7.5 s7.5 s

Speed

11 to fix54
  • Reduce unused JavaScript

    1.4 s · 452 KiB

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

  • Improve image delivery

    1.1 s · 467 KiB

    16 images could be 467 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Main-thread work: 5.1 s

    A phone's processor spends 5.1 s on main-thread work while loading, 1.7 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 (ContentSquare, Klaviyo and Klarna and others), adding 1.7 MB and 870 ms of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • ContentSquare adds 394 ms

    394 ms

    ContentSquare costs a phone 394 ms of main-thread work and 185 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.

  • Render-blocking requests

    400 ms

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

  • Klaviyo adds 153 ms

    153 ms

    Klaviyo costs a phone 153 ms of main-thread work and 311 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.

  • 1,698 HTML elements

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

  • tidio.co adds 109 ms

    109 ms

    tidio.co costs a phone 109 ms of main-thread work and 515 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.

  • Shopify adds 32 ms

    32 ms

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

  • Use efficient cache lifetimes

    250 ms · 86 KiB

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 31 KiB

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

  • Duplicated JavaScript

    150 ms · 13 KiB

    13 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    28 KiB

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

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

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 42 ms

    42 ms

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

Core Web Vitals

8 to fix33
  • 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.

  • Largest Contentful Paint: 13.7 s

    13.7 s

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

  • Time to Interactive: 16.4 s

    16.4 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user INP: 238 ms

    238 ms

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

  • Total Blocking Time: 501 ms

    501 ms

    Scripts block taps and scrolling for 501 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.

  • Largest content (LCP) held steady for real visitors

    -9%

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

4 checks passed
  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 677 ms

    677 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 24.2 MB in 360 requests

    24.2 MB

    Your homepage downloads 24.2 MB in 360 requests on a phone: media 19.6 MB (3), images 1.9 MB (97) and scripts 1.4 MB (86). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    16 KiB

    4 images are downloaded at several times the size a phone draws them, for example Gemini_Generated_Image_5rfibr5rfibr5rfi_2.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 16 KiB.

  • About 6.9 g of CO₂ per visit

    6.85 g

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

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

Accessibility

7 to fixGoogle 8990
  • 4 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have 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.

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

  • ARIA role should be appropriate for the element (7 elements)

    ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 4 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 (318 characters)

    Your meta description is 318 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.

  • 36 internal links, 0 external

    The homepage links to 36 pages on homesport.shop and 0 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Le Black Friday est enfin là : -40% sur le StepEasy”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Le 1er site dédié au sport à domicile en France ! – HomeSport”.

  • Canonical URL set

    The canonical URL is https://www.homesport.shop/.

  • Structured data in place

    Structured data found: FAQPage, 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://www.homesport.shop/sitemap.xml.

AI search readiness

100
4 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 (1,567 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 9 pages without a meta description

    https://www.homesport.shop/collections/nos-produits, https://www.homesport.shop/pages/sav-et-reparations, https://www.homesport.shop/pages/a-propos, https://www.homesport.shop/pages/contact, https://www.homesport.shop/policies/legal-notice and https://www.homesport.shop/policies/terms-of-sale and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.homesport.shop/products/stepeasy, https://www.homesport.shop/pages/sav-et-reparations, https://www.homesport.shop/pages/a-propos, https://www.homesport.shop/pages/contact, https://www.homesport.shop/products/tapis-de-course-foldable-pro and https://www.homesport.shop/products/velo-elliptique-homesport8 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 14 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

2 checks passed
  • Tap targets are thumb-sized

    32 of 34 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “[email protected]”.

  • 6 short forms

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 homesport.shop, 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

Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Judge Me Reviews · Klarna On Site Messaging · tidio.co · weglot.com · amazonaws.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
Tailwind CSS
E-commerce
Shopify
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 homesport.shop, including 19 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