Skip to content
https://w3techs.com

Lighthouse Mobile

· 0 checks — Mobile 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.

97

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 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:39.927 source:map[type:text value:[unattributed]]]]

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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 SizeDuration
w3techs.com/s46.css4.9 KiB310 ms

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
media.ethicalads.io/images/2023/07/mongodb-codedark-240x180.png3600.0 s29.6 KiB
m.q-success.com/mtj0.0 ms22.1 KiB
media.ethicalads.io/media/client/ethicalads.min.js3600.0 s10.8 KiB
/api/v1/decision/?publisher=w3techs-com&ad_types=image-v1...0.0 ms1.1 KiB
media.ethicalads.io/abp/px.gif?ch=2&rn=6.7837313715855893600.0 s558 B
server.ethicalads.io/proxy/view/10122/019db6e0-5aca-7f40-9c88-220f0c199ca5/0.0 ms431 B
media.ethicalads.io/abp/px.gif?ch=1&rn=6.7837313715855893600.0 s345 B

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
Sponsored: MongoDB div.ea-placement > div.ea-content > a > img
media.ethicalads.io/images/2023/07/mongodb-codedark-240x180.png29.1 KiB23.7 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Sponsored: MongoDB div.ea-placement > div.ea-content > a > img
media.ethicalads.io/images/2023/07/mongodb-codedark-240x180.png
Send email ul.share-buttons > li > a > img
Share on LinkedIn ul.share-buttons > li > a > img
Post on Bluesky ul.share-buttons > li > a > img
Add to DEV ul.share-buttons > li > a > img
Add to Hacker News ul.share-buttons > li > a > img

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

●Time to Interactive 2.5 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Max Potential First Input Delay 30 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 85 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.7 s
●Avoid long main-thread tasks 1 long task found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 160 ms
●Server Backend Latencies 130 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 160 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
83

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Simplify infrastructure div.ea-content > div.ea-text > a > strong.ea-headline
www.mongodb.com div.horizontal > div.ea-placement > div.ea-content > div.ea-domain
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t
© W3Techs.com table.tech_home > tbody > tr > th.w3t

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Wix tbody > tr > td > a.no_und
Astro tbody > tr > td > a.no_und
PHP tbody > tr > td > a.no_und
Ruby tbody > tr > td > a.no_und
Java tbody > tr > td > a.no_und
Scala tbody > tr > td > a.no_und
Ruby tbody > tr > td > a.no_und
Scala tbody > tr > td > a.no_und
Flash tbody > tr > td > a.no_und
Java tbody > tr > td > a.no_und
jQuery tbody > tr > td > a.no_und
Bootstrap tbody > tr > td > a.no_und
Underscore tbody > tr > td > a.no_und
Next.js tbody > tr > td > a.no_und
GSAP tbody > tr > td > a.no_und
Nuxt tbody > tr > td > a.no_und
Bootstrap tbody > tr > td > a.no_und
Animate tbody > tr > td > a.no_und
Foundation tbody > tr > td > a.no_und
Apache tbody > tr > td > a.no_und
LiteSpeed tbody > tr > td > a.no_und
Node.js tbody > tr > td > a.no_und
Node.js tbody > tr > td > a.no_und
LiteSpeed tbody > tr > td > a.no_und
hPanel tbody > tr > td > a.no_und
Plesk tbody > tr > td > a.no_und
cPanel tbody > tr > td > a.no_und
RunCloud tbody > tr > td > a.no_und
GridPane tbody > tr > td > a.no_und
Linux tbody > tr > td > a.no_und
Unix tbody > tr > td > a.no_und
Ubuntu tbody > tr > td > a.no_und
Shopify tbody > tr > td > a.no_und
Hostinger tbody > tr > td > a.no_und
Amazon tbody > tr > td > a.no_und
Hostinger tbody > tr > td > a.no_und
Shopify tbody > tr > td > a.no_und
Amazon tbody > tr > td > a.no_und
Google tbody > tr > td > a.no_und
Hostinger tbody > tr > td > a.no_und
Amazon tbody > tr > td > a.no_und
Oracle tbody > tr > td > a.no_und
Hostinger tbody > tr > td > a.no_und
Cloudflare tbody > tr > td > a.no_und
Hostinger tbody > tr > td > a.no_und
IONOS tbody > tr > td > a.no_und
Microsoft tbody > tr > td > a.no_und
Hostinger tbody > tr > td > a.no_und
Let’s Encrypt tbody > tr > td > a.no_und
GlobalSign tbody > tr > td > a.no_und
GoDaddy Group tbody > tr > td > a.no_und
DigiCert Group tbody > tr > td > a.no_und
Starfield tbody > tr > td > a.no_und
Actalis tbody > tr > td > a.no_und
CDNJS tbody > tr > td > a.no_und
jsDelivr tbody > tr > td > a.no_und
jsDelivr tbody > tr > td > a.no_und
unpkg tbody > tr > td > a.no_und
AdRoll tbody > tr > td > a.no_und
Equativ tbody > tr > td > a.no_und
AdRoll tbody > tr > td > a.no_und
Skimlinks tbody > tr > td > a.no_und
WhatsApp tbody > tr > td > a.no_und
Facebook tbody > tr > td > a.no_und
Twitter/X tbody > tr > td > a.no_und
Pinterest tbody > tr > td > a.no_und
LinkedIn tbody > tr > td > a.no_und
WhatsApp tbody > tr > td > a.no_und
Telegram tbody > tr > td > a.no_und
VKontakte tbody > tr > td > a.no_und
Cookies tbody > tr > td > a.no_und
HTTP/3 tbody > tr > td > a.no_und
External CSS tbody > tr > td > a.no_und
Compression tbody > tr > td > a.no_und
Open Graph tbody > tr > td > a.no_und
Twitter/X Cards tbody > tr > td > a.no_und
JSON-LD tbody > tr > td > a.no_und
Open Graph tbody > tr > td > a.no_und
HTML tbody > tr > td > a.no_und
XHTML tbody > tr > td > a.no_und
HTML5 tbody > tr > td > a.no_und
HTML tbody > tr > td > a.no_und
Windows-1252 tbody > tr > td > a.no_und
Windows-1251 tbody > tr > td > a.no_und
PNG tbody > tr > td > a.no_und
JPEG tbody > tr > td > a.no_und
SVG tbody > tr > td > a.no_und
WebP tbody > tr > td > a.no_und
GIF tbody > tr > td > a.no_und
SVG tbody > tr > td > a.no_und
WebP tbody > tr > td > a.no_und
AVIF tbody > tr > td > a.no_und
.com tbody > tr > td > a.no_und
.org tbody > tr > td > a.no_und
.de tbody > tr > td > a.no_und
.br tbody > tr > td > a.no_und
.ru tbody > tr > td > a.no_und
.in tbody > tr > td > a.no_und
.fr tbody > tr > td > a.no_und
.ai tbody > tr > td > a.no_und
Japan tbody > tr > td > a.no_und
France tbody > tr > td > a.no_und
Brazil tbody > tr > td > a.no_und
Cyprus tbody > tr > td > a.no_und
English tbody > tr > td > a.no_und
Spanish tbody > tr > td > a.no_und
German tbody > tr > td > a.no_und
Japanese tbody > tr > td > a.no_und
French tbody > tr > td > a.no_und
English tbody > tr > td > a.no_und
Chinese tbody > tr > td > a.no_und

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●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.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Elements with visible text labels have matching accessible names.
96

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
W3Techs div#hd > div#hdl > a > img
w3techs.com/logo1.gif150 x 50150 x 50225 x 75
●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
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
100

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.

○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 have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback