Skip to content
Recent Trends
Performance degrading ↓
79
TTFB improving ↑
532ms
FCP stable →
1.7s
LCP degrading ↓
5.4s
Scanned
2026-04-04 18:39 UTC
Worker
🇧🇷 Sao Paulo
Duration
1.4m
Vs prev

Global Performance

5/5 locations

High global latency — average 1132ms across 5 locations, fastest from Amsterdam (179ms), slowest from Singapore (2840ms). No CDN detected. 3 locations above the 500ms target.

Brazil - Sao Paulo
Full audit
1268ms
DNS 141ms · TLS 417ms
Netherlands - Amsterdam
179ms
DNS 26ms · TLS 32ms
United Stated - Santa Clara
885ms
DNS 75ms · TLS 290ms
United Stated - New York
488ms
DNS 11ms · TLS 157ms
Singapore - Singapore
2840ms
DNS 1916ms · TLS 329ms
CDN: No CDN · Avg TTFB: 1132ms · Cache: max-age=0, private, must-revalidate

Audit overview

Accessibility and Content need attention; the other categories are in good shape.

Fix Priority Matrix

5 findings

Quick Wins

1

High impact, low effort — start here.

Strategic

4

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

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

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

Cross-Origin-Embedder-Policy header is missing

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Security › Security Headers
Warning: 5

Cross-Origin-Opener-Policy header is missing

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Security › Security Headers
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

€660 investment → €4,402/month returns + EUR 20,500,000 risk avoided

Investment
€660
8.3 h · 5 findings
Monthly returns
€4.402
€52.825/yr
Payback
0.1 mo
+7904% Y1
Regulatory risk avoided EUR 20.500.000
Or — fix only the top 3 findings
€5600.1 mo payback · +9333% 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.
€20 — 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

6 barrier(s) likely increasing bounce by ~20%.

Barriers
6
1 crit 5 warn
Bounce delta
+20pp
added vs baseline
Score
75
B
Speed
0
Trust
1
Usability
1
Content
2
Nav
2
  • 3 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 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, …)
  • 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

€660 8.3 developer hours at €80/hr
Quick wins
€20 1 fixes in ~15 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

€4.402 / month at risk ~€52.825 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€20.500.000

RGPDEAA
  • No privacy policy link detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • Privacy Policy not detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • 6 of 8 <nav> elements are unlabeled
    EAA: EUR 1.000 – EUR 500.000

Bounce-Rate Cost

€4.402 /mo

+20.0pp bounce · ~2,001 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0,24 /mo

3193.7 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~319 KB per page load
    Saves €0,24/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 3 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

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

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

2.05 s

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

34 ms

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

0.052

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

3.60 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.83 s

Desktop

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

851 ms

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

851 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.038

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

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

851 ms

Categories

8
Avg score 75.2

How you compare

Where this site stands against peers running the same stack.

HSTS · 2620 peers
You 76
·
Avg 75
At average
0 50 100
Content P2Infrastructure P18Compliance P22Performance P74Sustainability P70SEO P39Security P59Accessibility P42

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

Better than 55% of HSTS sites See full HSTS benchmark →
jQuery · 1929 peers
You 76
·
Avg 73
At average
0 50 100
Content P3Compliance P13Performance P83SEO P19Security P81Sustainability P77Infrastructure P27Accessibility P48

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

Better than 69% of jQuery sites See full jQuery benchmark →

Technology stack

HSTS, with Nginx CDN

4 technologies detected 2 stack layers 2 with CPE identifier Standard

Stack Architecture

Framework
HSTS RSS jQuery 2.2.4
CDN
Nginx

All Detected Technologies (4)

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

Categories Web servers, Reverse proxies Website https://nginx.org/en Detected by BeaverCheck Evidence Server header: nginx
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

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

RSS is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format.

Categories Miscellaneous Website https://www.rssboard.org/rss-specification Detected by BeaverCheck

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
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (2)

No build tool detected

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

jQuery version may be outdated

Detected jQuery 2.2.4. The current major version is 3. Consider updating for security patches and new features.

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

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 (83)

Sprint 1: Quick Wins

+1

Highest ROI — low effort, high impact

1 findings 0h → C (77)
  • · Cross-Origin-Opener-Policy header is missing

Sprint 2: Core Fixes

+6

Medium effort, high structural impact

4 findings 8h → B (83)
  • · 3 control(s) without accessible label
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback