United States · Santa Clara Completed: Apr 22, 2026 00:32 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 79 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Good foundation, but a few gaps could be exploited.
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.
Rich content metadata — your pages look great everywhere.
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.
Cookie 'connect.sid' is missing the Secure flag
Security gaps expose your site and users to attacks, eroding trust.
1 image-only link(s) without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
1 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 image-in-link without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
4 image(s) missing alt attribute
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/770c9487-42cd-4514-af28-7947c4514d07)<a href="https://beavercheck.com/results/770c9487-42cd-4514-af28-7947c4514d07"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpixlr.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fpixlr.comThis 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.
6 barrier(s) likely increasing bounce by ~20%.
Page loads in 3.6s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 1.1s over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
High main-thread blocking time
+2% bouncePage is non-interactive for 412ms 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 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
5 broken link(s) on the page
+5% 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.
€553 investment → €1,641/month returns + EUR 120,500,000 risk avoided
€553
6h · 5 findings
€1,641 /mo
~€19,692 / year
EUR 120,500,000
if kept compliant
€43 — 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.
6.5 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€10,041,667 / month at risk
~€120,500,004 / year if left unfixed
€120,500,000
+8 more
€0.31 /mo
4186.0 MB/mo × 0.074 EUR/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.
3.19 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.57 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
412 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.
3.19 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.
7.31 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.
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 |
|---|---|---|
| /css2?family=Reddit+Sans:ital,wght@0,200..900;1,200..900&... | 995 B | 833 ms |
| pixlr.com/dist/webstyle.16d097b8c671f06f8726.css | 13.1 KiB |
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 | |
|---|---|---|---|
AI Image Generator Example One div.right > div.box-out > div#ai-image-generator > img | pixlr.com/images/index/ai-image-generator-one.webp | 50.0 KiB | 30.9 KiB |
AI Image Generator Example Three div.right > div.box-out > div#ai-image-generator > img | pixlr.com/images/index/ai-image-generator-three.webp | 45.2 KiB | 26.8 KiB |
AI Generative Expand Example After div.right > div.box-out > div#ai-generative-expand > img | pixlr.com/images/index/generative-expand-back.webp | 42.6 KiB | 23.1 KiB |
AI Generative Expand Example Before div.right > div.box-out > div#ai-generative-expand > img | pixlr.com/images/index/generative-expand-front.webp | 35.7 KiB | 19.4 KiB |
AI Remove Object div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/remove-object-info.webp | 27.8 KiB | 9.1 KiB |
AI Generative Transform div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/generative-transform-info.webp | 25.0 KiB | 6.3 KiB |
AI super scale div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/super-scale-info.webp | 24.5 KiB | 5.8 KiB |
AI Image Generator Example Two div.right > div.box-out > div#ai-image-generator > img | pixlr.com/images/index/ai-image-generator-two.webp | 26.3 KiB | 5.2 KiB |
AI Face Swapper div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/face-swap-info.webp | 23.3 KiB | 4.6 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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 minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Other | 1.1 s |
| Style & Layout | 824 ms |
| Script Evaluation | 574 ms |
| Script Parsing & Compilation | 349 ms |
| Parse HTML & CSS | 100 ms |
| Rendering | 96 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 |
|---|---|---|
| pixlr.com/dist/web.d72bd5e51ddc8cb5d9a4.js | 260.7 KiB | 204.5 KiB |
| accounts.google.com/gsi/client | 95.5 KiB | 67.9 KiB |
| www.googletagmanager.com/gtag/js?id=G-ZTY6N776WH | 165.0 KiB | 66.6 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.
HDR Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Bokeh Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Reflect Mirror Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Reflect Mirror Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Glitch Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Glitch Photo filter div.wrap > div.reels > a.box-shine > img.hero |
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 |
|---|
BEST IN CLASS body > section.design > div.wrap > span.row-label |
Open Photo Grid Maker section.design > div.wrap > div.left > a.button |
Open Product Shot Creator section.design > div.wrap > div.left > a.button |
Test Photo Filters section.design > div.wrap > div.left > a.button |
These are opportunities to improve the legibility of your content.
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.default html.default |
These items highlight common accessibility best practices.
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
accounts.google.com/gsi/client line 85, col 88 | [GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token. |
Not signed in with the identity provider. | |
The Content-Security-Policy directive name 'Strict-Transport-Security:' contains one or more invalid characters. Only ASCII alphanumeric characters or dashes '-' are allowed in directive names. | |
Unrecognized Content-Security-Policy directive 'includeSubDomains'. | |
Unrecognized Content-Security-Policy directive 'preload'. |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
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.
946 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
986 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.
946 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.
986 ms
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.
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 |
|---|---|---|
| /css2?family=Reddit+Sans:ital,wght@0,200..900;1,200..900&... | 995 B | 277 ms |
| pixlr.com/dist/webstyle.16d097b8c671f06f8726.css | 13.2 KiB |
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 | |
|---|---|---|---|
AI Image Generator Example One div.right > div.box-out > div#ai-image-generator > img | pixlr.com/images/index/ai-image-generator-one.webp | 50.0 KiB | 29.8 KiB |
AI Image Generator Example Three div.right > div.box-out > div#ai-image-generator > img | pixlr.com/images/index/ai-image-generator-three.webp | 45.2 KiB | 25.8 KiB |
AI Generative Expand Example After div.right > div.box-out > div#ai-generative-expand > img | pixlr.com/images/index/generative-expand-back.webp | 42.6 KiB | 19.6 KiB |
AI Noise reducation div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/remove-noise-info.webp | 26.0 KiB | 18.7 KiB |
AI Generative Transform div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/generative-transform-info.webp | 25.0 KiB | 17.7 KiB |
AI super scale div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/super-scale-info.webp | 24.5 KiB | 17.2 KiB |
AI Generative Expand Example Before div.right > div.box-out > div#ai-generative-expand > img | pixlr.com/images/index/generative-expand-front.webp | 35.7 KiB | 16.5 KiB |
AI Face Swapper div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/face-swap-info.webp | 23.3 KiB | 16.0 KiB |
AI Image Sharper div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/super-sharp-info.webp | 22.1 KiB | 14.8 KiB |
AI Generative Fill Before div.right > div.box-out > div#ai-generative-fill > img | pixlr.com/images/index/ai-generative-fill-before.webp | 35.8 KiB | 11.4 KiB |
AI Generative Fill After div.right > div.box-out > div#ai-generative-fill > img | pixlr.com/images/index/ai-generative-fill-after.webp | 32.2 KiB | 10.3 KiB |
AI Image Generator Example Two div.right > div.box-out > div#ai-image-generator > img | pixlr.com/images/index/ai-image-generator-two.webp | 26.3 KiB | 9.3 KiB |
AI Remove Background div.wrap > div.reels > a.box-shine > img.hero | pixlr.com/img/tool/remove-background-info.webp | 12.9 KiB | 7.9 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 |
|---|---|---|
| pixlr.com/dist/web.d72bd5e51ddc8cb5d9a4.js | 258.9 KiB | 203.1 KiB |
| accounts.google.com/gsi/client | 95.5 KiB | 70.4 KiB |
| www.googletagmanager.com/gtag/js?id=G-ZTY6N776WH | 165.0 KiB | 66.6 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.
HDR Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Bokeh Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Reflect Mirror Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Reflect Mirror Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Glitch Photo filter div.wrap > div.reels > a.box-shine > img.hero |
Glitch Photo filter div.wrap > div.reels > a.box-shine > img.hero |
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 |
|---|
BEST IN CLASS body > section.design > div.wrap > span.row-label |
Open Photo Grid Maker section.design > div.wrap > div.left > a.button |
Open Product Shot Creator section.design > div.wrap > div.left > a.button |
Test Photo Filters section.design > div.wrap > div.left > a.button |
These are opportunities to improve the legibility of your content.
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.default html.default |
These items highlight common accessibility best practices.
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
accounts.google.com/gsi/client line 85, col 88 | [GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token. |
Failed to load resource: the server responded with a status of 502 () | |
Failed to load resource: the server responded with a status of 502 () | |
Failed to load resource: the server responded with a status of 502 () | |
Failed to load resource: the server responded with a status of 502 () | |
Not signed in with the identity provider. | |
The Content-Security-Policy directive name 'Strict-Transport-Security:' contains one or more invalid characters. Only ASCII alphanumeric characters or dashes '-' are allowed in directive names. | |
Unrecognized Content-Security-Policy directive 'includeSubDomains'. | |
Unrecognized Content-Security-Policy directive 'preload'. |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
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