stcsc.sa website review

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

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

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

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

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

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

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

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

Google CDN costs a phone 652 ms of main-thread work and 1.1 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 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

Unpkg costs a phone 86 ms of main-thread work and 575 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 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 28.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to improve site performance, analyze usage, …”. Most of its time is element render delay (12.3 s).

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 140 ms to 95 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 3.8 s to 7.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

3 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 29.5 MB in 196 requests on a phone: images 14.5 MB (97), other files 8.6 MB (45) and media 3.5 MB (1). 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-light.png at 2,230 px wide, shown at 150 px. Resized copies would save about 91 KiB.

1 image (95 KiB) is 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 8.37 g of CO₂e: 1004.7 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”.

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

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

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

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

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

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

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

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

The homepage links to 7 pages on stcsc.sa and 0 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.stcsc.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.

https://www.stcsc.sa/en, https://www.stcsc.sa/en/about, https://www.stcsc.sa/en/solutions, https://www.stcsc.sa/en/industries, https://www.stcsc.sa/en/contact and https://www.stcsc.sa/ar all use the title “Specialized by STC - Critical Communication Solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.stcsc.sa/en/about, https://www.stcsc.sa/en/solutions, https://www.stcsc.sa/en/industries, https://www.stcsc.sa/en/contact and https://www.stcsc.sa/ar use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.stcsc.sa/en/about, whose canonical is https://www.stcsc.sa/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.stcsc.sa/en/about, https://www.stcsc.sa/en/solutions, https://www.stcsc.sa/en/industries, https://www.stcsc.sa/en/contact and https://www.stcsc.sa/ar have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.stcsc.sa/en/about, https://www.stcsc.sa/en/solutions, https://www.stcsc.sa/en/industries, https://www.stcsc.sa/en/contact and https://www.stcsc.sa/ar 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 5 pages linked from your homepage and read each the way a search engine does.

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

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

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

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