LCP
Largest Contentful Paint
4.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking Resources
How to optimize picki.com.vn
Eliminate Render Blocking Resources
High Impact+15 points estimated
Why It Matters
Render-blocking CSS and JavaScript files are delaying First Contentful Paint by 320ms and blocking critical rendering.
How to Fix
In LiteSpeed Cache settings, enable 'Optimize CSS Delivery' to defer non-critical CSS. Move jQuery and other blocking scripts to load asynchronously using the 'JS Defer' option. Inline critical CSS for above-the-fold content to prevent render blocking.
0Needs Improvement
What This Score Means
A score of 77 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
32ms
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 WordPress site has poor performance with a score of 77/100, but several critical issues are severely impacting user experience. The biggest problem is an extremely slow Speed Index of 9.1 seconds, meaning visitors wait over 9 seconds to see meaningful content appear on the page. The main culprits are a sluggish server response time (700ms), massive resource load delays (5.4 seconds), render-blocking JavaScript and CSS files, and oversized images that could be compressed by 430KB. Addressing the server performance, removing unused CSS/JavaScript (61KB combined savings), and optimizing images would dramatically improve loading speeds and could boost the performance score by 15-20 points.
Other Optimization Recommendations
Fix Resource Load Delay Issues
High Impact+25 points estimatedWhy It Matters:
Resource load delay of 5.4 seconds is causing your LCP to reach 4.1 seconds, severely impacting user experience.
How to Fix:
The LCP element is a background DIV that's delayed by render-blocking resources. Add fetchpriority='high' to critical background images. Use LiteSpeed Cache's critical CSS generation to inline above-the-fold styles. Consider converting the LCP background image to an optimized <img> tag with proper loading priority.
Optimize Server Response Time
High Impact+12 points estimatedWhy It Matters:
Your server takes 700ms to respond, which delays all subsequent resource loading and impacts both LCP and FCP by 600ms.
How to Fix:
Enable LiteSpeed Cache's page caching and object cache features. Optimize your WordPress database using WP-Optimize plugin. Consider upgrading to a faster hosting plan or implement a CDN through LiteSpeed's built-in CDN integration to reduce TTFB.
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 WordPress Speed Tests
WordPress Performance Resources
Optimize Hero Image Delivery
The 664KB hero background image is delaying LCP by 1.6 seconds as it's not optimized or prioritized.
Remove Unused JavaScript and CSS
Over 2.4MB of unused JavaScript and 411KB of unused CSS are slowing LCP by 7+ seconds.
Eliminate Render-Blocking Resources
Critical CSS and JavaScript files are blocking initial page render, delaying FCP by 4.4 seconds.
Extend Cache Lifetimes for Assets
Short cache durations force unnecessary re-downloads on repeat visits, slowing LCP by 150ms.