LCP
Largest Contentful Paint
5.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Render-Blocking CSS Resources
How to optimize fiziotars.hu
Next.js SiteScore: 69/100Analyzed December 2025
Remove Render-Blocking CSS Resources
High Impact+15 points estimated
Why It Matters
Critical CSS files are blocking initial render and delaying LCP by 150ms.
How to Fix
Use Next.js built-in CSS optimization by moving critical styles to _app.js or inline them in the document head. Extract above-the-fold CSS into a separate critical.css file. Defer non-critical CSS using media='print' onload='this.media="all"' technique for remaining stylesheets.
0Needs Improvement
What This Score Means
A score of 69 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
160ms
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 Next.js/React website has poor performance with a score of 69/100, primarily due to bloated third-party resources that are significantly slowing down page loading. The biggest culprit is Google reCAPTCHA, which is loading 191KB of unused JavaScript and causing nearly a full second of delay, while also triggering performance-damaging forced reflows. The site's First Contentful Paint and Largest Contentful Paint are both taking a sluggish 5 seconds, largely because of render-blocking CSS files and excessive unused code from both reCAPTCHA and UI frameworks like Ant Design. Removing or optimizing the reCAPTCHA implementation, cleaning up unused CSS/JavaScript, and addressing the render-blocking resources could easily improve the performance score by 15-20 points and dramatically speed up the user experience.
Other Optimization Recommendations
Eliminate Unused JavaScript from ReCAPTCHA
High Impact+25 points estimatedWhy It Matters:
ReCAPTCHA JavaScript wastes 191 KiB and delays LCP/FCP by 900ms, severely impacting Core Web Vitals.
How to Fix:
Implement lazy loading for ReCAPTCHA by only loading it when users interact with forms. Use dynamic imports in Next.js: const ReCAPTCHA = dynamic(() => import('react-google-recaptcha'), { ssr: false }). Load the script only when form fields are focused using useEffect hooks.
Optimize Unused CSS Rules
Medium Impact+12 points estimatedWhy It Matters:
70 KiB of unused CSS is wasting bandwidth and delaying FCP/LCP by 150ms.
How to Fix:
Use PurgeCSS with Next.js to automatically remove unused CSS during build process. Configure purge options in next.config.js to whitelist dynamic classes. Split CSS by components using CSS Modules or styled-components to load only necessary styles per page.
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Performance Analyses
Next.js Performance Resources
Frequently Asked Questions
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