LCP
Largest Contentful Paint
18.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Image Dimensions Properties
How to optimize uticket.com.br
Add Image Dimensions Properties
Medium Impact+8 points estimated
Why It Matters
Images without explicit dimensions cause layout shifts and degrade user experience.
How to Fix
Add width='64' height='64' attributes to all your category images (festas.webp, religiosos.webp, gastronomicos.webp, etc.). Use CSS aspect-ratio property as a fallback for responsive behavior. Reserve space for dynamically loaded images using min-height in CSS. This prevents content from jumping as images load.
0Poor
What This Score Means
A score of 37 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
278ms
Needs Improvement
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 website has severe performance issues with a critically low score of 37/100. The biggest problem is an extremely slow Largest Contentful Paint of 18.4 seconds, primarily caused by over 1.3MB of unused JavaScript that's blocking the page from loading efficiently. The site is also loading massive amounts of unnecessary code - nearly 3MB total - with most of it going unused, while heavy JavaScript execution is keeping the main thread busy for 3 seconds. Removing unused JavaScript, optimizing the main bundle size, and implementing proper code splitting could potentially improve load times by 6+ seconds and dramatically enhance user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
1,329 KiB of unused JavaScript is delaying LCP by 6.15 seconds and blocking user interactions.
How to Fix:
Analyze your main.60c52c31.js bundle using webpack-bundle-analyzer to identify unused dependencies. Remove or lazy-load unused Google Tag Manager scripts. Split your JavaScript into smaller chunks using code splitting to load only critical code initially. Consider removing unused features from your main bundle.
Fix Element Render Delay
High Impact+20 points estimatedWhy It Matters:
Your LCP element has a 2.76 second render delay, causing the 18.4 second LCP time.
How to Fix:
Move critical CSS inline to eliminate render-blocking stylesheets. Preload key resources that affect your LCP element (the 'Preços' link). Optimize the main thread work by deferring non-critical JavaScript execution until after the LCP element renders. Reduce DOM complexity around your navigation elements.
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 Generic Speed Tests
Generic Performance Resources
Fix Element Render Delay
Your LCP element has a 2.76 second render delay, causing the 18.4 second LCP time.
Remove Unused JavaScript Code
1,329 KiB of unused JavaScript is delaying LCP by 6.15 seconds and blocking user interactions.
Add Image Dimensions and Preconnects
Missing image dimensions can cause layout shifts, and missing preconnects delay third-party resource loading.
Optimize LCP Image Discovery
The LCP image has a 4.5 second resource load delay because it's not discoverable in the initial HTML.