nour.com.sa website review

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

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

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

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

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

4 third-party services load with your homepage (jQuery CDN, JSDelivr CDN and Cloudflare CDN and others), adding 308 KiB and 38 ms of main-thread time.

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

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.

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

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

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

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

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

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

carousel-1.jpg weighs 547 KiB. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example carousel-1.jpg at 1,915 px wide, shown at 390 px. Resized copies would save about 1.0 MB.

Your homepage downloads 2.7 MB in 54 requests on a phone: images 2.2 MB (32), fonts 233 KiB (3) and stylesheets 192 KiB (8). Under 2 MB keeps phones on slow connections fast.

6 images (2.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.

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

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h2 → h5), 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.

Your title is only 19 characters: “Nour Communications”. 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.

There are 3 <h1> headlines (“We Have Years of Excellence in Service Delivery”, “We Are Energizing Future with Innovation” and “We Are Building Tomorrow Seamless Engineering”). 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.

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://nour.com.sa/sitemap.xml, so Google discovers your pages only by following links.

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

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

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.

The homepage links to 33 pages on nour.com.sa and 3 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://nour.com.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.

Your homepage links to https://nour.com.sa/telecom-capability.html, which answers with an error. Visitors hit a dead end and search engines drop it.

https://nour.com.sa/our-services.html, https://nour.com.sa/corporate-overview.html, https://nour.com.sa/ceo-message.html, https://nour.com.sa/our-values.html, https://nour.com.sa/qhse.html and https://nour.com.sa/telecom-capabilities.html and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

28 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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

Social proof on the homepage: 29 testimonial or review blocks. 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.

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.

The homepage carries about 259 words of visible text.

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