Website review, no card needed
alothaiminvestment.com website review
Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 85 checks
This review found 42 issues worth fixing on alothaiminvestment.com, 11 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 101 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 105 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.8 s
1.6 s
2.3 s
3.1 s
3.9 s
4.7 s
5.4 s
6.2 s
Speed
Improve image delivery
9.4 s · 6.9 MB20 images could be 6.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.4 s faster on a phone.
Render-blocking requests
1.0 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 69). 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 (Google CDN, Google Maps and Cloudflare CDN and others), adding 1.4 MB and 777 ms of main-thread time.
Reduce unused JavaScript
150 ms · 635 KiBAbout 635 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.
Google CDN adds 330 ms
330 msGoogle CDN costs a phone 330 ms of main-thread work and 734 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 CSS
300 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Maps adds 260 ms
260 msGoogle Maps costs a phone 260 ms of main-thread work and 468 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
150 ms · 46 KiB9 files are served with short cache lifetimes, so returning visitors download them again (46 KiB).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 112 ms. During a long task the page ignores taps.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 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.
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: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 40.4 s
40.4 sYour largest element takes 40.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Al Othaim Investment”.
Time to Interactive: 43.1 s
43.1 sThe page becomes fully interactive after 43.1 s. Good is under 3.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
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.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 105 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
2 checks passed
Total Blocking Time: 88 ms
88 msScripts block the page for only 88 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 23.6 MB in 108 requests
23.6 MBYour homepage downloads 23.6 MB in 108 requests on a phone: images 21.7 MB (62), scripts 1.3 MB (28) and other files 349 KiB (3). Under 2 MB keeps phones on slow connections fast.
13 images over 500 KB
13 images weigh 12.0 MB together. On a phone connection a single image that size takes seconds.
13 images far larger than shown
3.6 MB13 images are downloaded at several times the size a phone draws them, for example othaim-dammam.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 3.6 MB.
40 images in older formats
40 images (18.4 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.
13 images below the first screen load straight away
13 images further down the page (3.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
othaim-dammam.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 6.7 g of CO₂ per visit
6.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.68 g of CO₂e: 801.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
80 images without alt text
80 images have 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.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
29 links without text
29 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4, h4 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Al Othaim Investment”. 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.
Meta description is short (20 characters)
Your meta description is only 20 characters: “Al Othaim Investment”. 70 to 160 characters is enough to sell the click.
3 H1 headlines
There are 3 <h1> headlines (“Enriching the world of business”, “Inspiring and enriching lives” and “Shaping visions, creating legacies”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 XML sitemap
No XML sitemap at https://alothaiminvestment.com/sitemap.xml, so Google discovers your pages only by following links.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
120 internal links, 18 external
The homepage links to 120 pages on alothaiminvestment.com and 18 external pages.
1 checks passed
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://alothaiminvestment.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 (2,577 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages share a title
/, https://alothaiminvestment.com/about-us, https://alothaiminvestment.com/sectors, https://alothaiminvestment.com/sectors/malls, https://alothaiminvestment.com/sectors/entertainment and https://alothaiminvestment.com/sectors/life and 9 others all use the title “Al Othaim Investment”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://alothaiminvestment.com/about-us, https://alothaiminvestment.com/sectors, https://alothaiminvestment.com/sectors/cinemas, https://alothaiminvestment.com/mediacenter and https://alothaiminvestment.com/careers have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages with very little text
https://alothaiminvestment.com/ar, https://alothaiminvestment.com/sectors and https://alothaiminvestment.com/careers 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 39 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 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
16 small tap targets
16 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 817 words of copy
The homepage carries about 817 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
6 calls to action
The homepage has 6 calls to action, for example “Learn more” and “Contact”.
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 alothaiminvestment.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
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on alothaiminvestment.com, including 14 speed issues, 8 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.