Reduce JavaScript Bundle Size

How to optimize grabtravel.grab.com

Generic SiteScore: 32/100Analyzed April 2026Re-analyze this site

Reduce JavaScript Bundle Size

High Impact+20 points estimated

Why It Matters

Unused JavaScript accounts for 358KB of waste, delaying LCP by 900ms and blocking main thread execution.

How to Fix

Implement code splitting to load only necessary JavaScript for each route. Remove 64% unused code from vendor-primevue bundle by importing only required components. Use dynamic imports for non-critical features like analytics and tracking scripts.

0Poor

What This Score Means

A score of 32 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

LCP

Largest Contentful Paint

10.8s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

858ms
Poor

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 Grab Travel website has severe performance issues with a critically low score of 32/100. The biggest problem is render-blocking CSS files that are preventing the page from displaying content for over 10 seconds, with First Contentful Paint taking 10.4 seconds and Largest Contentful Paint at 10.8 seconds. The main CSS file contains 98% unused code (57KB wasted) and is blocking the initial render, while the massive 1.7MB JavaScript bundle takes too long to download and execute. Immediately addressing the render-blocking resources by deferring non-critical CSS, removing unused code, and optimizing the enormous network payload could potentially improve the performance score by 40+ points and dramatically reduce load times from over 10 seconds to under 3 seconds.

Other Optimization Recommendations

Eliminate Render Blocking Resources

High Impact+25 points estimated

Why It Matters:

CSS files are blocking the initial page render for 480ms and delaying First Contentful Paint.

How to Fix:

Inline critical CSS for above-the-fold content directly in the HTML head. Use media queries or 'preload' with onload handler for non-critical CSS. Remove 98% unused CSS from main-HC7l7DEj.css by extracting only styles needed for initial viewport.

Optimize Image Delivery Performance

Medium Impact+10 points estimated

Why It Matters:

Oversized and unoptimized images waste 116KB and delay LCP by 150ms with poor user experience.

How to Fix:

Convert PNG images to WebP format for 30-50% size reduction. Resize loyalty program logo from 400x400 to actual display size of 63x63. Add explicit width and height attributes to prevent layout shifts and improve CLS.

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 Generic Speed Tests

Generic Performance Resources

Frequently Asked Questions