Global Performance
5/5 locations ✓High global latency — average 1922ms across 5 locations, fastest from Amsterdam (964ms), slowest from Santa Clara (4842ms). No CDN detected. Cache-Control header is missing. 5 locations above the 500ms target.
Audit overview
Compliance needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
3High impact, low effort — start here.
Strategic
2High impact, requires investment.
Easy Improvements
0Small gains, minimal effort.
Nothing in this quadrant — good news.
Deprioritize
0Low impact, high effort — do last.
Nothing in this quadrant — good news.
Screenshots
Top Priorities (5)
No H1 heading found
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
1 software version(s) disclosed in HTML: WordPress 7.0
Each disclosed version enables direct CVE lookup -- attacker reads the version, searches the CVE database, targets the site with a tested exploit.
2 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
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.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
BYN 440 investment → BYN 16,180/month returns
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 ~19%.
- 5 broken link(s) on the pageClicks land on 404s — trust drops and the session often ends→ Fix or remove the broken destinations surfaced on the Content tab
- No Content-Security-Policy headerHigher 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 tagsLinks 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 dataNo 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, …)
- Thin contentUnder 300 words — visitors bounce looking for substance, search engines rank competitors first→ Add a substantive FAQ, product detail, or case-study section
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
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.
Rates reflect fully-loaded developer cost including overhead
Warning:Cost of inaction
Bounce-Rate Cost
BYN 16,180 /mo
+18.6pp bounce · ~1,865 lost visitors/mo
CPC: BYN 8.68
Bandwidth Waste
BYN 0.06 /mo
241.9 MB/mo × 0.258 BYN/GB
- Optimize transfer: save ~24 KB per page loadSaves BYN 0.06/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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
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
Your data stays in your browser — nothing is sent to our servers
Lighthouse
Mobile
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
865 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.00 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.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
28.86 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.
1.00 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
212 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
252 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.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
605 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.
252 ms
Categories
8Performance
2 render-blocking <script src> tag(s) without async/defer
Security
1 software version(s) disclosed in HTML: WordPress 7.0
Accessibility
No H1 heading found
SEO
All checks pass
Infrastructure
All checks pass
Compliance
All checks pass
Content
All checks pass
Sustainability
All checks pass
How you compare
Where this site stands against peers running the same stack.
Top 10% of WordPress sites score 86+ on Compliance; you're at 63 — closing this gap is the highest-leverage improvement.
Top 10% of Bulma sites score 86+ on Compliance; you're at 63 — closing this gap is the highest-leverage improvement.
Technology stack
WordPress 7.0, on OpenResty/PHP, with Nginx CDN
Stack Architecture
WordPress 7.0
Bulma HSTS 
MySQL 
RSS Twitter Emoji (Twemoji) 
PHP 8.3.31
OpenResty 
Nginx All Detected Technologies (9)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
OpenResty is a web platform based on nginx which can run Lua scripts using its LuaJIT engine.
PHP is a general-purpose scripting language used for web development.
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
MySQL is an open-source relational database management system.
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.
Twitter Emoji is a set of open-source emoticons and emojis for Twitter, TweetDeck, and also for Android and iOS versions of the application.
Observations (4)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'PHP 8.3.31'. Remove this header in production to reduce information leakage.
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.
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.
This badge auto-updates with your latest scan result.
[](https://beavercheck.com/results/a54344e4-32c6-4d9b-87cb-0c8c3732f49e)<a href="https://beavercheck.com/results/a54344e4-32c6-4d9b-87cb-0c8c3732f49e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Finco.by" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Finco.byExport & share
Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.
Copies markdown to clipboard
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 (90)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · No H1 heading found
- · 1 software version(s) disclosed in HTML: WordPress 7.0
- · Cross-Origin-Opener-Policy header is missing
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing
- · 2 render-blocking <script src> tag(s) without async/defer