LCP
Largest Contentful Paint
2.7s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking CSS
How to optimize pabitovr.github.io
Eliminate Render Blocking CSS
High Impact+8 points estimated
Why It Matters
Your CSS file blocks initial page render for 157ms, directly delaying FCP and LCP by preventing critical content from appearing.
How to Fix
Inline critical above-the-fold CSS directly in your HTML <head> section. Move non-critical CSS to load asynchronously using media='print' onload="this.media='all'" technique. Consider splitting your style.css into critical and non-critical parts.
0Good
What This Score Means
A score of 92 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
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 website has good overall performance with a score of 92/100, but there's still room for improvement in loading speed. The biggest issue is that your First Contentful Paint takes 2.7 seconds, which means users have to wait nearly 3 seconds before seeing any content on the page. The main culprit is your CSS stylesheet (style.css) which is blocking the initial page render and could be optimized by either inlining critical CSS or deferring non-essential styles. Additionally, setting up longer cache lifetimes for your CSS and JavaScript files could save about 7KB on repeat visits and make your site feel much faster for returning users.
Other Optimization Recommendations
Implement Long Term CSS Caching
Medium Impact+4 points estimatedWhy It Matters:
Your CSS cache lifetime of only 10 minutes wastes 5.4KB on repeat visits, slowing down returning users unnecessarily.
How to Fix:
Configure your GitHub Pages or web server to set Cache-Control headers for CSS files to 1 year (31536000 seconds). Use cache-busting with file hashing instead of query parameters (?v=1.2). Update your HTML to reference style-[hash].css for better cache invalidation control.
Optimize Network Resource Delivery
Medium Impact+6 points estimatedWhy It Matters:
Your 2.7s LCP indicates slow resource loading that could be improved through better resource prioritization and delivery optimization.
How to Fix:
Add resource hints like <link rel='preload' href='style.css' as='style'> for critical CSS. Consider inlining your small 5.9KB CSS file directly into HTML to eliminate the network request entirely. Minify your CSS and HTML to reduce transfer sizes further.
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 Network Request Chain
Your CSS dependency creates a 348ms critical request chain that delays content rendering and impacts Speed Index.
Inline Critical CSS Styles
The external CSS file is blocking initial page render, directly delaying First Contentful Paint by 156ms.
Implement Long-term Asset Caching
Short cache lifetimes force unnecessary re-downloads of static assets, slowing repeat visits and wasting 7 KiB of bandwidth.
Reserve Space for Dynamic Elements
Multiple elements are shifting position during load, creating a poor user experience and CLS score of 1.148.