Website review, no card needed
getjolt.fr website review
Visit site (opens in a new tab)Reviewed 6 November 202635 issues · 83 checks
This review found 35 issues worth fixing on getjolt.fr, 8 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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
82B- #33,407 of 118,657 reviewed websitesbeats 66%
- #22,281 of 67,370 online storesbeats 60%
- #21,542 of 61,425 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 984 ms |
| May 23, 2026 | 974 ms |
| May 30, 2026 | 971 ms |
| Jun 6, 2026 | 979 ms |
| Jun 13, 2026 | 988 ms |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 187 ms |
| May 23, 2026 | 188 ms |
| May 30, 2026 | 193 ms |
| Jun 6, 2026 | 200 ms |
| Jun 13, 2026 | 202 ms |
| Jun 20, 2026 | 203 ms |
| Jun 27, 2026 | 200 ms |
| Jul 4, 2026 | 192 ms |
| Jul 11, 2026 | 188 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 181 ms |
| Aug 8, 2026 | 187 ms |
| Aug 15, 2026 | 193 ms |
| Aug 22, 2026 | 202 ms |
| Aug 29, 2026 | 207 ms |
| Sep 5, 2026 | 210 ms |
| Sep 12, 2026 | 206 ms |
| Sep 19, 2026 | 202 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 197 ms |
| Oct 17, 2026 | 202 ms |
| Oct 24, 2026 | 203 ms |
| Oct 31, 2026 | 201 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
Speed
Mobile performance score: 86
86/100Your mobile performance score is 86. 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 (YouTube, Other Google APIs/SDKs and Shopify and others), adding 2.8 MB and 479 ms of main-thread time.
Render-blocking requests
700 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
YouTube adds 464 ms
464 msYouTube costs a phone 464 ms of main-thread work and 1,022 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.
Reduce unused JavaScript
523 KiBAbout 523 KiB of JavaScript is downloaded but never used on this page.
1,876 HTML elements
The page has 1,876 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 3 ms
3 msShopify costs a phone 3 ms of main-thread work and 1.7 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.
Improve image delivery
182 KiB4 images could be 182 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
131 KiBAbout 131 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
56 KiB8 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 629 ms of it running JavaScript. That is comfortably low.
Server response: 77 ms
77 msYour server sent the HTML in 77 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.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.207
0.207The layout shifts by 0.207 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 187 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 182 ms
182 msReal visitors wait 182 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 785 ms
785 msReal visitors wait 785 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 134 ms
134 msScripts block the page for only 134 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.4 s
1.4 sYour largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “_______L_____ayout”.
Images and page weight
Page weight: 3.4 MB in 112 requests
3.4 MBYour homepage downloads 3.4 MB in 112 requests on a phone: images 1.6 MB (34), scripts 1.3 MB (48) and fonts 240 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BOLT_58a42db7-040d-4dce-b607-902b767cbb40.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).
1 image far larger than shown
176 KiB1 image is downloaded at several times the size a phone draws it, for example 20200407190016_Logo_Olympique_de_Marseille.svg at 1,950 px wide, shown at 52 px. Resized copies would save about 176 KiB.
1 image in older formats
1 image (30 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.0 g of CO₂ per visit
0.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor 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
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
57 internal links, 7 external
The homepage links to 57 pages on getjolt.fr and 7 external pages.
8 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Découvrez des articles pour la Récupération Musculaire, comme des Pistolet de Massage, des Bottes Pressothérapie, des T…”.
One H1 headline
Your main headline reads: “<img src="//getjolt.fr/cdn/shop/files/Groupe_5_3x_a17cb0d7-9af7-43ae-a8e0-370ad1690074_100x.png?v=1629978449" srcset="/…”.
Title: 44 characters
Your title is a healthy 44 characters: “Équipements de Récupération Musculaire JOLT™”.
Canonical URL set
The canonical URL is https://getjolt.fr/.
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://getjolt.fr/sitemap.xml.
AI search readiness
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 (932 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://getjolt.fr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://getjolt.fr/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://getjolt.fr/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages without a meta description
https://getjolt.fr/pages/athletes-ambassadeurs-jolt, https://getjolt.fr/pages/presse-medias-jolt, https://getjolt.fr/pages/blog-jolt-performance, https://getjolt.fr/pages/notre-mission and https://getjolt.fr/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://getjolt.fr/pages/athletes-ambassadeurs-jolt, https://getjolt.fr/pages/presse-medias-jolt, https://getjolt.fr/pages/programme-musculaire, https://getjolt.fr/pages/video-tutoriel-utilisation, https://getjolt.fr/pages/tetes-massage and https://getjolt.fr/pages/mode-operatoire-jolt-boots and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://getjolt.fr/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
3 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.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 small tap targets
2 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Unexpected token ')' Function (<anonymous>)”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 447 words of copy
The homepage carries about 447 words of visible text.
3 checks passed
7 short forms
7 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and TikTok Pixel.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Klaviyo (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 1 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.
18 other companies contacted
Loading the homepage contacts 18 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 getjolt.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on getjolt.fr, including 14 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.