Skip to content
OM · OMR (ر.ع.) · Estimated Dev cost: OMR 20/hr How jurisdiction is detected
Scanned
2026-11-20 18:22 UTC
Worker
🇪🇸 Madrid
Duration
54.00s
Vs prev
—

Audit overview

All categories sit comfortably above the 70 threshold; this is a clean audit.

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

1

Small gains, minimal effort.

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.

safaqat.om fails 2 mail checks: DMARC policy is none — monitoring only, Multiple SPF records found at apex (PERMERROR). 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
Warning: 1

DMARC policy is none — monitoring only

DMARC p=none collects reports but doesn't actually block spoofed mail — phishing emails still reach inboxes.

Security › Email Security
Warning: 2

Multiple SPF records found at apex (PERMERROR)

Informational: a labeled value pair from the audit.

Security › Email Security
Warning: 3

Page weight 1.0 MB exceeds 1 MB target by 39 KB

Page weight over the 1 MB target — image optimization is usually the biggest single lever.

Performance › Page Weight Inventory
Warning: 4

Total JS execution time is 4.4 s -- over the 3.5s budget

Performance issues directly impact user engagement and conversion rates.

Performance › JavaScript Blocking
Warning: 5

Unattributable: 307ms CPU time

Informational: CPU time spent on this resource. Total >1s is a perf budget violation.

Performance › JS Execution Cost
What fixing these means. Your site is in great shape. The remaining improvements are refinements rather than critical fixes. Your LCP of 2.7s exceeds Google's 2.5s 'Good' threshold and the 3 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.
2 security gaps detected — browsers may warn visitors about your site.
Your LCP is 2.7s — fixing the 3 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Business case

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

Return on investment

OMR 130 investment → OMR 1,114/month returns

Investment
OMR 130
6.5 h · 3 findings
Monthly returns
OMR 1,114
OMR 13,366/yr
Payback
0.1 mo
+10181% Y1
Or — fix only the top 3 findings
OMR 130 → 0.1 mo payback · +10181% 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.
OMR 10 — 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

2 barrier(s) likely increasing bounce by ~9%.

Barriers
2
2 warn
Bounce delta
+9pp
added vs baseline
Score
94
A
Speed
1
Trust
0
Usability
0
Content
0
Nav
1
  • Page loads in 2.7s
    Every additional 100ms above 2.5s costs conversions — you're 243ms over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • No skip-to-content link
    Keyboard and screen-reader users must tab through the entire header on every page
    → Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

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

Remediation cost

ر.ع.130 6.5 developer hours at ر.ع.20/hr
Quick wins
ر.ع.10 1 fixes in ~30 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

OMR 938 / month at risk ~OMR 11,254 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Bounce-Rate Cost

OMR 938 /mo

+9.1pp bounce · ~906 lost visitors/mo

CPC: OMR 1.03

Bandwidth Waste

OMR 0.10 /mo

3266.2 MB/mo × 0.031 OMR/GB

  • Optimize transfer: save ~327 KB per page load
    Saves OMR 0.10/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
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

93
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.
100
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.27 s

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

2.74 s

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

184 ms

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

0.007

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

1.62 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.82 s

Desktop

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

348 ms

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

800 ms

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

16 ms

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

0.010

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

667 ms

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

832 ms

Categories

8
Avg score 89.2

How you compare

Where this site stands against peers running the same stack.

Bulma · 516 peers
You 90
·
Avg 76
+14 above average
0 50 100
Security P99SEO P95Performance P94Sustainability P94Accessibility P93Infrastructure P14Compliance P23Content P77

Top 10% of Bulma sites score 94+ on Infrastructure; you're at 83 — closing this gap is the highest-leverage improvement.

Better than 97% of Bulma sites See full Bulma benchmark →
Google Search Console · 4722 peers
You 90
·
Avg 75
+15 above average
0 50 100
Security P96SEO P96Accessibility P92Performance P90Sustainability P88Infrastructure P16Content P81Compliance P22

Top 10% of Google Search Console sites score 95+ on Infrastructure; you're at 83 — closing this gap is the highest-leverage improvement.

Better than 94% of Google Search Console sites See full Google Search Console benchmark →

Technology stack

Bulma, on Firebase, with Fastly CDN

9 technologies detected 3 stack layers 1 with CPE identifier Enterprise

Stack Architecture

Framework
Bulma Google Search Console HSTS HTTP/3 Microsoft 365 Open Graph Priority Hints
Runtime
Firebase
CDN
Fastly

All Detected Technologies (9)

Categories CDN Website https://www.fastly.com Detected by BeaverCheck Evidence x-served-by: cache-toj-leto2350024-TOJ

Firebase is a Google-backed application development software that enables developers to develop iOS, Android and Web apps.

Categories Databases, Development Website https://firebase.google.com Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Framework Website https://bulma.io Detected by BeaverCheck Evidence Found 10 Bulma class patterns in HTML
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=bN8z6LysmVDm_6UwL23l8ks3RdK4nSYDq6JtaPRyY-c

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.

Categories Security Website https://www.rfc-editor.org/rfc/rfc6797#section-6.1 Detected by BeaverCheck

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

Categories Miscellaneous Website https://httpwg.org/ Detected by BeaverCheck
Categories Email Detected by BeaverCheck Evidence MX record: safaqat-om.mail.protection.outlook.com

Open Graph is a protocol that is used to integrate any web page into the social graph.

Categories Miscellaneous Website https://ogp.me Detected by BeaverCheck

Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.

Categories Performance Website https://wicg.github.io/priority-hints/ Detected by BeaverCheck

Observations (2)

No build tool detected

A framework (Bulma) 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.

Complex technology stack detected

9 technologies identified. A complex stack increases maintenance burden and attack surface. Consider whether all components are actively needed.

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%2FSafaQat.om)](https://beavercheck.com/sites/safaqat.om)
<a href="https://beavercheck.com/sites/safaqat.om"><img src="https://beavercheck.com/badge?url=https%3A%2F%2FSafaQat.om" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2FSafaQat.om

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 · 6h total → projected A (93)

Sprint 1: Quick Wins

+2

Highest ROI — low effort, high impact

3 findings 0h → A (92)
  • · Multiple SPF records found at apex (PERMERROR)
  • · Unattributable: 307ms CPU time
  • · DMARC policy is none — monitoring only

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

2 findings 6h → A (93)
  • · Total JS execution time is 4.4 s -- over the 3.5s budget
  • · Page weight 1.0 MB exceeds 1 MB target by 39 KB

Send Feedback