Website review, no card needed
sirar.com.sa website review
Visit site (opens in a new tab)Reviewed 3 November 202625 issues · 74 checks
This review found 25 issues worth fixing on sirar.com.sa, 6 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 73 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 125 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 93 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 101 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 88 ms |
| Aug 29, 2026 | 80 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 85 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 92 ms |
| Oct 10, 2026 | 97 ms |
| Oct 17, 2026 | 119 ms |
| Oct 24, 2026 | 114 ms |
| Oct 31, 2026 | 119 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.3 s
Speed
Render-blocking requests
900 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Use efficient cache lifetimes
472 KiB5 files are served with short cache lifetimes, so returning visitors download them again (472 KiB).
Reduce unused CSS
88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 81 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare CDN and Unpkg), adding 9 KiB and 5 ms of main-thread time.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93. That is in Google's “good” band (90 and up).
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 184 ms of it running JavaScript. That is comfortably low.
Server response: 162 ms
162 msYour server sent the HTML in 162 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 73 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Real Time Detection with Industry-Leading Cyber Capabilitie…”.
Time to Interactive: 2.0 s
2.0 sThe page is fully interactive after 2.0 s.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.22 g of CO₂e: 25.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 777 KiB in 17 requests
777 KiBYour homepage downloads 777 KiB in 17 requests on a phone: fonts 472 KiB (5), images 212 KiB (6) and HTML 50 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
17 form fields without a label
17 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 64 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“Real Time Detection with Industry-Leading Cyber C…”, “Swift Actions to Safeguard Your Business Momentum” and “Guaranteed Cybersecurity GRC and Security Awarene…”). One clear main headline is easier for people and search engines.
Meta description is long (307 characters)
Your meta description is 307 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at sirar.com.sa/robots.txt, the first file search crawlers ask for.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
134 internal links, 14 external
The homepage links to 134 pages on sirar.com.sa and 14 external pages.
4 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “sirar by stc | cybersecurity in excellence you can trust”.
Canonical URL set
The canonical URL is https://www.sirar.com.sa/.
Structured data in place
Structured data found: Organization, Service, WebPage and WebSite.
XML sitemap found
Your XML sitemap is reachable at https://www.sirar.com.sa/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.sirar.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.
2 checks passed
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,570 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.sirar.com.sa/report-incident, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page points its canonical at the homepage
https://www.sirar.com.sa/ar declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
3 pages slow to respond
https://www.sirar.com.sa/services/managed-soc, https://www.sirar.com.sa/services/threat-intelligence and https://www.sirar.com.sa/services/penetration-testing took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 65 found) and read each the way a search engine does.
5 checks passed
Every page has a meta description
All 14 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
52 small tap targets
52 of 61 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
A 15-field form
Your longest form asks for 15 fields (13 required). Every extra field lowers completion.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 701 words of copy
The homepage carries about 701 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “Learn More”.
Social proof on the page
Social proof on the homepage: 15 customer or partner logos and 15 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
No consent tool detected
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at sirar.com.sa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Ndc Cloud Arabian Internet & Communications Services Co.Ltd
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on sirar.com.sa, including 8 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.