LCP
Largest Contentful Paint
12.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused CSS Rules
How to optimize apple.com
Eliminate Unused CSS Rules
High Impact+12 points estimated
Why It Matters
94 KiB of unused CSS is blocking render and delaying LCP by 450ms.
How to Fix
Remove unused CSS from main.built.css (93% unused), modal.css (99% unused), and home-gallery.built.css (81% unused). Use tools like PurgeCSS to automatically eliminate dead CSS. Split critical above-the-fold CSS into inline styles and defer non-critical CSS loading.
0Needs Improvement
What This Score Means
A score of 56 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
16ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Apple.com page has poor performance with a score of 56/100, primarily due to excessive unused code and blocking resources. The biggest problem is 94 KiB of unused CSS that's delaying page rendering by 450ms, along with 280 KiB of unused JavaScript that could save 1.5 seconds in loading time. The site is also suffering from render-blocking requests that delay First Contentful Paint by over 11 seconds, and legacy JavaScript polyfills that aren't needed for modern browsers. Cleaning up unused code, deferring non-critical resources, and optimizing the critical rendering path could dramatically improve load times and boost the performance score by 30+ points.
Other Optimization Recommendations
Reduce Unused JavaScript Bundles
High Impact+18 points estimatedWhy It Matters:
280 KiB of unused JavaScript is slowing page load by 1.5 seconds and delaying LCP.
How to Fix:
Code-split autofilms.built.js (81% unused) and globalheader.umd.js (35% unused) to load only necessary functionality. Implement dynamic imports for gallery features that aren't immediately needed. Use tree-shaking in your build process to eliminate dead code automatically.
Fix Forced Layout Reflows
Medium Impact+8 points estimatedWhy It Matters:
JavaScript is causing 278ms of forced reflows that block rendering and hurt user experience.
How to Fix:
Batch DOM reads and writes in ac-analytics.js and main.built.js to avoid layout thrashing. Use transform properties instead of changing geometric properties like offsetWidth. Implement requestAnimationFrame for smoother animations and DOM updates.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Optimize LCP Image Discovery
The LCP image is not discoverable in initial HTML, causing delayed loading and poor performance.
Remove Unused JavaScript Code
280 KiB of unused JavaScript wastes bandwidth and delays LCP by 1.5 seconds.
Eliminate Render-Blocking JavaScript
Render-blocking scripts delay First Contentful Paint by 11.2 seconds, severely impacting user experience.
Fix Forced Layout Reflows
JavaScript is causing 278ms of forced reflows that block rendering and hurt user experience.