Website review, no card needed
jahia.com website review
Visit site (opens in a new tab)Reviewed 18 October 202627 issues · 76 checks
This review found 27 issues worth fixing on jahia.com, 5 of them high impact, across 76 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.0 s |
| May 2, 2026 | 2.3 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 105 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 89 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 112 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 182 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 130 ms |
| Oct 10, 2026 | 151 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 (desktop: 96). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
611 KiB15 files are served with short cache lifetimes, so returning visitors download them again (611 KiB).
Render-blocking requests
500 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.
Reduce unused JavaScript
150 ms · 316 KiBAbout 316 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Google Tag Manager and Hubspot and others), adding 653 KiB and 463 ms of main-thread time.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 165 ms. During a long task the page ignores taps.
Improve image delivery
110 KiB2 images could be 110 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Reduce unused CSS
20 KiBAbout 20 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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 871 ms of it running JavaScript. That is comfortably low.
Server response: 34 ms
34 msYour server sent the HTML in 34 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.
Real-user FCP: 4.1 s
4.1 sReal visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.3 s
3.3 sReal visitors wait 3.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 10.9 s
10.9 sThe page becomes fully interactive after 10.9 s. Good is under 3.8 s.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Tap response (INP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 104 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 81% slower for real visitors
+81%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.0 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 358 ms
358 msScripts block taps and scrolling for 358 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Enterprise CMS and DXP For multisite, multibrand, and multi…”. Most of its time is resource load delay (1.1 s).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user INP: 160 ms
160 msReal visitors wait 160 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 43.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.3 MB in 61 requests
1.3 MBYour homepage downloads 1.3 MB in 61 requests on a phone: scripts 969 KiB (31), images 243 KiB (21) and fonts 43 KiB (2). That is a lean page.
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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 images without alt text
5 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.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Enterprise CMS and DXP” and “Jahia, G2 leader in DXP (Fall 2026)”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (FAQPage, Organization, SoftwareApplication and WebPage) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
95 internal links, 4 external
The homepage links to 95 pages on jahia.com and 4 external pages.
6 checks passed
Meta description: 118 characters
Your meta description is 118 characters: “Deliver websites, portals, apps and personalized customer journeys with Jahia CMS & Digital Experience Platform (DXP).”.
Title: 58 characters
Your title is a healthy 58 characters: “Enterprise CMS & Digital Experience Platform (DXP) - Jahia”.
Canonical URL set
The canonical URL is https://www.jahia.com/en.
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://www.jahia.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.jahia.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.
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.
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,234 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.jahia.com/partners has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
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
2 small tap targets
2 of 10 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 “Sending form data to 'https://www.facebook.com/tr/' violates the following Content Security Policy directive: "form-act…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 800 words of copy
The homepage carries about 800 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “REQUEST DEMO” and “REQUEST A DEMO”.
10 calls to action
The homepage has 10 calls to action, for example “Pricing”, “Contact” and “Request Demo”.
Social proof on the page
Social proof on the homepage: a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
20 other companies contacted
Loading the homepage contacts 20 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 jahia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on jahia.com, including 15 speed issues, 5 SEO issues and 1 conversion gap. 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.