Eliminate Render-Blocking CSS

How to optimize payfast.greenn.com.br

Nuxt SiteScore: 67/100Analyzed February 2026Re-analyze this site

Eliminate Render-Blocking CSS

Medium Impact+12 points estimated

Why It Matters

Critical CSS files are blocking first paint, adding 300ms to FCP and delaying page visibility.

How to Fix

Use Nuxt's @nuxtjs/critters module to inline critical CSS automatically. Move non-critical CSS like Card.BwoSW8tZ.css and Whatsapp.xguJDDJ2.css to load asynchronously using media='print' onload='this.media="all"' technique. Remove unused 55KB from vue-tel-input.CX5yLeAC.css or load it conditionally.

0Needs Improvement

What This Score Means

A score of 67 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.

Core Web Vitals Analysis

LCP

Largest Contentful Paint

10.3s
Poor

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

112ms
Good

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.01
Good

Good: < 0.1

Measures visual stability - how much content shifts during page load

AI Performance Analysis

This Nuxt/Vue website has poor performance with a score of 67/100, indicating significant room for improvement. The biggest problem is an extremely slow Largest Contentful Paint of 10.3 seconds, primarily caused by a large, unoptimized product image that could save 606KB through modern formats (WebP/AVIF) and proper resizing. The site is also loading 175KB of unused JavaScript and has render-blocking CSS files that delay the initial page display by 300ms. Addressing the image optimization alone could improve load times by over 3 seconds, while cleaning up the unused code and implementing proper caching would further boost performance and user experience.

Other Optimization Recommendations

Optimize Image Delivery and Caching

High Impact+25 points estimated

Why It Matters:

The main product image is 608KB and poorly cached, directly causing the 10.3s LCP delay.

How to Fix:

Convert the product image from JPG to WebP/AVIF format for 90% size reduction. Resize images to match display dimensions (158x89px instead of 800x450px). Set proper cache headers with max-age=31536000 for the S3 images and implement CDN caching.

Remove Unused JavaScript Code

High Impact+18 points estimated

Why It Matters:

175KB of unused JavaScript creates 750ms delay and blocks critical rendering paths.

How to Fix:

Use Nuxt's tree-shaking by importing only needed components with auto-imports: false in nuxt.config.js. Split large bundles using dynamic imports with $lazy prefix for non-critical components. Remove unused dependencies from CHSsAhP0.js, CCEvibWK.js, and Dx0Omqdb.js files.

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

More Nuxt Speed Tests

Nuxt Performance Resources

Frequently Asked Questions