Skip to content
SA · SAR (ر.س) · Estimated Applicable regulations: KSA PDPL Dev cost: SAR 250/hr How jurisdiction is detected
Scanned
2026-08-19 06:54 UTC
Worker
🇺🇸 Santa Clara
Duration
50.00s
Vs prev

Global Performance

6/6 locations

High global latency — average 641ms across 6 locations, fastest from Amsterdam (381ms), slowest from Singapore (1127ms). No CDN detected. 2 locations above the 500ms target.

United States - Santa Clara
Full audit
387ms
DNS 299ms · TLS 33ms
Spain - Madrid
441ms
DNS 43ms · TLS 135ms
United Stated - New York
493ms
DNS 344ms · TLS 53ms
Netherlands - Amsterdam
381ms
DNS 9ms · TLS 128ms
Brazil - Sao Paulo
1019ms
DNS 558ms · TLS 160ms
Singapore - Singapore
1127ms
DNS 491ms · TLS 215ms
CDN: No CDN · Avg TTFB: 641ms · Cache: private

Audit overview

Compliance needs attention; the rest of the categories are in good shape.

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Screenshots

DESKTOP + MOBILE
Desktop
Desktop screenshot
Mobile
Mobile screenshot

Your mail setup has problems.

itb.com.sa fails 2 mail checks: No DMARC record found, No SPF record found. This is the kind of misconfiguration that sends your mail to spam.

Get a full deliverability audit — €179, 48h →

Top Priorities (5)

Sorted by impact
Critical: 1

Content-Security-Policy header is missing

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Security › Security Headers
Critical: 2

HSTS header is missing

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Security › Security Headers
Critical: 3

No Content-Security-Policy header found

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Security › Content Security Policy
Critical: 4

Page body has only 60 chars of text -- likely empty / placeholder

Security gaps expose your site and users to attacks, eroding trust.

Security › Empty Page Detection
Critical: 5

1 control(s) without accessible label

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Accessibility › Form Accessibility
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.
4 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

SAR 1,938 investment → SAR 28,061/month returns + SAR 5,000,000 risk avoided

Investment
SAR 1,938
7.8 h · 5 findings
Monthly returns
SAR 28,061
SAR 336,736/yr
Payback
0.1 mo
+17280% Y1
Regulatory risk avoided SAR 5,000,000
Or — fix only the top 3 findings
SAR 1,5630.1 mo payback · +21451% Y1
Optimistic scenario assuming the top 3 capture most of the upside. Real-world recovery typically falls between this projection and the full-fix ROI above.
SAR 188 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Conversion barriers

10 barrier(s) likely increasing bounce by ~31%.

Barriers
10
1 crit 9 warn
Bounce delta
+31pp
added vs baseline
Score
63
C
Speed
2
Trust
2
Usability
1
Content
3
Nav
2
  • Page takes 5.6s to load
    Users abandon at ~3s — you're 3.1s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • High main-thread blocking time
    Page is non-interactive for 469ms after first paint
    → Defer third-party scripts and split large bundles
  • No HSTS header
    Returning visitors are briefly exposed to downgrade attacks on first request
    → Set Strict-Transport-Security: max-age=31536000; includeSubDomains
  • No Content-Security-Policy header
    Higher XSS blast radius — one compromised script can exfiltrate the checkout form
    → Ship a reporting-only CSP first, then enforce once violations are clean
  • 1 form field(s) without a label
    Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
    → Associate every input with a visible <label for="…">; add autocomplete attributes

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Remediation cost

ر.س1,938 7.8 developer hours at ر.س250/hr
Quick wins
ر.س188 2 fixes in ~45 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Team composition

Multiplier applied to dev hours to reflect QA, design, and PM overhead. Use Dev only for solo work; Full team for projects with formal review processes.

ر.س /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Warning:Cost of inaction

SAR 18,716 / month at risk ~SAR 224,594 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

SAR 5,000,000

KSA PDPL
  • 1 non-essential cookie(s) set without consent banner
    KSA PDPL: SAR 10,000 – SAR 5,000,000

Bounce-Rate Cost

SAR 18,716 /mo

+31.2pp bounce · ~3,119 lost visitors/mo

CPC: SAR 6.00

Bandwidth Waste

SAR 0.55 /mo

1871.5 MB/mo × 0.296 SAR/GB

  • Optimize transfer: save ~187 KB per page load
    Saves SAR 0.55/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Lighthouse

Mobile

58
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
54
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

4.02 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.56 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

469 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.13 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.80 s

Desktop

79
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
54
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.80 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.27 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.026

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.80 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.27 s

Categories

8
Avg score 77.9

How you compare

Where this site stands against peers running the same stack.

Knockout.js · 7 peers
You 79
·
Avg 76
At average
0 50 100
Better than 71% of Knockout.js sites See full Knockout.js benchmark →
Webpack · 1041 peers
You 79
·
Avg 74
At average
0 50 100
Compliance P5Infrastructure P6Accessibility P93Content P10SEO P11Performance P87Security P84Sustainability P82

Top 10% of Webpack sites score 86+ on Compliance; you're at 66 — closing this gap is the highest-leverage improvement.

Better than 83% of Webpack sites See full Webpack benchmark →

Technology stack

Knockout.js 3.5.1

2 technologies detected 1 stack layers Minimal

Stack Architecture

Framework
Knockout.js 3.5.1 Webpack

All Detected Technologies (2)

Knockout.js is basically a library written in JavaScript, based on MVVM pattern that helps developers build rich and responsive websites.

Categories JavaScript frameworks Website https://knockoutjs.com Detected by BeaverCheck

Webpack is an open-source JavaScript module bundler.

Categories Miscellaneous Website https://webpack.js.org/ Detected by BeaverCheck

Observations (2)

No build tool detected

A framework (Knockout.js) was detected but no bundler was identified. The build tool may not be detectable from output patterns, or the site may use the framework's built-in bundler.

Minimal technology footprint

Only 2 technologies detected. This suggests a simple setup with minimal dependencies — excellent for performance and security.

Show your score

Drop this badge on your README, marketing site, or status page. It auto-updates every time the audit re-runs and links back to this report.

BeaverCheck badge

This badge auto-updates with your latest scan result.

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fportal.itb.com.sa)](https://beavercheck.com/sites/itb.com.sa)
<a href="https://beavercheck.com/sites/itb.com.sa"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fportal.itb.com.sa" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fportal.itb.com.sa

Export & share

Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.

Share

Copies markdown to clipboard

Export
Download Markdown Report Download JSON

Fix Plan

Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.

Three-week fix plan

2 sprints · 8h total → projected B (86)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

2 findings 1h → B (84)
  • · HSTS header is missing
  • · Page body has only 60 chars of text -- likely empty / placeholder

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

3 findings 7h → B (86)
  • · 1 control(s) without accessible label
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback