United States · Santa Clara Completed: Apr 22, 2026 22:16 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.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
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.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
6 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.
29 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
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/a9fbd11a-653a-48c2-bdc1-1ec014ca0cfa)<a href="https://beavercheck.com/results/a9fbd11a-653a-48c2-bdc1-1ec014ca0cfa"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fembedgooglemap.net" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fembedgooglemap.netThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 5.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. 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.
7 barrier(s) likely increasing bounce by ~28%.
Page takes 5.0s to load
+12% bounceUsers abandon at ~3s — you're 2.5s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
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
6 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
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.
€540 investment → €3,089/month returns + EUR 20,500,000 risk avoided
€540
6h · 5 findings
€3,089 /mo
~€37,071 / year
EUR 20,500,000
if kept compliant
€90 — 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.0 developer hours at €90/hr
Based on Germany rates (€90/hr)
Start here for the best return on investment
€1,708,333 / month at risk
~€20,500,002 / year if left unfixed
€20,500,000
+3 more
€0.13 /mo
1789.8 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 4 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.
5.01 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.01 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.008
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.01 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.
5.01 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.
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 |
|---|---|---|
| www.embedgooglemap.net/css/bootstrap.min.css | 23.6 KiB | 450 ms |
| www.embedgooglemap.net/css/bootstrap-slider.min.css | 2.5 KiB | 150 ms |
| www.embedgooglemap.net/js/common.js | 3.2 KiB | |
| www.embedgooglemap.net/css/custom.min.css | 1.7 KiB | |
| cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js | 27.9 KiB | 1.3 s |
| cdnjs.cloudflare.com/ajax/libs/bootstrap-slider/11.0.2/bootstrap-slider.min.js | 8.3 KiB | 1.0 s |
| cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.5.3/js/bootstrap.min.js | 13.4 KiB | 1.0 s |
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 |
|---|---|---|
| /maps/api/js/StaticMapService.GetMapImage?1m2&1i1235058&2... | 86400.0 s | 118.8 KiB |
| www.embedgooglemap.net/css/bootstrap.min.css | 0.0 ms | 23.6 KiB |
| www.embedgooglemap.net/js/common.js | 0.0 ms | 3.2 KiB |
| www.embedgooglemap.net/css/bootstrap-slider.min.css | 0.0 ms | 2.5 KiB |
| /maps/api/js?key=AIzaSyCmL18misQw9KdwqGaw3zHkitj8vG6QF2Y&... | 1800.0 s | 2.9 KiB |
| www.embedgooglemap.net/css/custom.min.css | 0.0 ms | 1.7 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 |
|---|---|
| embedgooglemap.net/ | 1.2 s |
| www.embedgooglemap.net/ | 0.0 ms |
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 rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.embedgooglemap.net/css/bootstrap.min.css | 23.4 KiB | 21.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.
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.card-body > div.form-group > div#zoomSlider > div.slider-handle div.card-body > div.form-group > div#zoomSlider > div.slider-handle |
div.col-lg-6 > div.form-group > div#widthSlider > div.slider-handle div.col-lg-6 > div.form-group > div#widthSlider > div.slider-handle |
div.col-lg-6 > div.form-group > div#heightSlider > div.slider-handle div.col-lg-6 > div.form-group > div#heightSlider > div.slider-handle |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
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 |
|---|
Community div.col-lg-12 > div#generate_map > div.mb-3 > a.btn |
Generate Code div.w-100 > div.card > div.card-body > button.btn |
try best ai humanizer div.card > div.col-lg-12 > p > a |
www.embedgooglemap.net div.row > div.col-lg-12 > div.copyright > a |
These are opportunities to improve the legibility of your content.
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.col-lg-6 > div.form-group > div.input-group > input#widthValue div.col-lg-6 > div.form-group > div.input-group > input#widthValue |
div.col-lg-6 > div.form-group > div.input-group > input#heightValue div.col-lg-6 > div.form-group > div.input-group > input#heightValue |
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.col-lg-8 > div.w-100 > div#map-container > iframe#map-canvas div.col-lg-8 > div.w-100 > div#map-container > iframe#map-canvas |
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.
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.
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 |
|---|---|
www.embedgooglemap.net/js/common.js line 323, col 4 | ReferenceError: bindFormListeners is not defined
at HTMLDocument.<anonymous> (https://www.embedgooglemap.net/js/common.js:324:5) |
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.
2.78 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.85 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.002
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.78 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.
2.85 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.
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.
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.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
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 | |
|---|---|---|---|
Embed Google Map div.card > div.card-body > div > div | /maps/api/js/StaticMapService.GetMapImage?1m2&1i1235058&2... | 118.7 KiB | 56.6 KiB |
Click “Get Code” div.card > div.col-lg-12 > ol > li | /maps/vt?pb=!1m5!1m4!1i14!2i4827!3i6153!4i256!2m3!1e0!2sm... | 26.4 KiB | 15.7 KiB |
Preview the map to make sure it looks right div.card > div.col-lg-12 > ol > li | /maps/vt?pb=!1m5!1m4!1i14!2i4825!3i6155!4i256!2m3!1e0!2sm... | 23.4 KiB | 12.7 KiB |
Enter your business name or address div.card > div.col-lg-12 > ol > li | /maps/vt?pb=!1m5!1m4!1i14!2i4827!3i6154!4i256!2m3!1e0!2sm... | 23.3 KiB | 12.6 KiB |
Select the correct place from the suggestions div.card > div.col-lg-12 > ol > li | /maps/vt?pb=!1m5!1m4!1i14!2i4826!3i6155!4i256!2m3!1e0!2sm... | 22.8 KiB | 12.1 KiB |
Adding a map isn’t just decorative. It solves real problems for visitors. div.row > div.card > div.col-lg-12 > p | /maps/vt?pb=!1m5!1m4!1i14!2i4826!3i6154!4i256!2m3!1e0!2sm... | 22.6 KiB | 12.0 KiB |
Adjust map settings like zoom, view type, width, and height div.card > div.col-lg-12 > ol > li | /maps/vt?pb=!1m5!1m4!1i14!2i4826!3i6153!4i256!2m3!1e0!2sm... | 22.5 KiB | 11.8 KiB |
If needed, click directly on the map to fine-tune the location div.card > div.col-lg-12 > ol > li | /maps/vt?pb=!1m5!1m4!1i14!2i4827!3i6155!4i256!2m3!1e0!2sm... | 20.7 KiB | 10.1 KiB |
div.col-lg-6 > div.form-group > div#heightSlider > div.slider-handle div.col-lg-6 > div.form-group > div#heightSlider > div.slider-handle | /maps/vt?pb=!1m5!1m4!1i10!2i301!3i384!4i256!2m1!1e1!3m12!... | 19.7 KiB | 9.1 KiB |
Your address becomes easier to understand visually div.card > div.col-lg-12 > ul > li | /maps/vt?pb=!1m5!1m4!1i14!2i4825!3i6154!4i256!2m3!1e0!2sm... | 17.1 KiB | 6.4 KiB |
Using Embed-GoogleMap.com, the process is straightforward: div.row > div.card > div.col-lg-12 > p | /maps/vt?pb=!1m5!1m4!1i14!2i4824!3i6154!4i256!2m3!1e0!2sm... | 16.7 KiB | 6.0 KiB |
For local businesses in particular, this often reduces confusion and unnecessar… div.row > div.card > div.col-lg-12 > p | /maps/vt?pb=!1m5!1m4!1i14!2i4824!3i6153!4i256!2m3!1e0!2sm... | 16.4 KiB | 5.7 KiB |
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 |
|---|---|---|
| www.embedgooglemap.net/css/bootstrap.min.css | 23.6 KiB | |
| www.embedgooglemap.net/css/custom.min.css | 1.7 KiB | |
| www.embedgooglemap.net/js/common.js | 3.2 KiB | |
| www.embedgooglemap.net/css/bootstrap-slider.min.css | 2.5 KiB | |
| cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js | 28.0 KiB | 349 ms |
| cdnjs.cloudflare.com/ajax/libs/bootstrap-slider/11.0.2/bootstrap-slider.min.js | 8.3 KiB | 289 ms |
| cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.5.3/js/bootstrap.min.js | 13.4 KiB | 289 ms |
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 |
|---|---|
| embedgooglemap.net/ | 722 ms |
| www.embedgooglemap.net/ | 0.0 ms |
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 rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.embedgooglemap.net/css/bootstrap.min.css | 23.4 KiB | 21.8 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.
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.card-body > div.form-group > div#zoomSlider > div.slider-handle div.card-body > div.form-group > div#zoomSlider > div.slider-handle |
div.col-lg-6 > div.form-group > div#widthSlider > div.slider-handle div.col-lg-6 > div.form-group > div#widthSlider > div.slider-handle |
div.col-lg-6 > div.form-group > div#heightSlider > div.slider-handle div.col-lg-6 > div.form-group > div#heightSlider > div.slider-handle |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
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 |
|---|
Community div.col-lg-12 > div#generate_map > div.mb-3 > a.btn |
Generate Code div.w-100 > div.card > div.card-body > button.btn |
try best ai humanizer div.card > div.col-lg-12 > p > a |
www.embedgooglemap.net div.row > div.col-lg-12 > div.copyright > a |
These are opportunities to improve the legibility of your content.
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.col-lg-6 > div.form-group > div.input-group > input#widthValue div.col-lg-6 > div.form-group > div.input-group > input#widthValue |
div.col-lg-6 > div.form-group > div.input-group > input#heightValue div.col-lg-6 > div.form-group > div.input-group > input#heightValue |
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.col-lg-8 > div.w-100 > div#map-container > iframe#map-canvas div.col-lg-8 > div.w-100 > div#map-container > iframe#map-canvas |
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.
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.
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 |
|---|---|
www.embedgooglemap.net/js/common.js line 323, col 4 | ReferenceError: bindFormListeners is not defined
at HTMLDocument.<anonymous> (https://www.embedgooglemap.net/js/common.js:324:5) |
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