Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.108141] map[node:map[boundingRect:map[bottom:17897 height:17316 left:0 right:412 top:581 width:412] lhId:page-1-MAIN nodeLabel:Extension 🧩 Get the Chrome Extension Bookmark ⭐ Click to Bookmark This Site Pro… path:2,HTML,1,BODY,4,MAIN selector:body > main.overflow-x-hidden snippet:<main class="overflow-x-hidden"> type:node] score:0.108141]]

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:47.091 source:map[column:64393 line:1 type:source-location url:https://m3u8-player.net/_next/static/chunks/1255-a841a0167cdc9bf2.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:78.616 source:map[type:text value:[unattributed]]] map[reflowTime:3.698 source:map[column:2628 line:0 type:source-location url:https://m3u8-player.net/_next/static/chunks/2749-c8c18c32c657f951.js urlProvider:network]] map[reflowTime:0.7 source:map[column:8881 line:0 type:source-location url:https://m3u8-player.net/_next/static/chunks/2749-c8c18c32c657f951.js urlProvider:network]] map[reflowTime:42.693 source:map[column:4110 line:0 type:source-location url:https://m3u8-player.net/_next/static/chunks/5684-f3121a3fcac2811a.js urlProvider:network]]]

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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

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.

Request	Cache TTL	Transfer Size
scripts.clarity.ms/0.8.69/clarity.js	86400.0 s	25.2 KiB
/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e178179150...	86400.0 s	11.3 KiB
analytics.ahrefs.com/analytics.js	14400.0 s	3.0 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.

	URL	Resource Size	Est Savings
M3U8 Player `div.block > div.flex > a.flex > img.w-8`	m3u8-player.net/logo.webp	17.9 KiB	17.9 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
m3u8-player.net/_next/static/css/7246120ffc5e6ac5.css	22.8 KiB	215 ms

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Extension 🧩 Get the Chrome Extension Bookmark ⭐ Click to Bookmark This Site Pro… `body > main.overflow-x-hidden`	0.108

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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: 1.5 s 145.9 KiB

URL	Transfer Size	Est Savings
accounts.google.com/gsi/client	98.3 KiB	76.9 KiB
www.googletagmanager.com/gtag/js?id=G-H2QLDPH4FL	169.0 KiB	69.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
m3u8-player.net/_next/static/chunks/1255-a841a0167cdc9bf2.js	1.6 s	1.3 s	39 ms
m3u8-player.net/	998 ms	86 ms	74 ms
www.googletagmanager.com/gtag/js?id=G-H2QLDPH4FL	559 ms	387 ms	95 ms
Unattributable	496 ms	15 ms	0.0 ms
scripts.clarity.ms/0.8.69/clarity.js	288 ms	244 ms	12 ms
m3u8-player.net/_next/static/chunks/5248-d3bf2d714f2558c2.js	171 ms	166 ms	4.9 ms
m3u8-player.net/_next/static/chunks/4bd1b696-100b9d70ed4e49c1.js	132 ms	81 ms	36 ms
m3u8-player.net/_next/static/chunks/8876-643a4521a15d6a59.js	116 ms	61 ms	54 ms
accounts.google.com/gsi/client	95 ms	39 ms	54 ms
m3u8-player.net/_next/static/chunks/7309-893209869a726851.js	92 ms	56 ms	35 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.9 s
Style & Layout	900 ms
Other	668 ms
Script Parsing & Compilation	523 ms
Parse HTML & CSS	126 ms
Rendering	81 ms
Garbage Collection	35 ms

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 885 KiB

●User Timing marks and measures 1 user timing

●Avoid long main-thread tasks 16 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 400 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 80 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.block > div.flex > button.inline-flex `div.container > div.block > div.flex > button.inline-flex`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > ul.flex > li.font-medium > a `div.flex > ul.flex > li.font-medium > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Manage your M3U playlists online, get a stable private address, and stop reconf… `body > aside.overflow-x-hidden > div.container > p.min-w-0`
See how it works `aside.overflow-x-hidden > div.container > p.min-w-0 > a.font-semibold`
Extension `div.container > div.text-center > a.mx-auto > span.inline-flex`
Bookmark `div.container > div.text-center > button.mx-auto > span.inline-flex`
View Pricing `aside.border-y > div.container > div.flex > a.text-primary`
Direct Link `div.bg-card > div.px-6 > div.flex > button.inline-flex`
WhatsApp `div.flex > div.flex > div.flex > button.inline-flex`
Telegram `div.flex > div.flex > div.flex > button.inline-flex`
Reddit `div.flex > div.flex > div.flex > button.inline-flex`
WeChat `div.flex > div.flex > div.flex > button.inline-flex`
Popular `a.group > div.p-8 > div.flex > span.text-xs`
Start Now `a.group > div.p-8 > div.flex > span`
Recommended `a.group > div.p-8 > div.flex > span.text-xs`
Convert Now `a.group > div.p-8 > div.flex > span`
Best value `div.container > div.grid > div.bg-card > span.inline-flex`
$3.25/month · Save 35% `div.grid > div.bg-card > div.px-6 > p.text-sm`
Start yearly `div.grid > div.bg-card > div.flex > button.inline-flex`
See full comparison `section.bg-muted/30 > div.container > div.mt-4 > a.font-medium`
View Pricing `section.bg-muted/30 > div.container > div.mt-8 > a.inline-flex`
Try the free playlist manager `section.bg-muted/30 > div.container > div.mt-8 > a.text-sm`
support@m3u8-player.net `section.bg-muted/30 > div.container > p.mt-5 > a.font-medium`
HLS Protocol Support `ul.flex > li.flex > div > div.mb-3`
Cross-Platform Compatible `ul.flex > li.flex > div > div.mb-3`
High-Performance Playback `ul.flex > li.flex > div > div.mb-3`
FAQ `section#faq > div.container > div.text-center > span.inline-flex`
Start Playing `div.mx-auto > div.mt-8 > button.inline-flex > a.flex`
Download App `div.floating-action-group > div.floating-action-install-wrap > button.floating-action-main > span.floating-action-main-label`

These are opportunities to improve the legibility of your content.

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
Download App `body > div.floating-action-group > div.floating-action-install-wrap > button.floating-action-main`

○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>`

●`[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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○`[lang]` attributes have a valid value

○`<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

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

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

●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`