Website review, no card needed
jahezgroup.com website review
Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 84 checks
This review found 40 issues worth fixing on jahezgroup.com, 10 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 76 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 80 ms |
| Jun 20, 2026 | 81 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 77 ms |
| Jul 11, 2026 | 78 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 81 ms |
| Aug 1, 2026 | 81 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 76 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 80 ms |
| Sep 12, 2026 | 83 ms |
| Sep 19, 2026 | 85 ms |
| Sep 26, 2026 | 83 ms |
| Oct 3, 2026 | 86 ms |
| Oct 10, 2026 | 83 ms |
| Oct 17, 2026 | 159 ms |
| Oct 24, 2026 | 151 ms |
| Oct 31, 2026 | 212 ms |
| Nov 7, 2026 | 220 ms |
| Nov 14, 2026 | 91 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
Render-blocking requests
1.8 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Use efficient cache lifetimes
1.0 MB44 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
842 KiB14 images could be 842 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
410 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 410 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Google CDN and Cloudflare CDN and others), adding 505 KiB and 134 ms of main-thread time.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Reduce unused JavaScript
70 KiBAbout 70 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 137 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
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.
Cumulative Layout Shift: 0.661
0.661The layout shifts by 0.661 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 101% slower for real visitors
+101%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 76 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 76 ms
76 msReal visitors wait 76 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Become the leading brand from Saudi to offer an ecosystem o…”.
Time to Interactive: 2.0 s
2.0 sThe page is fully interactive after 2.0 s.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.0 MB in 54 requests
2.0 MBYour homepage downloads 2.0 MB in 54 requests on a phone: images 1.4 MB (26), fonts 315 KiB (4) and scripts 234 KiB (8). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (983 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.
10 images below the first screen load straight away
10 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
31 KiB2 images are downloaded at several times the size a phone draws them, for example Screenshot-2024-11-20-at-4.15.02 PM.png at 1,266 px wide, shown at 370 px. Resized copies would save about 31 KiB.
About 0.6 g of CO₂ per visit
0.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
10 buttons without a name
10 buttons have no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (11 characters)
Your title is only 11 characters: “Jahez Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
33 internal links, 16 external
The homepage links to 33 pages on jahezgroup.com and 16 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://jahezgroup.com/.
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://jahezgroup.com/wp-sitemap.xml.
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://jahezgroup.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 (585 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://jahezgroup.com/ar all use the title “Jahez Group”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://jahezgroup.com/ar, https://jahezgroup.com/contact-us, https://jahezgroup.com/about-us, https://jahezgroup.com/our-brands, https://jahezgroup.com/newsroom and https://jahezgroup.com/sustainability and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://jahezgroup.com/ar, https://jahezgroup.com/about-us, https://jahezgroup.com/our-brands, https://jahezgroup.com/newsroom and https://jahezgroup.com/sustainability have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://jahezgroup.com/ar, https://jahezgroup.com/contact-us, https://jahezgroup.com/announcements, https://jahezgroup.com/analysts, https://jahezgroup.com/financial-calendar and https://jahezgroup.com/subscribe 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.
1 page slow to respond
https://jahezgroup.com/financial-information took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
8 broken images
8 images failed to load on a phone, for example https://jahezgroup.com/.
12 small tap targets
12 of 24 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 “Uncaught TypeError: $(...).EurolandIFrameAutoHeight is not a function”.
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.
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 719 words of copy
The homepage carries about 719 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: “CONTACT US”.
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”, “Subscribe Center” and “IR Contact”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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.
7 other companies contacted
Loading the homepage contacts 7 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 jahezgroup.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
- Cloudflare
Company
- Headquarters
- Riyadh
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on jahezgroup.com, including 13 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.