eahli.com website review

79 files are served with short cache lifetimes, so returning visitors download them again (14.9 MB).

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 12.3 s.

About 1.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 9.3 s faster on a phone.

12 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

About 819 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

263 KiB could be saved by minifying CSS.

The HTML itself could arrive about 1.1 s sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 1.2 s on a phone.

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

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

A phone's processor spends 2.5 s on main-thread work while loading, 619 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Your server takes 1.3 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

4 third-party services load with your homepage (Google Tag Manager, Snapchat and Twitter Online Conversion Tracking and others), adding 529 KiB and 346 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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 visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.97 (75th percentile). Good is under 0.1.

Real visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.

The first text or image appears after 12.6 s on a phone. Good is under 1.8 s.

Your largest element takes 31.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We care about your experience on our website, which is why …”.

Visually, the page fills in at 31.7 s (Speed Index). Good is under 3.4 s.

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

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

50 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 135 ms to 132 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 4.5 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.7 MB in 92 requests on a phone: images 11.2 MB (60), stylesheets 1.8 MB (13) and scripts 1.4 MB (13). Under 2 MB keeps phones on slow connections fast.

3 images weigh 7.5 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example ABK_Logo_-_High_Res..jpg at 11,811 px wide, shown at 200 px. Resized copies would save about 7.0 MB.

21 images (11.0 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.

8 images further down the page (7.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

3 buttons have no accessible name, so screen readers announce just “button”.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

43 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

15 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 14 <h1> headlines (“”, “Double Your Rewards with Every Fuel Up” and “Earn An Extra Salary With Alfouz!”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

19 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

There is no robots.txt at abk.eahli.com/robots.txt, the first file search crawlers ask for.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 292 pages on eahli.com and 30 external pages.

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.

There is no /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.

/en/abk-group/about-abk, /en/abk-group/corporate-governance, /en/abk-group/ir-home-page, /en/abk-group/esg, /en/cards/offers/discounts and /en/luxury-discounts and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/en/luxury-discounts and /en/packages/tajer/al-tajer-plus took over 3 s to send their HTML from our server.

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

6 images failed to load on a phone, for example https://abk.eahli.com/en/.

20 of 56 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Executing inline script violates the following Content Security Policy directive 'script-src 'unsafe-eval' 'self' https…”.

Chrome logged issues while loading the page (“Content security policy”).

1 link to other sites is dead, for example http://twitter.com/Abk_kuwait (520).

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://eahli.com goes through 2 redirects before the homepage loads.

2 links go through two or more redirects, for example https://itunes.apple.com/sa/app/smart-mobi/id942856310?mt=8.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block, 1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

eahli.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.

eahli.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.

Social proof on the homepage: 10 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 783 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 Analytics, Google Tag Manager, Snap Pixel and X (Twitter) Ads (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 12 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.