LCP
Largest Contentful Paint
6.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Font Loading Strategy
How to optimize ormimaq.com.br
Optimize Font Loading Strategy
High Impact+18 points estimated
Why It Matters
Custom fonts are causing 840ms delay in FCP and creating invisible text periods during load.
How to Fix
Add font-display: swap to your Woodmart theme's custom fonts in wp-content/themes/woodmart/fonts/. Preload critical font files using <link rel='preload'> in your theme's header.php. Consider using system fonts as fallbacks with font metric overrides.
0Needs Improvement
What This Score Means
A score of 60 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
97ms
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 60/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 6.2 seconds (should be under 2.5 seconds), caused primarily by render-blocking CSS files that delay the initial page display by nearly 9 seconds. The site is also bloated with 99 KB of unused CSS from the Woodmart theme and suffers from forced reflows that waste processing time. To improve performance, the site needs to defer non-critical CSS, minify the main stylesheet (saving 18 KB), optimize font loading, and reduce the massive amount of unused code - these changes could potentially improve the performance score by 30+ points and dramatically enhance user experience.
Other Optimization Recommendations
Eliminate Render Blocking CSS Files
High Impact+25 points estimatedWhy It Matters:
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
How to Fix:
Use a WordPress optimization plugin like WP Rocket or Autoptimize to defer non-critical CSS. Inline critical above-the-fold CSS directly in the HTML. Consider removing unused Woodmart theme CSS modules that aren't needed for your specific pages.
Remove Unused CSS and JavaScript
Medium Impact+12 points estimatedWhy It Matters:
99KB of unused CSS and 29KB of unused JavaScript are unnecessarily bloating your page and slowing load times.
How to Fix:
Use Asset CleanUp or Perfmatters to disable unused WordPress plugins and theme modules on specific pages. Remove the unused Swiper.js library (96% unused) and minimize Elementor CSS by only loading required widgets. Audit and remove any unused WooCommerce features.
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
Remove Unused Divi CSS and JavaScript
52KB of unused CSS and 74KB of unused JavaScript increase page weight and slow down parsing without providing value.
Compress and Resize Hero Image
The header logo is 51KB larger than needed and wastes bandwidth while potentially delaying LCP.
Optimize Web Font Loading Strategy
Web fonts cause significant layout shifts (CLS: 0.139) and delay content rendering, directly impacting user experience.
Remove Unused Divi CSS/JavaScript
84% of your CSS (52KB) and 66% of Divi JavaScript (74KB) is unused, slowing down page load times.