Mobile 375 × 812

Desktop 1440 × 900

Score: 78 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Major barriers for users with disabilities — up to 15% of your audience.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
Lean and efficient — low environmental impact per visit.
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.
Cookie 'PHPSESSID' is missing the Secure flag
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.
3 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
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/f523bdc7-3f9e-4b86-b9ea-3bcb68ad77cd)<a href="https://beavercheck.com/results/f523bdc7-3f9e-4b86-b9ea-3bcb68ad77cd"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnotes.io" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fnotes.ioThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
8 barrier(s) likely increasing bounce by ~28%.
Page loads in 2.7s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 192ms over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
Page feels frozen for 808ms
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
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
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
3 form field(s) without a label
+6% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
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
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
₺6,750 investment → ₺1,079/month returns + TRY 10,000,000 risk avoided
₺6,750
4h · 5 findings
₺1,079 /mo
~₺12,946 / year
TRY 10,000,000
if kept compliant
₺2,250 — 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.
4.5 developer hours at ₺1500/hr
Based on Turkey rates (₺1500/hr)
Start here for the best return on investment
₺833,336 / month at risk
~₺10,000,036 / year if left unfixed
TRY 10,000,000
+1 more
₺3.02 /mo
1168.6 MB/mo × 2.581 TRY/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 5 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.
946 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.69 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
808 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.225
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.80 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.
4.40 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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
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.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| notes.io/theme/styles/notes.min.css | 13.9 KiB | 165 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| notes.io/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js? | 14400.0 s | 12.6 KiB |
| /beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312... | 86400.0 s | 10.7 KiB |
| notes.io/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js | 2875.0 s | 4.4 KiB |
| notes.io/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js | 2875.0 s | 1.1 KiB |
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Performance issues directly impact user engagement and conversion rates.
head > meta head > meta |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
Notes
I'm Feeling Lucky
Tiktok Video Downloader - SaveTik - (free for limited… body > div.footer | 0.224 |
We'd love to hear from you. Please email us at hello@notes.io body > div.footer > div.socialArea > p | 0.000 |
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.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| notes.io/cdn-cgi/challenge-platform/scripts/jsd/main.js | 862 ms | 816 ms | 17 ms |
| notes.io/ | 491 ms | 84 ms | 3.2 ms |
| www.googletagmanager.com/gtag/js?id=G-H0XVNMGVTV | 469 ms | 351 ms | 86 ms |
| Unattributable | 396 ms | 10 ms | 0.0 ms |
| notes.io/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js | 388 ms | 187 ms | 4.6 ms |
| notes.io/theme/scripts/jquery.min.js | 96 ms | 66 ms | 26 ms |
| /beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312... | 82 ms | 41 ms | 6.5 ms |
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 |
|---|---|
| Script Evaluation | 1.6 s |
| Other | 665 ms |
| Style & Layout | 316 ms |
| Script Parsing & Compilation | 147 ms |
| Rendering | 47 ms |
| Parse HTML & CSS | 43 ms |
| Garbage Collection | 27 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
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-H0XVNMGVTV | 161.1 KiB | 67.9 KiB |
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.
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.programArea > div.notesArea > label > textarea#notesTextAreaID div.programArea > div.notesArea > label > textarea#notesTextAreaID |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
I'm Feeling Lucky body > div.footer > p > a |
Tiktok Video Downloader - SaveTik - (free for limited time) body > div.footer > p > a |
Paste Keyboard iOS - Quick Replies body > div.footer > p > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
What is notes.io? body > div.mainDiv > h1.whatIsNotesIO > img | notes.io/theme/images/whatisnotesio.png | 87 x 15 (5.80) | 148 x 22 (6.73) |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| SharedStorage | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
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.
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.
289 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
679 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
56 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.127
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
767 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.
1.12 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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
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.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| notes.io/theme/styles/notes.min.css | 13.9 KiB | 57 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| notes.io/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js? | 14400.0 s | 14.0 KiB |
| /beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312... | 86400.0 s | 10.7 KiB |
| notes.io/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js | 2875.0 s | 4.4 KiB |
| notes.io/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js | 2875.0 s | 1.1 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
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-H0XVNMGVTV | 161.1 KiB | 67.9 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
Notes
I'm Feeling Lucky
Tiktok Video Downloader - SaveTik - (free for limited… body > div.footer | 0.126 |
We'd love to hear from you. Please email us at hello@notes.io body > div.footer > div.socialArea > p | 0.000 |
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.
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.programArea > div.notesArea > label > textarea#notesTextAreaID div.programArea > div.notesArea > label > textarea#notesTextAreaID |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
I'm Feeling Lucky body > div.footer > p > a |
Tiktok Video Downloader - SaveTik - (free for limited time) body > div.footer > p > a |
Paste Keyboard iOS - Quick Replies body > div.footer > p > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
Notes.io Logo tr > td.barback > a > img.logo | notes.io/theme/images/logo.png | 190 x 45 (4.22) | 201 x 50 (4.02) |
Notes.io slogan tr > td.barback > div.slogan > img | notes.io/theme/images/fastEasyShort.png | 90 x 20 (4.50) | 119 x 22 (5.41) |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| SharedStorage | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
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.
Send Feedback