Lighthouse Mobile
· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.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.
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
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.
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 |
|---|---|---|
| /obj/tiktok_web_login_static/slardar/fe/sdk-web/plugins/c... | 300.0 s | 9.8 KiB |
| /obj/tiktok_web_login_static/slardar/fe/sdk-web/plugins/c... | 300.0 s | 9.8 KiB |
| /obj/tiktok_web_login_static/slardar/fe/sdk-web/plugins/c... | 300.0 s | 9.6 KiB |
| /obj/tiktok_web_login_static/slardar/fe/sdk-web/plugins/c... | 300.0 s | 9.6 KiB |
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.
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#login-modal > div.middle > div.css-1ucn8qi-f59ed85f--DivIconContainer > img div#login-modal > div.middle > div.css-1ucn8qi-f59ed85f--DivIconContainer > img | /obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile... | 29.7 KiB | 28.2 KiB |
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.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
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.
| URL | Transfer Size |
|---|---|
| /obj/tiktok_web_login_static_eu/tiktok-infra/csp/sdk-pre/... | 1.7 KiB |
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.
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.
Diagnostics
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 |
|---|---|---|
| /obj/tiktok_web_login_static/secsdk/secsdk-lastest.umd.js | 40.6 KiB | 14.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 |
|---|---|---|
| /obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile... | 30.2 KiB | 27.9 KiB |
| /obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile... | 17.9 KiB | 13.6 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.
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.
| Category | Time Spent |
|---|---|
| Script Evaluation | 8.1 s |
| Style & Layout | 2.3 s |
| Other | 1.3 s |
| Script Parsing & Compilation | 807 ms |
| Garbage Collection | 262 ms |
| Rendering | 162 ms |
| Parse HTML & CSS | 113 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
| Back/forward cache is disabled because WebSocket has been used. | Not actionable |
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.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div.tt-intro__container > div.tt-intro__scroll-body > div.mb-16 > img.tt-intro__large-image div.tt-intro__container > div.tt-intro__scroll-body > div.mb-16 > img.tt-intro__large-image | /obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile... |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
Remote-access “transfers of EEA User Data to China”: Update on Irish GDPR decis… body.hidden > div#:r6: > div.TUXModal-overlay > div#:r4: |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Open TikTok div.middle > div.css-i270b2-f59ed85f--DivGuideBtnContainer > div.matrix-smart-wrapper > button.css-fnrey4-f59ed85f--ButtonOpenTT |
Allow cookies from TikTok on this browser? div.tiktok-cookie-banner > div.cookie-content > p.cookie-title |
Cookies Policy div.tiktok-cookie-banner > div.cookie-content > p.cookie-desc > a |
Got it div.css-1428ksb-f59ed85f--ButtonItem > button.TUXButton > div.TUXButton-content > div.TUXButton-label |
These are opportunities to improve the legibility of your content.
Best Practices
General
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 |
|---|---|
| Unload event listeners are deprecated and will be removed. | /obj/tiktok_web_login_static_eu/tiktok_privacy_protection... line 3, col 11517 |
| SharedStorage |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 400 () | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. | |
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
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.
Crawling and Indexing
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
Learn more div.tt-sheet__container > div.tt-sheet__body > div.text-color-TextSecondary > a |
To appear in search results, crawlers need access to your app.
Content Best Practices
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
Format your HTML in a way that enables crawlers to better understand your app’s content.