Mobile 375 × 812

Desktop 1440 × 900

Score: 73 / 100
Based on 8 categories, 0 sections
Room to improve — your 14.6s load time is above Google's 2.5s 'Good' threshold.
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.
Good server performance with room for optimization.
Strong compliance posture across regulations.
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.
'unsafe-inline' found in script source
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 11.4 MB (4.9 MB transferred)
Performance issues directly impact user engagement and conversion rates.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
11 image-only link(s) without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 link(s) with no accessible text
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/b80e83ad-7295-4883-ba8e-e854835ec1ab)<a href="https://beavercheck.com/results/b80e83ad-7295-4883-ba8e-e854835ec1ab"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fg.page" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fg.pageThis 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 14.6s 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 ~30%.
Page takes 14.6s to load
+12% bounceUsers abandon at ~3s — you're 12.1s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 2.5s
+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
1 form field(s) without a label
+2% 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
5 link(s) with generic text ("click here", "read more")
+1% bounceScreen-reader users navigating by link list see no context — and search engines can't infer relevance
Fix: Rewrite with descriptive phrases that identify the destination
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.
€595 investment → €222/month returns + EUR 500,000 risk avoided
€595
7h · 5 findings
€222 /mo
~€2,658 / year
EUR 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.
7.0 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€41,668 / month at risk
~€500,014 / year if left unfixed
€500,000
+2 more
€1.15 /mo
15503.5 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.
4.43 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
14.64 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.49 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.071
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.10 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.
28.34 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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
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.
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.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
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.gstatic.com/awmp/bgc_gbp_bootstrapper.js | 7.9 KiB | |
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 143.9 KiB | 905 ms |
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 1.1 KiB | |
| www.gstatic.com/awmp/glass.css | 534 B | |
| fonts.googleapis.com/icon?family=Material+Icons | 817 B | 152 ms |
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 | |
|---|---|---|---|
div.text-image-wrapper > ion-text-image.image-wrapper > picture > img.Image div.text-image-wrapper > ion-text-image.image-wrapper > picture > img.Image | /marketing-cms/assets/images/ads/79/fd/023a2fb74734b2d856... | 54.1 KiB | 33.3 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
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 |
|---|---|
| g.page/ | 774 ms |
| business.google.com/ | 769 ms |
| www.google.com/business/?ppsrc=GPDA2 | 772 ms |
| business.google.com/en-all/business-profile/?ppsrc=GPDA2 | 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.
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 |
|---|---|---|
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 143.6 KiB | 127.9 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/styles__ltr.css | 41.6 KiB | 39.9 KiB |
| www.gstatic.com/glue/v27_0/glue-material.min.css | 18.1 KiB | 18.1 KiB |
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 |
|---|---|---|
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 299.1 KiB | 195.6 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.6 KiB | 160.6 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.6 KiB | 156.8 KiB |
| www.googletagmanager.com/gtag/js?id=G-V9K47ZG8NP&cx=c>m=4e64f0 | 146.9 KiB | 102.8 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-MZN2RPC3>m=4e64f0 | 127.9 KiB | 59.8 KiB |
| www.googletagmanager.com/gtag/destination?id=G-V9K47ZG8NP&cx=c>m=4e64f0 | 146.9 KiB | 59.6 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-KW3B4LW | 149.5 KiB | 57.9 KiB |
| www.gstatic.com/marketing-cms/reviewed-scripts/youtube/www-widgetapi.js | 63.0 KiB | 49.9 KiB |
| /marketing-cms/reviewed-scripts/glue/v27_0/material-compo... | 54.0 KiB | 36.6 KiB |
| www.gstatic.com/feedback/js/help/prod/service/lazy.min.js | 39.1 KiB | 30.2 KiB |
| /engage/marketing/automation/prod/v1/marketing_analytics_... | 36.9 KiB | 25.0 KiB |
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 |
|---|---|---|---|
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 2.7 s | 2.3 s | 251 ms |
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 1.9 s | 960 ms | 212 ms |
| business.google.com/en-all/business-profile/?ppsrc=GPDA2 | 1.5 s | 33 ms | 3.0 ms |
| Unattributable | 923 ms | 21 ms | 0.0 ms |
| www.googletagmanager.com/gtm.js?id=GTM-KW3B4LW | 529 ms | 434 ms | 66 ms |
| www.googletagmanager.com/gtag/destination?id=G-V9K47ZG8NP&cx=c>m=4e64f0 | 463 ms | 396 ms | 58 ms |
| www.googletagmanager.com/gtm.js?id=GTM-MZN2RPC3>m=4e64f0 | 368 ms | 279 ms | 50 ms |
| /recaptcha/api2/anchor?ar=1&k=6Lfz6Z0rAAAAAOtj-FM77_5TIC1... | 221 ms | 134 ms | 6.5 ms |
| /marketing-cms/reviewed-scripts/glue/v27_0/material-compo... | 169 ms | 98 ms | 70 ms |
| www.googletagmanager.com/gtag/js?id=G-V9K47ZG8NP&cx=c>m=4e64f0 | 97 ms | 34 ms | 63 ms |
| /engage/marketing/automation/prod/v1/marketing_analytics_... | 86 ms | 48 ms | 17 ms |
| www.gstatic.com/awmp/bgc_gbp_bootstrapper.js | 53 ms | 48 ms | 3.8 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 | 4.9 s |
| Style & Layout | 1.5 s |
| Other | 1.3 s |
| Script Parsing & Compilation | 854 ms |
| Parse HTML & CSS | 252 ms |
| Garbage Collection | 250 ms |
| Rendering | 172 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 |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
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 | |
|---|---|
div.glue-header__container > div.glue-header__cta > a.glue-button > img div.glue-header__container > div.glue-header__cta > a.glue-button > img | www.gstatic.com/images/branding/productlogos/googleg/v6/24px.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.
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
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 |
|---|---|
| business.google.com/en-all/business-profile/restaurants/ | Learn more |
| business.google.com/en-all/business-profile/retail/ | Learn more |
| business.google.com/en-all/business-profile/services/ | 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.
1.14 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.59 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
182 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.075
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.53 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.99 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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
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.
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 |
|---|---|---|
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 143.9 KiB | 123 ms |
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 1.1 KiB | |
| www.gstatic.com/awmp/bgc_gbp_bootstrapper.js | 7.9 KiB | |
| www.gstatic.com/awmp/glass.css | 535 B | |
| fonts.googleapis.com/icon?family=Material+Icons | 424 B |
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 | |
|---|---|---|---|
div.text-image-wrapper > ion-text-image.image-wrapper > picture > img.Image div.text-image-wrapper > ion-text-image.image-wrapper > picture > img.Image | /marketing-cms/assets/images/ads/b4/89/acff23ea48fb83dfd8... | 53.0 KiB | 40.9 KiB |
div.text-image-wrapper > ion-text-image.image-wrapper > picture > img.Image div.text-image-wrapper > ion-text-image.image-wrapper > picture > img.Image | /marketing-cms/assets/images/ads/79/fd/023a2fb74734b2d856... | 52.0 KiB | 40.3 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 |
|---|---|
| g.page/ | 222 ms |
| business.google.com/ | 210 ms |
| www.google.com/business/?ppsrc=GPDA2 | 213 ms |
| business.google.com/en-all/business-profile/?ppsrc=GPDA2 | 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 |
|---|---|---|
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 143.6 KiB | 124.6 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/styles__ltr.css | 41.6 KiB | 39.9 KiB |
| www.gstatic.com/glue/v27_0/glue-material.min.css | 18.1 KiB | 18.1 KiB |
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 |
|---|---|---|
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 299.1 KiB | 196.9 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.6 KiB | 160.6 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.6 KiB | 156.5 KiB |
| www.googletagmanager.com/gtag/js?id=G-V9K47ZG8NP&cx=c>m=4e64f0 | 146.9 KiB | 102.8 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-MZN2RPC3>m=4e64f0 | 127.9 KiB | 59.8 KiB |
| www.googletagmanager.com/gtag/destination?id=G-V9K47ZG8NP&cx=c>m=4e64f0 | 146.9 KiB | 59.5 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-KW3B4LW | 149.5 KiB | 57.9 KiB |
| www.gstatic.com/marketing-cms/reviewed-scripts/youtube/www-widgetapi.js | 63.0 KiB | 49.9 KiB |
| /marketing-cms/reviewed-scripts/glue/v27_0/material-compo... | 54.0 KiB | 36.6 KiB |
| www.gstatic.com/feedback/js/help/prod/service/lazy.min.js | 39.1 KiB | 30.2 KiB |
| /engage/marketing/automation/prod/v1/marketing_analytics_... | 36.9 KiB | 25.0 KiB |
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 |
|---|---|---|---|
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 702 ms | 584 ms | 69 ms |
| /marketing-cms/ads/resource/00000188-911b-d8f4-a3ae-bb7b1... | 456 ms | 239 ms | 46 ms |
| business.google.com/en-all/business-profile/?ppsrc=GPDA2 | 377 ms | 9.9 ms | 0.7 ms |
| Unattributable | 271 ms | 8.1 ms | 0.0 ms |
| www.googletagmanager.com/gtm.js?id=GTM-KW3B4LW | 148 ms | 122 ms | 17 ms |
| www.googletagmanager.com/gtag/destination?id=G-V9K47ZG8NP&cx=c>m=4e64f0 | 115 ms | 96 ms | 14 ms |
| www.googletagmanager.com/gtm.js?id=GTM-MZN2RPC3>m=4e64f0 | 71 ms | 57 ms | 13 ms |
| /recaptcha/api2/anchor?ar=1&k=6Lfz6Z0rAAAAAOtj-FM77_5TIC1... | 56 ms | 39 ms | 1.6 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.2 s |
| Other | 378 ms |
| Style & Layout | 374 ms |
| Script Parsing & Compilation | 223 ms |
| Parse HTML & CSS | 62 ms |
| Garbage Collection | 45 ms |
| Rendering | 39 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 |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
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.
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
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 |
|---|---|
| business.google.com/en-all/business-profile/restaurants/ | Learn more |
| business.google.com/en-all/business-profile/retail/ | Learn more |
| business.google.com/en-all/business-profile/services/ | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback