Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize youtube.com
Multiple redirects are adding 780ms of unnecessary delay before the page even starts loading.
Update all internal links to point directly to https://m.youtube.com/ instead of https://youtube.com/. Configure server to serve mobile version directly without redirects. Update canonical URLs and sitemaps to reflect the final destination.
A score of 52 falls in the "Needs Improvement" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.
This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.
Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This mobile YouTube page has poor performance with a score of 52/100, indicating significant user experience issues. The biggest problem is render-blocking JavaScript and CSS files that are delaying the page from displaying content, causing an extremely slow Largest Contentful Paint of 8.9 seconds and First Contentful Paint of 6.0 seconds. The site is loading massive amounts of unused code - 612 KiB of unnecessary JavaScript and 178 KiB of unused CSS - while also suffering from a redirect that adds nearly a second of delay. Optimizing these render-blocking resources, removing unused code, and eliminating the redirect could potentially improve loading times by 4+ seconds and dramatically enhance the mobile browsing experience.
Why It Matters:
Critical CSS and JavaScript files are blocking page rendering and delaying LCP by 3 seconds.
How to Fix:
Move critical CSS inline using critical CSS extraction tools. Defer non-critical JavaScript by adding async/defer attributes to script tags. Load above-the-fold CSS first, then defer remaining stylesheets using media='print' onload technique.
Why It Matters:
Over 600KB of unused JavaScript and 180KB of unused CSS are unnecessarily delaying page load by 2+ seconds.
How to Fix:
Use coverage tools in Chrome DevTools to identify unused code. Split JavaScript bundles and lazy load non-critical components. Remove unused CSS by auditing stylesheets and implementing tree-shaking for CSS-in-JS solutions.
Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
The oversized logo image wastes 97 KiB and delays LCP by 450ms while being displayed much smaller than its actual size.
126 KiB of unused JavaScript from Google Analytics and GTM delays LCP by 900ms and wastes bandwidth.
Render blocking CSS and fonts delay LCP and FCP by 1,050ms, preventing users from seeing content immediately.
Award images are oversized by 441KB and lack explicit dimensions, causing layout shifts.