LCP
Largest Contentful Paint
6.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused CSS Rules
How to optimize tecu.it
WordPress SiteScore: 62/100Analyzed February 2026
Remove Unused CSS Rules
High Impact+18 points estimated
Why It Matters
214 KiB of unused CSS wastes bandwidth and delays FCP by 1.2 seconds.
How to Fix
Remove completely unused dashicons.min.css (35KB) since it's not needed on frontend. Use Asset CleanUp plugin to disable FontAwesome CSS on pages that don't need icons. Configure Porto theme to load only essential CSS modules for your specific page layouts.
0Needs Improvement
What This Score Means
A score of 62 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
120ms
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 62/100, primarily due to severe loading delays affecting user experience. The biggest problem is render-blocking JavaScript and CSS files that are preventing the page from displaying content quickly, causing a painfully slow Largest Contentful Paint of 6.7 seconds and taking over 12 seconds to become fully interactive. The site is also suffering from multiple page redirects (adding 840ms delay), oversized unoptimized images wasting 256 KiB of bandwidth, and massive amounts of unused CSS (214 KiB) and JavaScript code that's unnecessarily slowing down the page. Addressing these render-blocking resources and implementing proper caching could potentially improve loading times by over 3.5 seconds and dramatically enhance the user experience.
Other Optimization Recommendations
Eliminate Render-Blocking JavaScript Files
High Impact+25 points estimatedWhy It Matters:
Render-blocking JavaScript delays LCP by 3.7 seconds, preventing critical content from appearing quickly.
How to Fix:
Add async or defer attributes to non-critical JavaScript files in your WordPress theme. Move Ultimate VC Addons scripts (slick.min.js, custom.min.js) to load after page content. Use WP Rocket or Asset CleanUp plugin to automatically defer JavaScript execution until after DOM is ready.
Fix Redirect Chain Issues
Medium Impact+12 points estimatedWhy It Matters:
The redirect from tecu.it to www.tecu.it adds 840ms delay to every page load.
How to Fix:
Update all internal links to use https://www.tecu.it directly in WordPress settings and content. Configure your web server to serve the www version as primary instead of redirecting. Use Search Replace plugin to update any hardcoded non-www URLs in your database.
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
Fix Font Display Strategy
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
Optimize LCP Element Discovery
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
Remove Unused CSS and JavaScript
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
Eliminate Render Blocking CSS Files
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
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