saif-zone.com website review

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

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

About 1.7 MB of JavaScript is downloaded but never used on this page.

6 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.4 MB and 1.4 s of main-thread time.

57 files are served with short cache lifetimes, so returning visitors download them again (1,014 KiB).

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

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

6 images could be 239 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.

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

Polyfills for old browsers add 23 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 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

The layout shifts by 1.789 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

17 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-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.9 MB in 96 requests on a phone: scripts 2.6 MB (27), images 1.5 MB (49) and stylesheets 1.0 MB (5). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example group-photo.jpg at 1,965 px wide, shown at 120 px. Resized copies would save about 1.0 MB.

8 images (1.3 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 (1.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 1.67 g of CO₂e: 200.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

There are 6 <h1> headlines (“Where Businesses”, “Connect & Grow” and “SAIF BUSINESS”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 34 pages on saif-zone.com and 5 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 https://www.saif-zone.com/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.

/, https://www.saif-zone.com/en, https://www.saif-zone.com/en/landing-page/e-services, https://www.saif-zone.com/en/about-us, https://www.saif-zone.com/en/freezone and https://www.saif-zone.com/en/business-set-up and 10 others all use the title “Sharjah Airport International Free Zone Authority”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.saif-zone.com/en/landing-page/e-services, https://www.saif-zone.com/en/regulations, https://www.saif-zone.com/en/landing-page/saif-business-support-packages, https://www.saif-zone.com/en/landing-page/financing-solutions-with-edb, https://www.saif-zone.com/en/media/news/saif-zone-participates-in-tamel-eng and https://www.saif-zone.com/en/media/news/saif-zone-explores-partnerships-in-hong-kong-eng and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.saif-zone.com/en and https://www.saif-zone.com/ar use the same meta description. A description written for each page earns more clicks.

https://www.saif-zone.com/en/media has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.saif-zone.com/ar has 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 28 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

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 717 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.