Website review, no card needed
ismena.com website review
Visit site (opens in a new tab)Reviewed 3 November 202615 issues · 74 checks
This review found 15 issues worth fixing on ismena.com, 7 of them high impact, across 74 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.0 s |
| May 23, 2026 | 4.8 s |
| Jun 6, 2026 | 5.6 s |
| Jun 13, 2026 | 5.7 s |
| Jun 20, 2026 | 5.7 s |
| Jun 27, 2026 | 5.7 s |
| Jul 4, 2026 | 5.9 s |
| Jul 11, 2026 | 5.9 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 3.9 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 157 ms |
| Jun 27, 2026 | 156 ms |
| Jul 4, 2026 | 157 ms |
| Jul 11, 2026 | 134 ms |
| Jul 18, 2026 | 113 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 105 ms |
| Sep 12, 2026 | 108 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 115 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 101 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
1.5 s
3.1 s
4.6 s
6.1 s
7.6 s
9.2 s
10.7 s
12.2 s
Speed
Use efficient cache lifetimes
2.0 s · 4.0 MB44 files are served with short cache lifetimes, so returning visitors download them again (4.0 MB).
Main-thread work: 12.0 s
A phone's processor spends 12.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
400 ms · 746 KiB15 images could be 746 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Unpkg and YouTube), adding 123 KiB and 101 ms of main-thread time.
Render-blocking requests
50 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save 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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 228 ms
228 msYour server sent the HTML in 228 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.
Time to Interactive: 34.9 s
34.9 sThe page becomes fully interactive after 34.9 s. Good is under 3.8 s.
Speed Index: 12.1 s
12.1 sVisually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sustaining Tomorrow's Innovation”.
Real-user TTFB: 917 ms
917 msReal visitors wait 917 ms for your server to start answering (75th percentile). Good is under 800 ms.
9 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 100 ms
100 msReal visitors wait 100 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.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 141 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 63% faster for real visitors
-63%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 162 ms
162 msScripts block the page for only 162 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 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: 9.6 MB in 242 requests
9.6 MBYour homepage downloads 9.6 MB in 242 requests on a phone: other files 5.4 MB (195), images 3.6 MB (39) and fonts 385 KiB (4). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (133 KiB) is 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 (133 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.72 g of CO₂e: 326.9 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
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.
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 37 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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
Title is short (9 characters)
Your title is only 9 characters: “iSolution”. Between 30 and 65 characters leaves room to say what you do and for whom.
71 internal links, 15 external
The homepage links to 71 pages on ismena.com and 15 external pages.
7 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “iSolution is a Google Cloud premier partner in Riyadh delivering cloud, data & AI, integration, and security to 1000+ e…”.
One H1 headline
Your main headline reads: “Sustaining Tomorrow's Innovation”.
Canonical URL set
The canonical URL is https://www.ismena.com/.
Structured data in place
Structured data found: Organization and 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.ismena.com/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (655 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ismena.com/llms.txt (2 KiB, 17 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
7 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.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
51 of 56 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 536 words of copy
The homepage carries about 536 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 Us” and “Contact us”.
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Contact us” and “Talk to usTalk to us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, 27 customer or partner logos and 2 trust badges.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 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 ismena.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 15 issues on ismena.com, including 9 speed issues, 1 SEO issue 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.