LCP
Largest Contentful Paint
12.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Discovery
How to optimize apple.com
Optimize LCP Image Discovery
High Impact+15 points estimated
Why It Matters
The LCP image is not discoverable in initial HTML, causing delayed loading and poor performance.
How to Fix
Add fetchpriority='high' attribute to the hero iPhone image. Include the image directly in HTML instead of loading via JavaScript. Preload the LCP image using <link rel='preload' as='image'> in the document head.
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
Apple's website has poor performance with a score of 56/100, indicating significant issues that hurt user experience. The biggest problem is excessive JavaScript that blocks the page from rendering - nearly 287KB of unused JavaScript is delaying content display by 1.5 seconds, while render-blocking scripts are causing an 11-second delay in First Contentful Paint. The site also suffers from inefficient font loading and caching strategies that could save an additional 1.5MB in bandwidth. Removing unused JavaScript, deferring non-critical scripts, and optimizing font delivery would provide the most immediate performance improvements.
Other Optimization Recommendations
Eliminate Render-Blocking JavaScript
High Impact+25 points estimatedWhy It Matters:
Render-blocking scripts delay First Contentful Paint by 11.2 seconds, severely impacting user experience.
How to Fix:
Add async or defer attributes to non-critical JavaScript files. Move autofilms.built.js and globalheader.umd.js to load after initial render. Inline critical JavaScript directly in HTML for immediate execution.
Remove Unused JavaScript Code
High Impact+20 points estimatedWhy It Matters:
280 KiB of unused JavaScript wastes bandwidth and delays LCP by 1.5 seconds.
How to Fix:
Use tree-shaking to eliminate dead code from autofilms.built.js (80% unused). Split large bundles into smaller chunks loaded on-demand. Remove legacy polyfills for modern browser features like Array.isArray and forEach.
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
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.
Reduce Unused JavaScript Bundles
280 KiB of unused JavaScript is slowing page load by 1.5 seconds and delaying LCP.