Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize topbusca.com.br
The main image wastes 471KB using outdated PNG format and oversized dimensions, significantly impacting page load performance.
Install ShortPixel or Imagify to automatically convert the hero image to WebP/AVIF format. Use WordPress responsive images by serving 671x377px version instead of 768x432px. Add explicit width and height attributes to prevent layout shift.
A score of 100 falls in the "Good" 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 achieves a perfect performance score of 100/100, indicating excellent overall optimization. However, there are still some technical improvements that could enhance user experience further: the main image is unnecessarily large at 471 KiB and could be reduced by converting to modern formats like WebP and properly sizing it for display. Additionally, render-blocking CSS files are delaying initial page paint by an estimated 370ms, which could be resolved by inlining critical CSS or deferring non-essential stylesheets. Despite the perfect score, addressing these image optimization and render-blocking issues would make the site even faster and more efficient.
Why It Matters:
Critical CSS files are blocking first paint and delaying LCP by 350ms, preventing users from seeing content quickly.
How to Fix:
Use a WordPress optimization plugin like WP Rocket or LiteSpeed Cache to inline critical CSS. Load non-critical CSS asynchronously using media='print' onload technique. Consider combining the two CSS files (header.min.css and ucss file) to reduce HTTP requests.
Why It Matters:
JavaScript is causing 152ms of forced reflows by reading layout properties after DOM changes, blocking the main thread.
How to Fix:
Audit WordPress plugins for DOM manipulation code that reads offsetWidth/height properties. Batch DOM reads before writes using requestAnimationFrame. Consider deferring non-critical JavaScript that queries geometric properties until after initial render.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
JavaScript is causing 152ms of forced reflows by reading layout properties after DOM changes, blocking the main thread.
JavaScript is forcing layout recalculations causing 40ms of blocking time.
The main image wastes 482KB and could significantly improve perceived performance.
Critical CSS files are blocking first paint and delaying LCP by 350ms, preventing users from seeing content quickly.