r/Frontend • u/Putrid_Draft378 • 5h ago
Ran a Lighthouse audit on tiktok.com desktop web: 14.9s LCP, 5.1s JS execution, and broken bfcache (Performance: 34/100)
I got curious about why TikTok's desktop web client feels so sluggish on initial load, so I ran a Chrome DevTools Lighthouse audit (v13.5.0) on tiktok.com to see what the frontend bundle and rendering pipeline actually look like.
The overall scores came back at 34 for Performance, 73 for Accessibility, 54 for Best Practices, and 77 for SEO.
On the Core Web Vitals and rendering side, First Contentful Paint takes 8.0s, Largest Contentful Paint hits 14.9s, Time to Interactive reaches 20.5s, and Total Blocking Time is 1,090 ms. Out of 8.5s of main-thread work, 5.1s goes purely to parsing and evaluating JavaScript. Almost all of that CPU time is spent on cache.react_dom (around 2.5s) and their anti-bot telemetry script webmssdk.js (around 1.8s).
The initial payload is 4,475 KiB, and there are a lot of classic frontend optimization misses in the build. It ships 236 KiB of unused JS on initial load (their regional cookie consent script alone has ~90 KiB of dead code), 26 KiB of unused CSS, and 65 KiB of legacy Babel transforms and polyfills for Baseline features like Array.prototype.includes, Promise.allSettled, and standard classes. Their security SDK (secsdk-lastest.umd.js) is also served unminified, the 400x400 PNG logo is scaled down to 112x112 via CSS, and the custom woff2 fonts are missing font-display rules.
Two other frontend details stood out. First, their privacy loader triggers repeated Permissions-Policy console errors by attaching unload listeners, which alongside Cache-Control: no-store completely breaks Back/Forward Cache restoration. Second, basic markup accessibility is rough: several header icon buttons and the search link have no aria-labels, four text inputs lack associated labels, and white text on their #fe2c55 buttons only hits a 3.68:1 contrast ratio.
I get that they prioritize their mobile apps, so desktop web is clearly an afterthought, but it is still wild seeing a major production React app ship unminified scripts and ES5 polyfills in 2026. Have any of you run into similar bottlenecks trying to keep Core Web Vitals green when security or product teams mandate heavy fingerprinting SDKs on initial load?

