LCP
Largest Contentful Paint
0.8s
Good
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Extend Cache Lifetimes
How to optimize learndigitalmarketing.academy
Extend Cache Lifetimes
Medium Impact+2 points estimated
Why It Matters
Short cache lifetimes force unnecessary re-downloads of static assets, slowing repeat visits and wasting 69 KiB of bandwidth.
How to Fix
Set cache headers for your avatar image to at least 1 year instead of 1 week. Configure your server or CDN to cache YouTube thumbnail images for longer periods by implementing a proxy or downloading them locally. Add cache-control headers with max-age=31536000 for static assets that don't change frequently.
0Good
What This Score Means
A score of 100 falls in the "Good" 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
17ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.05
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website achieves an excellent performance score of 100/100, indicating fast loading times and good user experience. However, there are still optimization opportunities that could improve repeat visitor experience and reduce bandwidth usage. The biggest issue is inefficient caching policies, particularly for images like YouTube thumbnails that are only cached for 2 hours instead of longer periods, wasting about 69 KiB on repeat visits. Additionally, the site's CSS file could be optimized by removing 78% of unused CSS rules (saving 11 KiB) and minifying the remaining code to reduce file size by another 2 KiB.
Other Optimization Recommendations
Remove Unused CSS Rules
Medium Impact+3 points estimatedWhy It Matters:
78% of your CSS is unused, creating unnecessary network overhead that could impact initial page rendering.
How to Fix:
Audit your styles.css file to identify and remove unused CSS rules that account for 11 KiB of wasted bytes. Use tools like PurgeCSS or UnCSS to automatically eliminate unused styles. Consider splitting CSS into critical above-the-fold styles and non-critical styles that can be loaded asynchronously.
Minify CSS Files
Low Impact+1 point estimatedWhy It Matters:
Unminified CSS wastes 2.5 KiB of network payload, adding unnecessary bytes to your critical rendering path.
How to Fix:
Enable CSS minification in your build process or server configuration to remove whitespace, comments, and unnecessary characters. Use tools like cssnano or clean-css to automatically minify your styles.css file. Consider enabling gzip compression alongside minification for additional savings.
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 Main Thread Processing
JavaScript execution blocks the main thread for 2.5 seconds, creating 300ms of Total Blocking Time that prevents user interactions.
Reduce Unused JavaScript Payload
226KB of unused JavaScript is wasted bandwidth that delays LCP by 1.4 seconds and increases loading costs.
Eliminate Render-Blocking CSS Resources
Critical CSS is blocking page rendering for 2,040ms, severely delaying both LCP and FCP by over 2 seconds.
Minify CSS Files
Unminified CSS wastes 2.5 KiB of network payload, adding unnecessary bytes to your critical rendering path.