Skip to content
Scanned
2026-09-22 02:52 UTC
Worker
🇪🇸 Madrid
Duration
39.00s
Vs prev

Global Performance

6/6 locations

Strong global performance — average 153ms across 6 locations, fastest from New York (44ms), slowest from Singapore (283ms). GitHub Pages edge cache (MISS).

Spain - Madrid
Full audit
182ms
DNS 31ms · TLS 3ms
Netherlands - Amsterdam
143ms
DNS 4ms · TLS 12ms
United States - Santa Clara
115ms
DNS 11ms · TLS 8ms
United Stated - New York
44ms
DNS 6ms · TLS 5ms
Singapore - Singapore
283ms
DNS 7ms · TLS 6ms
Brazil - Sao Paulo
150ms
DNS 9ms · TLS 8ms
CDN: GitHub Pages (MISS) · Avg TTFB: 153ms · Cache: max-age=600

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.

sardar-ak-008.github.io 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
Warning: 2

6 third-party resources (70% of weight)

Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.

Performance › Page Weight Inventory
Warning: 3

60 inline style attribute(s) detected

Inline style attributes force `style-src 'unsafe-inline'` in any CSP -- effectively negating CSP's XSS-mitigation value for stylesheets.

Security › CSP Inline-Style Readiness
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. Your LCP of 2.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 2.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

$825 investment → $6,897/month returns + USD 157,500 risk avoided

Investment
$825
8.3 h · 4 findings
Monthly returns
$6,897
$82,766/yr
Payback
0.1 mo
+9932% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$8000.1 mo payback · +10246% 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.
$25 — 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 ~23%.

Barriers
6
1 crit 5 warn
Bounce delta
+23pp
added vs baseline
Score
75
B
Speed
1
Trust
1
Usability
1
Content
2
Nav
1
  • 3 broken link(s) on the page
    Clicks land on 404s — trust drops and the session often ends
    → Fix or remove the broken destinations surfaced on the Content tab
  • Page loads in 2.9s
    Every additional 100ms above 2.5s costs conversions — you're 440ms over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • 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
  • Layout shifts during page load
    Content movement causes mis-clicks on CTAs and form fields
    → Add width/height to images; reserve space for late-loading embeds
  • 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

$825 8.3 developer hours at $100/hr
Quick wins
$25 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

$6,069 / month at risk ~$72,822 / 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
  • Privacy Policy not detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Heading level skipped: H2 → H4 (missing H3)
    ADA Title III: USD 25,000 – USD 150,000

Bounce-Rate Cost

$6,068 /mo

+22.6pp bounce · ~2,256 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.02 /mo

264.0 MB/mo × 0.080 USD/GB

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

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

2.94 s

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

2.94 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.196

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

3.15 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.94 s

Desktop

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

808 ms

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

808 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.238

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

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

808 ms

Categories

8
Avg score 82.4

How you compare

Where this site stands against peers running the same stack.

Google Font API · 1268 peers
You 82
·
Avg 75
+7 above average
0 50 100
Compliance P7Sustainability P91Performance P88Accessibility P88Content P23Security P75Infrastructure P74SEO P43

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

Better than 87% of Google Font API sites See full Google Font API benchmark →
HSTS · 3095 peers
You 82
·
Avg 77
At average
0 50 100
Compliance P8Sustainability P82Accessibility P78Performance P75Infrastructure P71Content P30Security P66SEO P51

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

Better than 77% of HSTS sites See full HSTS benchmark →

Technology stack

Google Font API, hosted on GitHub Pages, with Fastly CDN

5 technologies detected 3 stack layers 2 with CPE identifier Standard

Stack Architecture

Framework
Google Font API HSTS Varnish
CDN
Fastly
Hosting
GitHub Pages

All Detected Technologies (5)

Fastly is a cloud computing services provider. Fastly's cloud platform provides a content delivery network, Internet security services, load balancing, and video & streaming services.

Categories CDN Website https://www.fastly.com Detected by BeaverCheck Evidence x-served-by: cache-toj-leto2350044-TOJ
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

GitHub Pages is a static site hosting service.

Categories PaaS Website https://pages.github.com/ Detected by BeaverCheck Evidence Domain: .github.io, Header: x-github-request-id

Google Font API is a web service that supports open-source font files that can be used on your web designs.

Categories Font scripts Website https://fonts.google.com/ Detected by BeaverCheck

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

Varnish is a reverse caching proxy.

Categories Caching Website https://www.varnish-cache.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (2)

Hosted on GitHub Pages

GitHub Pages provides free static hosting with automatic HTTPS. Limitations: no server-side code, 1GB site size limit, 100GB/month bandwidth.

No build tool detected

A framework (Google Font API) 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%2Fsardar-ak-008.github.io%2FPortfolio-Sardar-AK%2F)](https://beavercheck.com/sites/sardar-ak-008.github.io)
<a href="https://beavercheck.com/sites/sardar-ak-008.github.io"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsardar-ak-008.github.io%2FPortfolio-Sardar-AK%2F" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fsardar-ak-008.github.io%2FPortfolio-Sardar-AK%2F

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

Sprint 1: Quick Wins

+2

Highest ROI — low effort, high impact

2 findings 0h → B (84)
  • · 6 third-party resources (70% of weight)
  • · Cross-Origin-Opener-Policy header is missing

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

3 findings 8h → B (88)
  • · Content-Security-Policy header is missing
  • · Cross-Origin-Embedder-Policy header is missing
  • · 60 inline style attribute(s) detected

Send Feedback