Skip to content
https://mega.nz

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

72

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
mega.io/wp-includes/js/jquery/jquery.min.js?ver=3.7.10.0 ms35.9 KiB
mega.io/wp-includes/blocks/spacer/style.min.css?ver=6.6.20.0 ms1.3 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst 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.png7.3 KiB6.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.png7.3 KiB6.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.png7.0 KiB5.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.png5.7 KiB4.6 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:89.5590009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:1878.8929990234376 label:Resource load delay subpart:resourceLoadDelay] map[duration:4931.416 label:Resource load duration subpart:resourceLoadDuration] map[duration:58.922 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-VIDEO
nodeLabel: section.animated-hero > div.scroll-region > div.media > video
path: 1,HTML,1,BODY,2,MAIN,0,SECTION,0,DIV,0,DIV,1,VIDEO
selector: section.animated-hero > div.scroll-region > div.media > video
snippet: <video autoplay="" muted="" playsinline="" src="https://mega.io/wp-content/themes/megapages/assets/animated-hero/video/xl.…">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO
nodeLabel: section.animated-hero > div.scroll-region > div.media > video
path: 1,HTML,1,BODY,2,MAIN,0,SECTION,0,DIV,0,DIV,1,VIDEO
selector: section.animated-hero > div.scroll-region > div.media > video
snippet: <video autoplay="" muted="" playsinline="" src="https://mega.io/wp-content/themes/megapages/assets/animated-hero/video/xl.…">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
mega.io/wp-content/themes/megapages/megalib/js/megalib.js?ver=177441288732.0 KiB
mega.io/wp-includes/js/jquery/jquery.min.js?ver=3.7.135.9 KiB
mega.io/wp-content/themes/megapages/assets/css/dialogs.css?ver=17393045481.3 KiB
mega.io/wp-content/themes/megapages/megalib/css/blocks.css?ver=16741048821.1 KiB
mega.io/wp-content/themes/megapages/megalib/css/dialogs.css?ver=17514349402.0 KiB
/wp-content/themes/megapages/megalib/css/templates/footer...1.5 KiB
/wp-content/themes/megapages/megalib/css/templates/header...2.2 KiB
mega.io/wp-content/themes/megapages/megalib/css/wp.css?ver=1674104882691 B
/wp-content/themes/megapages/blocks/home-social-proof/blo...1.2 KiB
mega.io/wp-includes/blocks/spacer/style.min.css?ver=6.6.21.3 KiB
/wp-content/themes/megapages/blocks/full-width-banner/blo...1.5 KiB
/wp-content/themes/megapages/blocks/ft-alternating-coming...1.5 KiB
/wp-content/themes/megapages/blocks/pricing-page/competit...601 B
/wp-content/themes/megapages/blocks/pricing-page/competit...853 B
/wp-content/themes/megapages/blocks/feature-alternating/b...1.7 KiB
mega.io/wp-content/themes/megapages/blocks/single-slice/block.css?ver=1751434886797 B
/wp-content/themes/megapages/blocks/ft-simple-card-column...875 B
mega.io/wp-content/themes/megapages/blocks/simple-card/block.css?ver=1691036107690 B
mega.io/wp-content/themes/megapages/assets/css/common.css?ver=17604884261.2 KiB
/wp-content/themes/megapages/blocks/animated-hero/block.c...1.1 KiB
mega.io/wp-content/themes/megapages/megalib/css/common.css?ver=177244766410.8 KiB
mega.io/wp-content/themes/megapages/megalib/css/buttons.css?ver=17514349403.2 KiB
mega.io/wp-content/themes/megapages/megalib/css/icons.css?ver=17712950075.8 KiB
mega.io/wp-content/themes/megapages/megalib/css/theme.css?ver=17712950076.7 KiB
mega.io/wp-content/themes/megapages/megalib/css/fonts.css?ver=1707971095958 B

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.4 s
URLTime Spent
mega.nz/2.4 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

Why this matters

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

Why this matters

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

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 56.5 KiB
URLTransfer SizeEst Savings
mega.nz/secureboot.js?r=177629714840.7 KiB20.8 KiB
blob:https://mega.nz/55ad46c3-c5af-4197-a68e-33b46c579beb27.7 KiB14.4 KiB
mega.io/wp-content/themes/megapages/megalib/js/megalib.js?ver=177441288731.8 KiB14.3 KiB
/wp-content/themes/megapages/megalib/js/megalib-component...15.2 KiB4.9 KiB
mega.io/wp-content/themes/megapages/assets/js/megapages.js?ver=17724476584.9 KiB2.2 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.5 KiB
URLTransfer SizeEst Savings
mega.io/wp-content/themes/megapages/megalib/css/common.css?ver=177244766410.8 KiB2.5 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 25.1 KiB
URLTransfer SizeEst Savings
mega.io/wp-includes/js/jquery/jquery.min.js?ver=3.7.134.7 KiB25.1 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
mega.io/wp-content/uploads/pass-hero.png1.1 MiB
mega.io/wp-content/themes/megapages/assets/animated-hero/video/xl.webm297.0 KiB
mega.io/wp-content/uploads/2023/03/20230221_Mega_icons_00025-1.png154.0 KiB
mega.io/wp-content/uploads/2023/03/20230215_Mega_icons_upd_00003.png125.3 KiB
mega.io/wp-content/uploads/20221223_Mega_Main_1-encryption-padlock-1.webm112.3 KiB
mega.io/wp-content/themes/megapages/assets/animated-hero/bgimg-xl/03.png110.5 KiB
mega.io/wp-content/themes/megapages/assets/animated-hero/bgimg-xl/02.png105.3 KiB
mega.io/wp-content/themes/megapages/assets/animated-hero/bgimg-xl/04.png104.7 KiB
mega.io/wp-content/themes/megapages/megalib/fonts/Inter-Bold.woff2104.0 KiB
mega.io/wp-content/themes/megapages/assets/animated-hero/bgimg-xl/01.png103.9 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Modern HTTP
●Network dependency tree
●Optimize viewport for mobile
●Max Potential First Input Delay 30 ms
●Reduce unused CSS
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 1,970 ms
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 30 ms
●Avoid large layout shifts 5 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
98

Accessibility

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.

Navigation

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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EN div.upper > div.inner-content > div.right-group > button.text-button
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[role]`s have all required `[aria-*]` attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○`[role]` values are valid
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
85

SEO

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
mega.io/aboutLearn more
mega.io/businessLearn more

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

To appear in search results, crawlers need access to your app.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback