dar-engineering.com website review

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

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

18 images could be 18.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

4 third-party services load with your homepage (JSDelivr CDN, Cloudflare CDN and Google Fonts and others), adding 27.9 MB and 74 ms of main-thread time.

Azure Web Services costs a phone 0 ms of main-thread work and 27.8 MB 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.

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

About 26 KiB of CSS is downloaded but never applied on this page.

6 KiB could be saved by minifying CSS.

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

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 see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

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

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

Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your homepage downloads 28.0 MB in 81 requests on a phone: images 27.9 MB (49), stylesheets 54 KiB (5) and scripts 40 KiB (4). Under 2 MB keeps phones on slow connections fast.

17 images weigh 26.0 MB together. On a phone connection a single image that size takes seconds.

18 images are downloaded at several times the size a phone draws them, for example Alfanar Manufacturing Complex and Administration Building (1 at 1,920 px wide, shown at 334 px. Resized copies would save about 14.9 MB.

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

10 images further down the page (11.4 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 7.94 g of CO₂e: 953.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 tap targets are too small or too close together to hit reliably with a finger.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

3 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 skip levels (h1 → h3, h3 → h5 and h4 → h6), which makes the page harder to scan with a screen reader.

Your title is only 8 characters: “DAR Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 8 characters: “DAR Home”. 70 to 160 characters is enough to sell the click.

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

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

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 at https://www.dar-engineering.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at dar-engineering.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 51 pages on dar-engineering.com and 15 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/about-us has no <title>, so Google invents the link text in results.

/en and /en/Home all use the title “DAR Home”. Search engines can't tell which page to show for a search, so each competes with the others.

/en/about-us has no meta description, so Google writes the search snippet from whatever text it finds.

/en/about-us, /en/company-overview, /en/milestones, /en/our-values, /en/our-work and /en/media-center and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

/en/contact-us and /ar/Home 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 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.

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

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

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

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

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.

dar-engineering.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.

dar-engineering.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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 223 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.

Opening the homepage sets 3 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.