dallah.com website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.

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

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

YouTube costs a phone 1.0 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 37 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Google CDN and others), adding 3.1 MB and 1.6 s of main-thread time.

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

About 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 350 ms faster on a phone.

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

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

Google CDN costs a phone 122 ms of main-thread work and 348 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.

Polyfills for old browsers add 6 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.

3 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 23.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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.

Your homepage downloads 6.1 MB in 155 requests on a phone: scripts 2.8 MB (42), images 2.6 MB (54) and stylesheets 276 KiB (25). Under 2 MB keeps phones on slow connections fast.

25 images (1.6 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 (732 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example DallahLogoNewH.webp at 1,600 px wide, shown at 390 px. Resized copies would save about 108 KiB.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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 on the page fails this check, rated moderate by axe-core.

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

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

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

Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 29 characters: “الرئيسية - دله البركة القابضة”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 10 characters: “دله البركة”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links have no real href, so search engines can't follow them.

The homepage links to 28 pages on dallah.com and 12 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

Your homepage links to /faqs, which answers with an error. Visitors hit a dead end and search engines drop it.

/about-us, /our-investment, /social-responsibility, /news-and-media, /contact-us and /en and 7 others use the same meta description. A description written for each page earns more clicks.

/about-us, /our-investment, /social-responsibility, /news-and-media, /contact-us and /en and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

/about-us, /our-investment, /social-responsibility, /contact-us, /news-media/ask301225 and /news-media/rasm271125 and 5 others 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.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

1 link from your homepage to your own site is broken, for example https://dallah.com/faqs (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 22 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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, 1 of them by other companies (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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.