United Stated · New York Completed: Apr 16, 2026 17:54 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.
Strong compliance posture across regulations.
Rich content metadata — your pages look great everywhere.
Heavier than average — reducing page weight saves energy and bandwidth.
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.
Page weighs 11.2 MB (7.9 MB transferred)
Performance issues directly impact user engagement and conversion rates.
Soft 404: server returns HTTP 200 for non-existent pages
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
158 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
160 HTTP requests — consider bundling or reducing
Performance issues directly impact user engagement and conversion rates.
Cross-Origin-Embedder-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
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/96ab1867-79da-4020-bea5-2119abd13678)<a href="https://beavercheck.com/results/96ab1867-79da-4020-bea5-2119abd13678"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmega.co.nz" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fmega.co.nzThis 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 12.9s exceeds Google's 2.5s 'Good' threshold and the 3 performance issues below directly contribute 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 conversion rate.
5 barrier(s) likely increasing bounce by ~25%.
Page takes 12.9s to load
+12% bounceUsers abandon at ~3s — you're 10.4s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 991ms
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
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
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.
NZD 800 investment → NZD 392/month returns
NZD 800
8h · 5 findings
NZD 392 /mo
~NZD 4,706 / year
No applicable regulations in this jurisdiction
NZD 50 — 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.
8.0 developer hours at NZ$100/hr
Based on New Zealand rates (NZ$100/hr)
Start here for the best return on investment
NZD 3.30 / month at risk
~NZD 40 / year if left unfixed
NZD 3.30 /mo
24781.0 MB/mo × 0.133 NZD/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 2 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.04 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
12.86 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
991 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.003
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.02 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.
12.88 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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| connect.facebook.net/en_US/fbevents.js | 1200.0 s | 96.4 KiB |
| /signals/config/1689110234910227?v=2.9.298&r=stable&domai... | 1200.0 s | 44.3 KiB |
| mega.io/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 0.0 ms | 35.9 KiB |
| www.redditstatic.com/ads/pixel.js | 60.0 s | 19.0 KiB |
| mega.io/wp-includes/blocks/spacer/style.min.css?ver=6.6.2 | 0.0 ms | 1.3 KiB |
| /rp.gif?ts=1776362016928&id=a2_hf9xxr1a4fyr&event=PageVis... | 0.0 ms | 667 B |
| /tr/?id=1689110234910227&ev=PageView&dl=https%3A%2F%2Fmeg... | 0.0 ms | 16 B |
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.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
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.
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.simple-card > div.container > div.img-box > div.img div.simple-card > div.container > div.img-box > div.img | mega.io/wp-content/uploads/MEGA-icon-message-call.png | 7.3 KiB | 6.2 KiB |
div.simple-card > div.container > div.img-box > div.img div.simple-card > div.container > div.img-box > div.img | mega.io/wp-content/uploads/MEGA-icon-lock.png | 7.3 KiB | 6.2 KiB |
div.simple-card > div.container > div.img-box > div.img div.simple-card > div.container > div.img-box > div.img | mega.io/wp-content/uploads/MEGA-icon-cloud.png | 7.0 KiB | 5.9 KiB |
div.simple-card > div.container > div.img-box > div.img div.simple-card > div.container > div.img-box > div.img | mega.io/wp-content/uploads/MEGA-icon-zap.png | 5.7 KiB | 4.6 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Lists the toplevel main thread tasks that executed during page load.
Performance issues directly impact user engagement and conversion rates.
Collection of useful page vitals.
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 |
|---|---|
| mega.co.nz/ | 3.8 s |
| mega.io/ | 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.
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.
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.
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.
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Performance issues directly impact user engagement and conversion rates.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| mega.io/wp-content/themes/megapages/megalib/css/common.css?ver=1772447664 | 10.8 KiB | 2.5 KiB |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| mega.io/wp-content/themes/megapages/megalib/js/megalib.js?ver=1774412887 | 31.8 KiB | 14.3 KiB |
| /wp-content/themes/megapages/megalib/js/megalib-component... | 15.2 KiB | 4.9 KiB |
| mega.io/wp-content/themes/megapages/assets/js/megapages.js?ver=1772447658 | 4.9 KiB | 2.2 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 |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-KQJBQHLY8B&cx=c>m=4e64f0 | 177.4 KiB | 66.7 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-T5VVWV85 | 130.6 KiB | 58.1 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.3 KiB | 33.6 KiB |
| mega.io/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 34.7 KiB | 25.1 KiB |
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.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Cloud storage div.cards > div.simple-card > div.container > h5.heading |
MEGA div.matrix-cards > div.matrix-card > div.box > h5.competitor-name |
Registered users div.right-section > div.data-point > div.content > h5.heading |
These are opportunities to improve keyboard navigation in your application.
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 |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
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 |
|---|---|
| mega.io/about | Learn more |
| mega.io/business | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
To appear in search results, crawlers need access to your app.
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.
3.47 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.32 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
61 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.004
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.55 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.32 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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| mega.io/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 0.0 ms | 86.9 KiB |
| connect.facebook.net/en_US/fbevents.js | 1200.0 s | 96.4 KiB |
| /signals/config/1689110234910227?v=2.9.298&r=stable&domai... | 1200.0 s | 44.3 KiB |
| www.redditstatic.com/ads/pixel.js | 60.0 s | 19.0 KiB |
| mega.io/wp-includes/blocks/spacer/style.min.css?ver=6.6.2 | 0.0 ms | 1.3 KiB |
| /rp.gif?ts=1776362038816&id=a2_hf9xxr1a4fyr&event=PageVis... | 0.0 ms | 667 B |
| /tr/?id=1689110234910227&ev=PageView&dl=https%3A%2F%2Fmeg... | 0.0 ms | 16 B |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
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.
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.simple-card > div.container > div.img-box > div.img div.simple-card > div.container > div.img-box > div.img | mega.io/wp-content/uploads/MEGA-icon-message-call.png | 7.3 KiB | 6.2 KiB |
div.simple-card > div.container > div.img-box > div.img div.simple-card > div.container > div.img-box > div.img | mega.io/wp-content/uploads/MEGA-icon-lock.png | 7.3 KiB | 6.2 KiB |
div.simple-card > div.container > div.img-box > div.img div.simple-card > div.container > div.img-box > div.img | mega.io/wp-content/uploads/MEGA-icon-cloud.png | 7.0 KiB | 5.9 KiB |
div.simple-card > div.container > div.img-box > div.img div.simple-card > div.container > div.img-box > div.img | mega.io/wp-content/uploads/MEGA-icon-zap.png | 5.7 KiB | 4.6 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Lists the toplevel main thread tasks that executed during page load.
Performance issues directly impact user engagement and conversion rates.
Collection of useful page vitals.
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 |
|---|---|
| mega.co.nz/ | 2.8 s |
| mega.io/ | 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.
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.
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.
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Performance issues directly impact user engagement and conversion rates.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| mega.io/wp-content/themes/megapages/megalib/js/megalib.js?ver=1774412887 | 114.1 KiB | 51.3 KiB |
| /wp-content/themes/megapages/megalib/js/megalib-component... | 59.5 KiB | 19.3 KiB |
| mega.io/wp-content/themes/megapages/assets/js/megapages.js?ver=1772447658 | 15.8 KiB | 7.0 KiB |
| mega.io/wp-content/themes/megapages/blocks/animated-hero/view.js?ver=1739304548 | 8.9 KiB | 3.4 KiB |
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 |
|---|---|---|
| mega.io/wp-content/themes/megapages/megalib/css/theme.css?ver=1771295007 | 61.3 KiB | 52.1 KiB |
| mega.io/wp-content/themes/megapages/megalib/css/common.css?ver=1772447664 | 44.8 KiB | 41.6 KiB |
| mega.io/wp-content/themes/megapages/megalib/css/icons.css?ver=1771295007 | 42.5 KiB | 26.4 KiB |
| mega.io/wp-content/themes/megapages/megalib/css/buttons.css?ver=1751434940 | 15.2 KiB | 12.8 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 |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-KQJBQHLY8B&cx=c>m=4e64f0 | 177.4 KiB | 66.2 KiB |
| mega.io/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 85.5 KiB | 62.1 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-T5VVWV85 | 130.6 KiB | 58.1 KiB |
| /wp-content/themes/megapages/megalib/js/megalib-component... | 59.5 KiB | 45.9 KiB |
| mega.io/wp-content/themes/megapages/megalib/js/megalib.js?ver=1774412887 | 114.1 KiB | 43.3 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.3 KiB | 34.0 KiB |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| mega.io/wp-content/themes/megapages/megalib/css/theme.css?ver=1771295007 | 61.6 KiB | 14.0 KiB |
| mega.io/wp-content/themes/megapages/megalib/css/common.css?ver=1772447664 | 45.1 KiB | 10.6 KiB |
| mega.io/wp-content/themes/megapages/megalib/css/icons.css?ver=1771295007 | 42.8 KiB | 5.1 KiB |
| mega.io/wp-content/themes/megapages/megalib/css/buttons.css?ver=1751434940 | 15.5 KiB | 3.5 KiB |
| mega.io/wp-content/themes/megapages/megalib/css/dialogs.css?ver=1751434940 | 6.9 KiB | 2.1 KiB |
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.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Cloud storage div.cards > div.simple-card > div.container > h5.heading |
MEGA div.matrix-cards > div.matrix-card > div.box > h5.competitor-name |
Registered users div.right-section > div.data-point > div.content > h5.heading |
These are opportunities to improve keyboard navigation in your application.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
EN div.upper > div.inner-content > div.right-group > button.text-button |
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 |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
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 |
|---|---|
| mega.io/about | Learn more |
| mega.io/business | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
To appear in search results, crawlers need access to your app.
Send Feedback