saudiprojects.sa website review

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

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).

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

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

YouTube costs a phone 0 ms of main-thread work and 349 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.

1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

2 third-party services load with your homepage (masakenapp.com and YouTube), adding 459 KiB and 1 ms of main-thread time.

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

Your largest element takes 22.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Scroll down”.

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

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

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

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

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

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 16.6 MB in 98 requests on a phone: images 15.0 MB (53), scripts 753 KiB (13) and fonts 566 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example logo-BdGRHzot.png at 4,932 px wide, shown at 99 px. Resized copies would save about 153 KiB.

2 images (192 KiB) 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.

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

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

All page content should be contained by landmarks: 8 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Your title is only 15 characters: “مشاريع السعودية”. 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.

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

Your meta description is 463 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://saudiprojects.sa/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at saudiprojects.sa/robots.txt, the first file search crawlers ask for.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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 incomplete here.

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://saudiprojects.sa/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.

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

Large scripts ship without source maps.

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.

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

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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