Audit overview
3 categories need attention: Performance, and 2 others.
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)
Page weighs 27.6 MB (10.6 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
12 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.
398 third-party resources (100% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
399 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
SGD 495 investment → SGD 9,898/month returns + SGD 1,000,000 risk avoided
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 ~28%.
- Page takes 24.5s to loadUsers abandon at ~3s — you're 22.0s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 4.0sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 3 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
- 12 link(s) with generic text ("click here", "read more")Screen-reader users navigating by link list see no context — and search engines can't infer relevance→ Rewrite with descriptive phrases that identify the destination
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
Compliance Risk
SGD 1,000,000
- No privacy policy link detectedPDPA: SGD 10,000 – SGD 1,000,000
- Trackers detected but no cookie policy foundPDPA: SGD 10,000 – SGD 1,000,000
- Trackers detected but no privacy policy foundPDPA: SGD 10,000 – SGD 1,000,000
Bounce-Rate Cost
SGD 9,895 /mo
+28.3pp bounce · ~2,827 lost visitors/mo
CPC: SGD 3.50
Bandwidth Waste
SGD 3.62 /mo
33479.5 MB/mo × 0.108 SGD/GB
- Optimize transfer: save ~3.3 MB per page loadSaves SGD 3.62/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 2 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.
8.97 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
24.47 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.95 s
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.
10.30 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.
41.45 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.37 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.66 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
346 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.006
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.83 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.
8.51 s
Categories
8Performance
Page weighs 27.6 MB (10.6 MB transferred)
Security
Cross-Origin-Embedder-Policy header is missing
Accessibility
12 link(s) with no accessible text
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 Amazon Route 53 sites score 82+ on Sustainability; you're at 50 — closing this gap is the highest-leverage improvement.
Top 10% of Font Awesome sites score 90+ on Sustainability; you're at 50 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, hosted on AWS, with AWS CloudFront CDN
Stack Architecture
Google Tag Manager 
New Relic 
PostHog 
Font Awesome 
Google Font API Google Play app Google Search Console HSTS Native app preferred 
Open Graph 
Permutive 
React 
React Router 7.13.0
Tailwind CSS 
AWS CloudFront Amazon CloudFront 
AWS Amazon Web Services All Detected Technologies (19)
Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Font Awesome is a font and icon toolkit based on CSS and Less.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Permutive is a publisher-focused data management platform.
React is an open-source JavaScript library for building user interfaces or UI components.
React Router provides declarative routing for React.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
New Relic is a SaaS offering that focuses on performance and availability monitoring.
PostHog is the open-source, all-in-one product analytics platform.
Observations (2)
No build tool detected
A framework (Amazon Route 53) 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
19 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/917553b1-c8d8-4dfc-a334-a5f9f66cdbc1)<a href="https://beavercheck.com/results/917553b1-c8d8-4dfc-a334-a5f9f66cdbc1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbusinesstimes.com.sg" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fbusinesstimes.com.sgExport & 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 · 6h total → projected B (81)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Page weighs 27.6 MB (10.6 MB transferred)
- · 12 link(s) with no accessible text
- · 398 third-party resources (100% of weight)
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing
- · 399 HTTP requests — consider bundling or reducing