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

26

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:246.994 source:map[column:174191 line:1 type:source-location url:https://sf16-website-login.neutral.ttwstatic.com/obj/tiktok_web_login_static/ttweb_webmssdk_ex/1.0.0.2404/webmssdk_ex.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:10.629 source:map[column:62724 line:0 type:source-location url:https://sf16-website-login.neutral.tiktokcdn-eu.com/obj/tiktok_web_login_static_eu/webmssdk/1.0.0.368/webmssdk.js urlProvider:network]] map[reflowTime:175.722 source:map[column:63335 line:0 type:source-location url:https://sf16-website-login.neutral.tiktokcdn-eu.com/obj/tiktok_web_login_static_eu/webmssdk/1.0.0.368/webmssdk.js urlProvider:network]] map[reflowTime:9.578 source:map[column:177534 line:0 type:source-location url:https://sf16-website-login.neutral.ttwstatic.com/obj/tiktok_web_login_static/ttweb_webmssdk_ex/1.0.0.2404/webmssdk_ex.js urlProvider:network]] map[reflowTime:237.416 source:map[column:178008 line:0 type:source-location url:https://sf16-website-login.neutral.ttwstatic.com/obj/tiktok_web_login_static/ttweb_webmssdk_ex/1.0.0.2404/webmssdk_ex.js urlProvider:network]]]

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:366.3870009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:2134.2899990234373 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-VIDEO
nodeLabel: div#tiktok-webapp-mobile-player-container > div#playback_refactor > div > video
path: 1,HTML,1,BODY,0,DIV,0,DIV,9,DIV,0,DIV,0,DIV,4,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div#tiktok-webapp-mobile-player-container > div#playback_refactor > div > video
snippet: <video data-version="0.3.73" preload="auto" playsinline="" webkit-playsinline="true" src="blob:https://www.tiktok.com/bf60a9a5-140f-47fd-ba94-1f0f212a9aa0" style="width: 100%; height: 100%; vertical-align: middle; position: absolute;">

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

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.

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst 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 KiB28.2 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.

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

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: 830 ms
URLTime Spent
tiktok.com/830 ms
www.tiktok.com/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

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 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: 150 ms 14.4 KiB
URLTransfer SizeEst Savings
/obj/tiktok_web_login_static/secsdk/secsdk-lastest.umd.js40.6 KiB14.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 41.5 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.

URLTotal CPU TimeScript EvaluationScript Parse
/obj/tiktok_web_login_static_eu/webmssdk/1.0.0.368/webmss...4.3 s2.4 s18 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...3.2 s2.7 s17 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...1.5 s866 ms109 ms
Unattributable975 ms143 ms0.0 ms
www.tiktok.com/584 ms17 ms0.4 ms
/obj/tiktok_web_login_static_eu/tiktok_privacy_protection...523 ms392 ms35 ms
/obj/tiktok_web_login_static_eu/pns/tiktok-cookie-banner/...333 ms264 ms52 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...324 ms253 ms64 ms
/obj/tiktok_web_login_static_eu/slardar/fe/sdk-web/browse...280 ms131 ms3.4 ms
/obj/tiktok_web_login_static/secsdk/secsdk-lastest.umd.js244 ms224 ms18 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...206 ms194 ms12 ms
/obj/tiktok_web_login_static/ttweb_webmssdk_ex/1.0.0.2404...125 ms94 ms26 ms
/obj/tiktok_web_login_static_eu/ztcatt/v1.0.0.21/loader-b...109 ms78 ms30 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...96 ms48 ms37 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...86 ms80 ms2.0 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...79 ms64 ms15 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...74 ms12 ms59 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...72 ms59 ms13 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...60 ms56 ms4.3 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...53 ms2.2 ms17 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...51 ms39 ms9.5 ms
/obj/tiktok_web_login_static_eu/tiktok/webapp/main/mobile...50 ms11 ms31 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.

CategoryTime Spent
Script Evaluation8.4 s
Style & Layout2.5 s
Other1.5 s
Script Parsing & Compilation802 ms
Garbage Collection259 ms
Rendering213 ms
Parse HTML & CSS120 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure 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

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

Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 52 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 200 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 260 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
Avoid non-composited animations
92

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.

Why this matters

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.

Why this matters

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.

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
`[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
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
The page contains a heading, skip link, or landmark region
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
`<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
Heading elements appear in a sequentially-descending order
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
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.
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.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
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.
73

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Access to fetch at 'https://mon16-normal-no1a.tiktokv.eu/monitor_browser/collect/batch/?bid=tiktok_pns_web_runtime' from origin 'https://www.tiktok.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
Uses HTTPS
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
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
83

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

Why this matters

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.

Why this matters

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.

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
robots.txt is valid
Document has a valid `hreflang`
Image elements have `[alt]` attributes

Send Feedback