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
CSS files are blocking initial page render for 7.8 seconds, preventing users from seeing content.
Use a WordPress optimization plugin like WP Rocket to defer non-critical CSS files. Inline critical above-the-fold CSS directly in HTML head. Move widget and sticky-loader CSS to load after initial render using media='print' onload technique.
A score of 58 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 issues with a score of 58/100. The biggest problem is extremely slow visual loading, with content taking 18.7 seconds to fully appear and 7.7 seconds for the largest element to load. The site is overloaded with render-blocking CSS and JavaScript files that prevent the page from displaying quickly, along with unoptimized fonts that delay text rendering by over 2 seconds. Reducing the number of CSS/JS files, optimizing font loading with proper display settings, and addressing the complex network dependency chain could dramatically improve load times and user experience.
Why It Matters:
Font loading blocks content display for 2.3 seconds, severely delaying First Contentful Paint.
How to Fix:
Add font-display: swap to your custom Poppins fonts in WordPress theme CSS. Preload critical font files by adding <link rel='preload'> tags for Poppins-Regular.woff2 and Poppins-SemiBold.woff. Consider using font-display: optional for non-critical font weights to prevent render blocking.
Why It Matters:
The largest content element isn't discoverable from initial HTML, causing unnecessary delay in loading.
How to Fix:
Add fetchpriority='high' attribute to your hero section background image or largest visible element. Ensure the LCP element is present in initial HTML rather than loaded via JavaScript. Move critical images above the fold out of lazy loading.
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.
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
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.