Website review, no card needed
calystene.com website review
Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 75 checks
This review found 33 issues worth fixing on calystene.com, 13 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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
71CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.3 s
2.0 s
2.6 s
3.3 s
3.9 s
4.6 s
5.2 s
Speed
Use efficient cache lifetimes
4.2 s · 949 KiB33 files are served with short cache lifetimes, so returning visitors download them again (949 KiB).
Render-blocking requests
2.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Improve image delivery
1.4 s · 300 KiB4 images could be 300 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce unused JavaScript
1.1 s · 213 KiBAbout 213 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.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
480 ms · 99 KiBAbout 99 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 480 ms faster on a phone.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 291 KiB and 215 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 592 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.9 s
7.9 sYour largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “La vocation de CALYSTENE est de développer des solutions in…”. Most of its time is element render delay (4.0 s).
Cumulative Layout Shift: 0.307
0.307The layout shifts by 0.307 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 7.9 s
7.9 sThe page becomes fully interactive after 7.9 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Total Blocking Time: 187 ms
187 msScripts block the page for only 187 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
slider-futura-smart-design-768x320.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 in older formats
4 images (325 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.
1 image below the first screen load straight away
1 image further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.35 g of CO₂e: 41.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.2 MB in 38 requests
1.2 MBYour homepage downloads 1.2 MB in 38 requests on a phone: scripts 513 KiB (13), images 409 KiB (9) and fonts 191 KiB (3). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Calystene, dossier patient informatisé, DPI, logiciel gestion cabinet médical”.
No XML sitemap
No XML sitemap at https://www.calystene.com/sitemap.xml, so Google discovers your pages only by following links.
34 internal links, 4 external
The homepage links to 34 pages on calystene.com and 4 external pages.
6 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Spécialiste des solutions de gestion de cabinets médicaux, de dossier patient informatisé (DPI) et de système d'informa…”.
One H1 headline
Your main headline reads: “CALYSTENE, le précurseur santé”.
Canonical URL set
The canonical URL is https://www.calystene.com/.
Structured data in place
Structured data found: 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.
AI search readiness
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.
No llms.txt
There is no https://www.calystene.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (309 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://www.calystene.com/contact, https://www.calystene.com/calystene-sa-le-precurseur-sante, https://www.calystene.com/futura-smart-design-solutions-informatiques-pour-hopitaux-et-cliniques/securite-augmentee, https://www.calystene.com/les-domaines-fonctionnels-gap, https://www.calystene.com/futura-smart-design-solutions-informatiques-pour-hopitaux-et-cliniques/telechargement and https://www.calystene.com/futura-city and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.calystene.com/futura-smart-design, whose canonical is https://www.calystene.com/futura-smart-design-a-lexport-premiere-etape-tunis-2014. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.calystene.com/contact and https://www.calystene.com/les-domaines-fonctionnels-gap have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://www.calystene.com/contact, https://www.calystene.com/actualites-des-solutions-informatique-en-sante-de-calystene, https://www.calystene.com/les-domaines-fonctionnels-gap, https://www.calystene.com/futura-smart-design-solutions-informatiques-pour-hopitaux-et-cliniques/telechargement and https://www.calystene.com/futura-smart-design-solutions-informatiques-pour-hopitaux-et-cliniques/telechargement-2 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
10 small tap targets
10 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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_TUNNEL_CONNECTION_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 246 words
The homepage has only about 246 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “[email protected]”.
1 call to action
The homepage has 1 call to action, for example “[email protected]”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
3 other companies contacted
Loading the homepage contacts 3 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 calystene.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Infomaniak Network SA
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 calystene.com, including 13 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.