Skip to content
Recent Trends
Performance stable →
69
TTFB stable →
924ms
FCP stable →
4.8s
LCP stable →
5.0s
Scanned
2026-10-20 16:43 UTC
Worker
🇸🇬 Singapore
Duration
1.4m
Vs prev
no change

Global Performance

6/6 locations ✓

High global latency — average 648ms across 6 locations, fastest from Amsterdam (229ms), slowest from Santa Clara (978ms). Cloudflare edge cache (DYNAMIC). 4 locations above the 500ms target.

Singapore - Singapore
Full audit
924ms
DNS 9ms · TLS 15ms
Spain - Madrid
333ms
DNS 39ms · TLS 29ms
Netherlands - Amsterdam
229ms
DNS 13ms · TLS 14ms
Brazil - Sao Paulo
852ms
DNS 12ms · TLS 12ms
United Stated - New York
571ms
DNS 9ms · TLS 13ms
United States - Santa Clara
978ms
DNS 123ms · TLS 16ms
CDN: Cloudflare (DYNAMIC) · Avg TTFB: 648ms · Cache: max-age=0

Audit overview

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

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

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

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

1 link(s) with no accessible text

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Accessibility › Link & Button Quality
Critical: 4

No <main> landmark found

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Accessibility › Landmark Structure
Critical: 5

No favicon or icon links detected

Without a favicon, your tab shows a blank icon and bookmarks look unbranded — amateur signal in every browser surface.

Accessibility › Favicon & Branding
What fixing these means. Your site is in great shape. The remaining improvements are refinements rather than critical fixes. 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.
3 accessibility issues exclude 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

$442 investment → $10,772/month returns + USD 157,500 risk avoided

Investment
$442
4.4 h · 5 findings
Monthly returns
$10,772
$129,258/yr
Payback
0.0 mo
+29166% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$375 → 0.0 mo payback · +34369% 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.
$142 — 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

7 barrier(s) likely increasing bounce by ~26%.

Barriers
7
1 crit 6 warn
Bounce delta
+26pp
added vs baseline
Score
72
B
Speed
1
Trust
2
Usability
0
Content
3
Nav
1
  • Page takes 5.0s to load
    Users abandon at ~3s — you're 2.5s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 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
  • No Open Graph tags
    Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
    → Add og:title, og:description, og:image, og:url to the page head
  • No structured data
    No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
    → Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

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

Remediation cost

$442 4.4 developer hours at $100/hr
Quick wins
$142 4 fixes in ~85 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

$6,990 / month at risk ~$83,880 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy found (page links and common paths checked)
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

Bounce-Rate Cost

$6,990 /mo

+26.0pp bounce · ~2,598 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.09 /mo

1075.0 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~108 KB per page load
    Saves $0.09/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

69
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
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.

4.77 s

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

5.02 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.019

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

4.77 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.03 s

Desktop

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
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.

680 ms

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

978 ms

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

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

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

978 ms

Categories

8
Avg score 84.2

How you compare

Where this site stands against peers running the same stack.

WordPress · 1065 peers
You 85
·
Avg 76
+9 above average
0 50 100
Compliance P2Performance P96Sustainability P96Security P95SEO P13Content P17Accessibility P78Infrastructure P65

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

Better than 92% of WordPress sites See full WordPress benchmark →
Google Search Console · 4409 peers
You 85
·
Avg 75
+10 above average
0 50 100
Compliance P2Performance P94Sustainability P94Security P91Accessibility P85Infrastructure P73SEO P33Content P35

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

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

Technology stack

WordPress, with Cloudflare CDN

6 technologies detected 3 stack layers 2 with CPE identifier Complex

Stack Architecture

CMS
WordPress
Framework
Google Search Console HTTP/3 Plesk Tailwind CSS
CDN
Cloudflare

All Detected Technologies (6)

Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.

Categories CDN Website https://www.cloudflare.com Detected by BeaverCheck Evidence Server header in redirect: cloudflare
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories CMS Detected by BeaverCheck · Medium Evidence robots.txt Disallow pattern: /wp-admin/
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=EGpODiO6bJX7ZKSDY-aCWqMZeb7gwMAqNl3BSJ8j3s0

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

Plesk is a web hosting and server data centre automation software with a control panel developed for Linux and Windows-based retail hosting service providers.

Categories Hosting panels Website https://www.plesk.com Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Framework Website https://tailwindcss.com Detected by BeaverCheck Evidence Found 69 unique Tailwind utility classes in HTML

Observations (2)

WordPress detected — review security configuration

WordPress sites benefit from: protecting wp-login.php, disabling XML-RPC if unused, restricting REST API access, and keeping all plugins and themes up to date. Check the Security tab for specific findings.

→ Security

No build tool detected

A framework (Google Search Console) 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.

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

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

Sprint 1: Quick Wins

+6

Highest ROI — low effort, high impact

4 findings 1h → A (91)
  • · No <main> landmark found
  • · HSTS header is missing
  • · 1 link(s) with no accessible text
  • · No favicon or icon links detected

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

1 findings 3h → A (93)
  • · Content-Security-Policy header is missing

Send Feedback