Website review, no card needed
jubailiagrotecgroup.com website review
Visit site (opens in a new tab)Reviewed 2 November 202646 issues · 92 checks
This review found 46 issues worth fixing on jubailiagrotecgroup.com, 19 of them high impact, across 92 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 8.8 s |
| May 23, 2026 | 8.6 s |
| May 30, 2026 | 8.8 s |
| Jun 6, 2026 | 8.4 s |
| Jun 13, 2026 | 8.4 s |
| Jun 20, 2026 | 8.5 s |
| Jun 27, 2026 | 8.4 s |
| Jul 4, 2026 | 8.8 s |
| Jul 11, 2026 | 9.1 s |
| Jul 18, 2026 | 8.9 s |
| Jul 25, 2026 | 8.7 s |
| Aug 1, 2026 | 8.8 s |
| Aug 8, 2026 | 8.5 s |
| Aug 15, 2026 | 8.7 s |
| Aug 22, 2026 | 8.6 s |
| Aug 29, 2026 | 8.3 s |
| Sep 5, 2026 | 8.4 s |
| Sep 12, 2026 | 8.3 s |
| Sep 19, 2026 | 8.5 s |
| Sep 26, 2026 | 8.6 s |
| Oct 3, 2026 | 8.6 s |
| Oct 10, 2026 | 8.6 s |
| Oct 17, 2026 | 8.8 s |
| Oct 24, 2026 | 9.0 s |
| Oct 31, 2026 | 9.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 94 ms |
| May 23, 2026 | 93 ms |
| May 30, 2026 | 92 ms |
| Jun 6, 2026 | 94 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 92 ms |
| Jun 27, 2026 | 93 ms |
| Jul 4, 2026 | 92 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 94 ms |
| Aug 1, 2026 | 94 ms |
| Aug 8, 2026 | 90 ms |
| Aug 15, 2026 | 93 ms |
| Aug 22, 2026 | 93 ms |
| Aug 29, 2026 | 91 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 95 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 93 ms |
| Oct 17, 2026 | 92 ms |
| Oct 24, 2026 | 96 ms |
| Oct 31, 2026 | 97 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
How it loaded on a phone
0.7 s
1.3 s
2.0 s
2.6 s
3.3 s
4.0 s
4.6 s
5.3 s
Speed
Use efficient cache lifetimes
2.1 s · 2.2 MB51 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Reduce unused JavaScript
1.4 s · 239 KiBAbout 239 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.
Render-blocking requests
1.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
900 ms · 1.9 MB24 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Reduce unused CSS
480 ms · 74 KiBAbout 74 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.
Minify JavaScript
480 ms · 69 KiB69 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 410 ms
410 msGoogle Tag Manager costs a phone 410 ms of main-thread work and 177 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 272 ms. During a long task the page ignores taps.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, YouTube and Cloudflare CDN and others), adding 244 KiB and 418 ms of main-thread time.
Minify CSS
130 ms · 11 KiB11 KiB could be saved by minifying CSS.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 85 ms
85 msYour server sent the HTML in 85 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 LCP: 12.2 s
12.2 sReal visitors wait 12.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 12.7 s
12.7 sReal visitors see the first content after 12.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 6.1 s
6.1 sReal visitors wait 6.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Focused and Forward At the heart of our operations is our m…”.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Total Blocking Time: 725 ms
725 msScripts block taps and scrolling for 725 ms in total while the page loads. Good is under 200 ms.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 94 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 8.8 s to 9.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 80 requests
4.5 MBYour homepage downloads 4.5 MB in 80 requests on a phone: images 3.7 MB (58), scripts 554 KiB (9) and fonts 188 KiB (6). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
jadestone-office.png weighs 1.1 MB. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (2.2 MB) 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.
An image on the first screen is lazy-loaded
Our-Services.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).
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
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.
ARIA role should be appropriate for the element (40 elements)
ARIA role should be appropriate for the element: 40 elements on the page fail this check, rated minor by axe-core.
17 form fields without a label
17 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail 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
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 11 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 short (21 characters)
Your title is only 21 characters: “Jubaili Agrotec Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
46 links crawlers can't follow
46 links have no real href, so search engines can't follow them.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (281 characters)
Your meta description is 281 characters; Google truncates after about 160, so the end of your pitch is cut.
55 internal links, 8 external
The homepage links to 55 pages on jubailiagrotecgroup.com and 8 external pages.
5 checks passed
One H1 headline
Your main headline reads: “JAG”.
Canonical URL set
The canonical URL is https://www.jubailiagrotecgroup.com/.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.jubailiagrotecgroup.com/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://www.jubailiagrotecgroup.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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 (1,766 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a title
https://www.jubailiagrotecgroup.com/subsidiaries/ja/zambia and https://www.jubailiagrotecgroup.com/subsidiaries/ja/brazil have no <title>, so Google invents the link text in results.
15 pages share a meta description
https://www.jubailiagrotecgroup.com/subsidiaries, https://www.jubailiagrotecgroup.com/about, https://www.jubailiagrotecgroup.com/services, https://www.jubailiagrotecgroup.com/contact, https://www.jubailiagrotecgroup.com/subsidiaries/ja/nigeria and https://www.jubailiagrotecgroup.com/subsidiaries/ja/ghana and 9 others use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://www.jubailiagrotecgroup.com/subsidiaries/ja/nigeria, https://www.jubailiagrotecgroup.com/subsidiaries/ja/ghana, https://www.jubailiagrotecgroup.com/subsidiaries/ja/ivory-coast, https://www.jubailiagrotecgroup.com/subsidiaries/ja/uganda, https://www.jubailiagrotecgroup.com/subsidiaries/ja/tanzania and https://www.jubailiagrotecgroup.com/subsidiaries/ja/kenya and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.jubailiagrotecgroup.com/subsidiaries/ja/nigeria, https://www.jubailiagrotecgroup.com/subsidiaries/ja/ghana, https://www.jubailiagrotecgroup.com/subsidiaries/ja/ivory-coast and https://www.jubailiagrotecgroup.com/subsidiaries/ja/uganda took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
5 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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.
Best practices
11 small tap targets
11 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 18-field form
Your longest form asks for 18 fields (12 required). Every extra field lowers completion.
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 853 words of copy
The homepage carries about 853 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “CONTACT US” and “APPLY TODAY”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 2 trust badges.
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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
6 other companies contacted
Loading the homepage contacts 6 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 jubailiagrotecgroup.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
- Angular
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on jubailiagrotecgroup.com, including 19 speed issues, 4 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.