Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize uticket.com.br
LCP image has 5.8 second resource load delay because it's not discoverable in initial HTML.
Move the hero image (img.uticket.com.br/event/01LSQUKU4KINFH/l) from JavaScript-rendered content to static HTML. Add fetchpriority='high' attribute to the LCP image element. Preload the image using <link rel='preload' as='image'> in the document head.
A score of 27 falls in the "Poor" 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 event ticketing website has severe performance issues with a critically low score of 27/100. The biggest problem is an enormous amount of unused JavaScript (1,285 KiB) that's blocking the page from loading quickly, causing the Largest Contentful Paint to take a devastating 21.7 seconds and First Contentful Paint to reach 7.4 seconds. The site is also suffering from poor caching strategies and inefficient network requests that create long dependency chains, with Google Fonts taking nearly 6 seconds to load. Removing unused JavaScript code, implementing better caching policies, and optimizing the main JavaScript bundle could potentially improve the score by 40+ points and dramatically reduce load times from over 20 seconds to under 5 seconds.
Why It Matters:
Unused JavaScript (1,285 KiB) is blocking main thread for 4.3 seconds and delaying LCP by 6.75 seconds.
How to Fix:
Use webpack-bundle-analyzer to identify unused code in main.60c52c31.js. Implement code splitting to load only critical JavaScript initially. Remove unused polyfills and use modern ES6+ features for supported browsers. Consider lazy loading non-critical components.
Why It Matters:
Short cache lifetimes (4 hours for main JS) force unnecessary re-downloads and slow repeat visits.
How to Fix:
Configure your web server to cache static assets (JS, CSS, images) for at least 1 year with cache-control headers. Use content hashing in filenames to enable safe long-term caching. Set up CDN caching for third-party resources like Google Fonts and Facebook scripts.
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 Generic Speed Tests
Images without explicit dimensions cause layout shifts and degrade user experience.
Your LCP element has a 2.76 second render delay, causing the 18.4 second LCP time.
1,329 KiB of unused JavaScript is delaying LCP by 6.15 seconds and blocking user interactions.
Missing image dimensions can cause layout shifts, and missing preconnects delay third-party resource loading.