ekhool.com website review

Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

About 125 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

6 third-party services load with your homepage (Google Tag Manager, Cookie-Script.com and lfeeder.com and others), adding 421 KiB and 528 ms of main-thread time.

Google Tag Manager costs a phone 445 ms of main-thread work and 365 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.

About 62 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.

4 long tasks block the main thread while loading, the longest for 357 ms. During a long task the page ignores taps.

9 files are served with short cache lifetimes, so returning visitors download them again (44 KiB).

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

The page has 1,835 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

5 images could be 247 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Polyfills for old browsers add 5 KiB JavaScript that modern phones do not need.

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.

Your largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Best LMS Software Platform for Organization Training Soluti…”.

The page becomes fully interactive after 10.8 s. Good is under 3.8 s.

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 373 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 117 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.2 MB in 80 requests on a phone: images 1.5 MB (54), scripts 492 KiB (10) and fonts 137 KiB (4). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example lms-for-enterprise-segment.webp at 1,200 px wide, shown at 320 px. Resized copies would save about 35 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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.

9 form fields have no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (6 elements).

Structured data found (Brand, BreadcrumbList, HowTo and ItemList) but with 1 problem, for example “Service: no offers (price) block”.

The homepage links to 230 pages on ekhool.com and 13 external pages.

We fetched 15 pages linked from your homepage (of 190 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Error: <svg> attribute height: Expected length, "40pxx".”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

15 links from your homepage to your own site are broken, for example https://ekhool.com/ar (404).

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ekhool.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

ekhool.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 977 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, 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.

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.