Skip to content
https://timhopam.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.

—

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
i.ytimg.com/vi/sd8sfpVAR8w/hqdefault.jpg7200.0 s20.7 KiB
i.ytimg.com/vi/DvadfV2GiP4/hqdefault.jpg7200.0 s8.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.

URLResource SizeEst Savings
Nước cờ em chọn div.tha-foryou-track > a.tha-foryou-card > span.tha-foryou-image > img
i.ytimg.com/vi/sd8sfpVAR8w/hqdefault.jpg20.6 KiB7.7 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.

URLTransfer Size
/wp-content/litespeed/css/57e3c0c08d5cf72da30a8fb5951f36c...6.9 KiB
timhopam.com/wp-includes/js/jquery/jquery.min.js30.7 KiB
/wp-content/litespeed/css/e0fdec2c249ef4ddfb9cb25481823b3...2.9 KiB
/wp-content/litespeed/css/b8df096240ea6bb336a15fe265b38a0...12.1 KiB
/wp-content/litespeed/css/321e0b2b5d557413598c84581ddf0ea...129 B

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

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.

Diagnostics

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.

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.

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.

CategoryTime Spent
Other1.0 s
Style & Layout591 ms
Script Evaluation504 ms
Rendering224 ms
Script Parsing & Compilation115 ms
Parse HTML & CSS112 ms

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
●Avoids enormous network payloads Total size was 1,937 KiB
●JavaScript execution time 0.5 s
●Avoid non-composited animations 5 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 0 ms
●Server Backend Latencies 390 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 380 ms
○INP breakdown
○LCP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid large layout shifts
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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Tài khoản Đăng ký Đăng nhập div#header > div.container > div#ham-user-nav > div#ham-guest-menu

These are opportunities to improve the usage of ARIA in your application which 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
Ballad div#content_box > section.hopam-discover > nav.hopam-rhythm-list > a.hopam-rhythm
01 ol.hopam-top-viewed > li > a.hopam-top-link > span.hopam-rank
02 ol.hopam-top-viewed > li > a.hopam-top-link > span.hopam-rank
03 ol.hopam-top-viewed > li > a.hopam-top-link > span.hopam-rank
04 ol.hopam-top-viewed > li > a.hopam-top-link > span.hopam-rank
⭐ BÀI HÁT DÀNH CHO BẠN div#content_box > section.tha-foryou > div.tha-foryou-head > h3.featured-category-title
HỢP ÂM BÀI HÁT MỚI ĐĂNG div.article > div#content_box > section.hopam-home-section > h3.featured-category-title
Duy Mạnh article.latestPost > header > div.post-info > a
Hoàng Hải article.latestPost > header > div.post-info > a
Phạm Khải Tuấn article.latestPost > header > div.post-info > a
Minh Khang article.latestPost > header > div.post-info > a
Jimmii Nguyễn article.latestPost > header > div.post-info > a
Tuno article.latestPost > header > div.post-info > a
Jimmii Nguyễn article.latestPost > header > div.post-info > a
Nhạc Ngoại article.latestPost > header > div.post-info > a
Jimmii Nguyễn article.latestPost > header > div.post-info > a
Nguyễn Đình Long article.latestPost > header > div.post-info > a
Lý Thiên Tuấn article.latestPost > header > div.post-info > a
Đạt Max article.latestPost > header > div.post-info > a
Long Họ Huỳnh article.latestPost > header > div.post-info > a
Tracy Thảo My article.latestPost > header > div.post-info > a
1.034 div.pagination-wrapper > nav.navigation > div.nav-links > a.page-numbers
Next div.pagination-wrapper > nav.navigation > div.nav-links > a.next
🎸 CA KHÚC NGẪU NHIÊN div.article > div#content_box > section.hopam-home-section > h3.featured-category-title
Hạnh Nguyễn article.latestPost > header > div.post-info > a
Nguyễn Văn Chung article.latestPost > header > div.post-info > a
Hà Thúc Sinh article.latestPost > header > div.post-info > a
Phi Bằng article.latestPost > header > div.post-info > a
Quang Dũng article.latestPost > header > div.post-info > a
thơ Yên Ninh article.latestPost > header > div.post-info > a
Thái Cơ article.latestPost > header > div.post-info > a
Xem tất cả › div#block-26 > section.tha-explore-widget > div.tha-explore-head > a#thaExploreAllLink
Nhạc sĩ section.tha-explore-widget > div.tha-explore-controls-row > div.tha-tabs-nav > button.tha-tab-btn
Ca sĩ section.tha-explore-widget > div.tha-explore-controls-row > div.tha-tabs-nav > button.tha-tab-btn
NHẠC SĨ div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-role
NHẠC SĨ div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-role
Hơn 110 sáng tác div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-count
NHẠC SĨ div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-role
Hơn 120 sáng tác div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-count
Kết nối cùng cộng đồng yêu nhạc div.th-social > div.th-social-title > div > small
Facebook/timhopam div.th-social > a.th-social-item > span.th-social-text > b
Theo dõi trang div.th-social > a.th-social-item > span.th-social-text > small
YouTube/@timhopamguitar div.th-social > a.th-social-item > span.th-social-text > b
Xem video hướng dẫn div.th-social > a.th-social-item > span.th-social-text > small
Tham gia cộng đồng yêu Guitar div.th-social > a.th-social-item > span.th-social-text > small
Bắt đầu đếm div.metro-box > div.metro-btn-row > button#btnToggle > span#btnLabel

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.metro-wrapper > div.metro-box > div.metro-control-slider > input#bpmRange div.metro-wrapper > div.metro-box > div.metro-control-slider > input#bpmRange

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#header > div.container > div#secondary-navigation > a#pull div#header > div.container > div#secondary-navigation > a#pull

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.

Best practices

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

These items highlight common accessibility best practices.

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
NGƯỜI MỚI TẬP CHƠI aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
NHẠC XUÂN HAY NHẤT aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
TUYỆT PHẨM BOLERO aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
CA KHÚC HAY VỀ MẸ aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
TOP 100 NHẠC TRỮ TÌNH aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
NHẠC ĐÁM CƯỚI aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
○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
●`[role]` values are valid
●`[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
●Elements use only permitted ARIA 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.
●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
●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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
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