United States · Santa Clara Completed: Apr 22, 2026 22:51 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Cross-Origin-Embedder-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
Cross-Origin-Opener-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
Nothing in this quadrant — good news.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/02ef61b7-807c-402d-aa87-c90b89b4fc06)<a href="https://beavercheck.com/results/02ef61b7-807c-402d-aa87-c90b89b4fc06"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbsky.social" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fbsky.socialThis badge auto-updates with your latest scan result.
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.
7 barrier(s) likely increasing bounce by ~25%.
Page takes 6.4s to load
+12% bounceUsers abandon at ~3s — you're 3.9s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
High main-thread blocking time
+2% bouncePage is non-interactive for 446ms after first paint
Fix: Defer third-party scripts and split large bundles
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
1 broken link(s) on the page
+2% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$250 investment → $4,550/month returns + USD 157,500 risk avoided
$250
2h · 5 findings
$4,550 /mo
~$54,602 / year
USD 157,500
if kept compliant
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.
2.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,125 / month at risk
~$157,503 / year if left unfixed
$157,500
+5 more
$0.21 /mo
2646.3 MB/mo × 0.080 USD/GB
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 3 critical issues to capture this value
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
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.94 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.36 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
446 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.
5.42 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.
6.38 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Image of a post by user @theferocity.bsky.social. div.bg-offwhite > div.absolute > picture > img | bsky.social/about/hero-reply-card.webp | 52.7 KiB | 46.8 KiB |
Image of a post by user @mnateshyamalan.bsky.social. div.bg-offwhite > div.absolute > picture > img | bsky.social/about/hero-social-card.webp | 38.3 KiB | 34.8 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| bsky.social/ | 1.0 s |
| bsky.social/about | 0.0 ms |
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-WTBZ3K80ET&cx=c>m=4e64k1 | 156.9 KiB | 66.1 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-KZT6XPW7 | 118.0 KiB | 64.6 KiB |
| bsky.social/about/_next/static/chunks/framework-fa877b8be7542607.js | 58.1 KiB | 27.6 KiB |
| bsky.social/about/_next/static/chunks/pages/_app-e6ca888df01112c8.js | 42.0 KiB | 20.2 KiB |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Other | 938 ms |
| Script Evaluation | 938 ms |
| Style & Layout | 300 ms |
| Script Parsing & Compilation | 186 ms |
| Rendering | 123 ms |
| Parse HTML & CSS | 29 ms |
| Garbage Collection | 17 ms |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
CNBC div > div > div.flex > img.w-auto | bsky.social/about/cnbc-1.svg |
CNBC div > div > div.flex > img.w-auto | bsky.social/about/cnbc-1.svg |
TechCrunch div > div > div.flex > img.w-auto | bsky.social/about/techcrunch-logo-1.svg |
TechCrunch div > div > div.flex > img.w-auto | bsky.social/about/techcrunch-logo-1.svg |
Engadget div > div > div.flex > img.w-auto | bsky.social/about/engadget.svg |
Engadget div > div > div.flex > img.w-auto | bsky.social/about/engadget.svg |
The Verge div > div > div.flex > img.w-auto | bsky.social/about/the-verge.svg |
The Verge div > div > div.flex > img.w-auto | bsky.social/about/the-verge.svg |
The Wall Street Journal div > div > div.flex > img.w-auto | bsky.social/about/the-wall-street-journal-1.svg |
The Wall Street Journal div > div > div.flex > img.w-auto | bsky.social/about/the-wall-street-journal-1.svg |
Image of a post by user @theferocity.bsky.social. div.bg-offwhite > div.absolute > picture > img | bsky.social/about/hero-reply-card.webp |
The Washington Post div > div > div.flex > img.w-auto | bsky.social/about/the-washington-post.svg |
The Washington Post div > div > div.flex > img.w-auto | bsky.social/about/the-washington-post.svg |
Image of a post by user @mnateshyamalan.bsky.social. div.bg-offwhite > div.absolute > picture > img | bsky.social/about/hero-social-card.webp |
Tech Dirt div > div > div.flex > img.w-auto | bsky.social/about/techdirt-logo.svg |
Tech Dirt div > div > div.flex > img.w-auto | bsky.social/about/techdirt-logo.svg |
Associated Press div > div > div.flex > img.w-auto | bsky.social/about/associate-press.svg |
Associated Press div > div > div.flex > img.w-auto | bsky.social/about/associate-press.svg |
NY Times div > div > div.flex > img.w-auto | bsky.social/about/the-new-york-times.svg |
NY Times div > div > div.flex > img.w-auto | bsky.social/about/the-new-york-times.svg |
Mashable div > div > div.flex > img.w-auto | bsky.social/about/mash-logo.svg |
Mashable div > div > div.flex > img.w-auto | bsky.social/about/mash-logo.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
How is Bluesky different? div.flex > div.h-full > div.mt-4 > h5.text-sans-20 |
Take a deeper dive div.flex > div.h-full > div.mt-4 > h5.text-sans-20 |
Martin Kleppmann div.h-full > div.mt-4 > p.mt-4 > a.text-primary-blue |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Your timeline, your choice div.flex > div.w-full > div.max-w-[440px] > h4.font-700 |
How is Bluesky different? div.flex > div.h-full > div.mt-4 > h5.text-sans-20 |
These are opportunities to improve keyboard navigation in your application.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Company
Blog
AT Protocol
App div#__next > div.grid > nav.800:hidden > ul.w-full |
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Company nav.800:hidden > ul.w-full > div.py-8 > li.block |
Blog nav.800:hidden > ul.w-full > div.py-8 > li.block |
AT Protocol nav.800:hidden > ul.w-full > div.py-8 > li.block |
App nav.800:hidden > ul.w-full > div.py-8 > li.block |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| bsky.social/about/faq | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
598 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.63 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
107 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.
1.20 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.63 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Image of a post by user @theferocity.bsky.social. div.bg-offwhite > div.absolute > picture > img | bsky.social/about/hero-reply-card.webp | 52.7 KiB | 45.8 KiB |
Image of a post by user @mnateshyamalan.bsky.social. div.bg-offwhite > div.absolute > picture > img | bsky.social/about/hero-social-card.webp | 38.3 KiB | 28.0 KiB |
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-WTBZ3K80ET&cx=c>m=4e64k1 | 156.9 KiB | 66.6 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-KZT6XPW7 | 118.0 KiB | 64.6 KiB |
| bsky.social/about/_next/static/chunks/framework-fa877b8be7542607.js | 58.0 KiB | 27.8 KiB |
| bsky.social/about/_next/static/chunks/pages/_app-e6ca888df01112c8.js | 42.0 KiB | 20.2 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
CNBC div > div > div.flex > img.w-auto | bsky.social/about/cnbc-1.svg |
CNBC div > div > div.flex > img.w-auto | bsky.social/about/cnbc-1.svg |
TechCrunch div > div > div.flex > img.w-auto | bsky.social/about/techcrunch-logo-1.svg |
TechCrunch div > div > div.flex > img.w-auto | bsky.social/about/techcrunch-logo-1.svg |
Engadget div > div > div.flex > img.w-auto | bsky.social/about/engadget.svg |
Engadget div > div > div.flex > img.w-auto | bsky.social/about/engadget.svg |
The Verge div > div > div.flex > img.w-auto | bsky.social/about/the-verge.svg |
The Verge div > div > div.flex > img.w-auto | bsky.social/about/the-verge.svg |
The Wall Street Journal div > div > div.flex > img.w-auto | bsky.social/about/the-wall-street-journal-1.svg |
The Wall Street Journal div > div > div.flex > img.w-auto | bsky.social/about/the-wall-street-journal-1.svg |
Image of a post by user @mnateshyamalan.bsky.social. div.bg-offwhite > div.absolute > picture > img | bsky.social/about/hero-social-card.webp |
Image of a post by user @theferocity.bsky.social. div.bg-offwhite > div.absolute > picture > img | bsky.social/about/hero-reply-card.webp |
The Washington Post div > div > div.flex > img.w-auto | bsky.social/about/the-washington-post.svg |
The Washington Post div > div > div.flex > img.w-auto | bsky.social/about/the-washington-post.svg |
Tech Dirt div > div > div.flex > img.w-auto | bsky.social/about/techdirt-logo.svg |
Tech Dirt div > div > div.flex > img.w-auto | bsky.social/about/techdirt-logo.svg |
Associated Press div > div > div.flex > img.w-auto | bsky.social/about/associate-press.svg |
Associated Press div > div > div.flex > img.w-auto | bsky.social/about/associate-press.svg |
NY Times div > div > div.flex > img.w-auto | bsky.social/about/the-new-york-times.svg |
NY Times div > div > div.flex > img.w-auto | bsky.social/about/the-new-york-times.svg |
Mashable div > div > div.flex > img.w-auto | bsky.social/about/mash-logo.svg |
Mashable div > div > div.flex > img.w-auto | bsky.social/about/mash-logo.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| bsky.social/ | 493 ms |
| bsky.social/about | 0.0 ms |
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Martin Kleppmann div.h-full > div.mt-4 > p.mt-4 > a.text-primary-blue |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
See project div.grid > a.rounded-[20px] > div.flex > p.font-600 |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Your timeline, your choice div.flex > div.w-full > div.max-w-[440px] > h4.font-700 |
How is Bluesky different? div.flex > div.h-full > div.mt-4 > h5.text-sans-20 |
These are opportunities to improve keyboard navigation in your application.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| bsky.social/about/faq | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback