Skip to content
Recent Trends
Performance stable →
82
TTFB degrading ↓
888ms
FCP stable →
2.4s
LCP stable →
4.1s
Scanned
2026-08-22 22:06 UTC
Worker
🇺🇸 New York
Duration
49.00s
Vs prev
Declined by -1

Global Performance

6/6 locations

High global latency — average 820ms across 6 locations, fastest from Santa Clara (134ms), slowest from Amsterdam (1717ms). No CDN detected. Cache-Control disables caching (no-store). 4 locations above the 500ms target.

United Stated - New York
Full audit
467ms
DNS 8ms · TLS 142ms
United States - Santa Clara
134ms
DNS 10ms · TLS 49ms
Singapore - Singapore
867ms
DNS 7ms · TLS 381ms
Spain - Madrid
726ms
DNS 36ms · TLS 328ms
Netherlands - Amsterdam
1717ms
DNS 18ms · TLS 294ms
Brazil - Sao Paulo
1006ms
DNS 223ms · TLS 332ms
CDN: No CDN · Avg TTFB: 820ms · Cache: no-store

Audit overview

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

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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.

rcf-community.com 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

Cookie 'PHPSESSID' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
Critical: 3

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: 4

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

Page weighs 5.9 MB (4.8 MB transferred)

Informational: total page weight (uncompressed) and bytes actually transferred over the wire.

Performance › Page Weight Budget
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 12.9s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. 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.
Your LCP is 12.9s — fixing the 1 performance critical 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

$650 investment → $9,687/month returns + USD 150,000 risk avoided

Investment
$650
6.5 h · 4 findings
Monthly returns
$9,687
$116,238/yr
Payback
0.1 mo
+17783% Y1
Regulatory risk avoided USD 150,000
Or — fix only the top 3 findings
$3500.0 mo payback · +33111% 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.
$50 — 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

8 barrier(s) likely increasing bounce by ~28%.

Barriers
8
1 crit 7 warn
Bounce delta
+28pp
added vs baseline
Score
69
C
Speed
1
Trust
2
Usability
1
Content
3
Nav
1
  • Page takes 12.9s to load
    Users abandon at ~3s — you're 10.4s 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
  • 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
  • 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

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

Remediation cost

$650 6.5 developer hours at $100/hr
Quick wins
$50 2 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

$7,408 / month at risk ~$88,893 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$150,000

ADA Title III
  • No <main> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • No <nav> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000

Bounce-Rate Cost

$7,407 /mo

+27.5pp bounce · ~2,753 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$1.22 /mo

15223.5 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.5 MB per page load
    Saves $1.22/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

73
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
53
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
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.

2.07 s

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

12.86 s

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

17 ms

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

0.001

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

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

12.86 s

Desktop

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

809 ms

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

3.18 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.004

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

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

3.19 s

Categories

8
Avg score 76.9

How you compare

Where this site stands against peers running the same stack.

jQuery · 2078 peers
You 78
·
Avg 74
At average
0 50 100
SEO P8Accessibility P82Compliance P19Security P81Content P21Performance P77Sustainability P34Infrastructure P61

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

Better than 77% of jQuery sites See full jQuery benchmark →
Apache · 506 peers
You 78
·
Avg 73
At average
0 50 100
Accessibility P83Security P81Infrastructure P79SEO P25Compliance P32Performance P68Sustainability P39Content P42

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

Better than 80% of Apache sites See full Apache benchmark →

Technology stack

jQuery 3.6.0, on Apache/PHP, hosted on Apache HTTP Server

5 technologies detected 4 stack layers 3 with CPE identifier Standard

Stack Architecture

Framework
jQuery 3.6.0
Runtime
PHP 8.4.23
Server
Apache
Hosting
Apache HTTP Server GoDaddy

All Detected Technologies (5)

Categories Server Website https://httpd.apache.org Detected by BeaverCheck Evidence Server header: Apache

Apache is a free and open-source cross-platform web server software.

Categories Web servers Website https://httpd.apache.org/ Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Hosting Detected by BeaverCheck · Medium Evidence NS record: ns69.domaincontrol.com

PHP is a general-purpose scripting language used for web development.

Categories Programming languages Website https://php.net Detected by BeaverCheck Evidence x-powered-by: PHP/8.4.23
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.

Categories JavaScript libraries Website https://jquery.com Detected by BeaverCheck Evidence Script URL: https://rcf-community.com/js/jquery-3.6.0.min.js
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (2)

Runtime exposed via X-Powered-By header

The X-Powered-By header reveals 'PHP 8.4.23'. Remove this header in production to reduce information leakage.

→ Security

No build tool detected

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

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 B (87)

Sprint 1: Quick Wins

+8

Highest ROI — low effort, high impact

3 findings 0h → B (86)
  • · Page weighs 5.9 MB (4.8 MB transferred)
  • · Cookie 'PHPSESSID' is missing the Secure flag
  • · HSTS header is missing

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

2 findings 6h → B (87)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback