Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize ormimaq.com.br
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
Use WP Rocket or Asset CleanUp to remove unused Woodmart theme CSS (101KB savings). Audit the swiper.min.js library showing 96% unused code. Consider code splitting or conditional loading for unused JavaScript components.
A score of 59 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This WordPress site has poor performance with a score of 59/100, primarily due to excessive unused CSS that's blocking initial page rendering and delaying content visibility. The biggest issue is the main stylesheet (style.css) which contains 99 KiB of unused CSS rules, causing a 4.4-second delay in First Contentful Paint and contributing to a sluggish 6.5-second Largest Contentful Paint. Additionally, the site is loading 29 KiB of unused JavaScript from the Swiper library and has inefficient font loading that adds nearly 900ms of delay. Cleaning up the CSS by removing unused rules, optimizing JavaScript loading, and implementing proper font-display strategies could dramatically improve performance and boost the score by 30+ points.
Why It Matters:
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
How to Fix:
Add fetchpriority='high' to the hero section background image or container. Move critical CSS inline for above-the-fold content. Ensure LCP element styling is not dependent on external stylesheets that delay rendering.
Why It Matters:
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
How to Fix:
Add font-display: swap to @font-face declarations in your theme CSS. Preload critical Woodmart fonts using <link rel='preload'>. Use font fallbacks with size-adjust property to minimize layout shift during font swaps.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
194KB of unused JavaScript creates 850ms of blocking time and extends Time to Interactive to 9.6 seconds.
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.