Optimize JavaScript Bundle Size

How to optimize lebgul.bcl.my

Generic SiteScore: 33/100Analyzed May 2026Re-analyze this site

Optimize JavaScript Bundle Size

High Impact+20 points estimated

Why It Matters

4.6 seconds of main thread blocking from excessive JavaScript prevents user interactions and delays page readiness.

How to Fix

Remove duplicate TinyMCE script loading (appears twice). Split large bundles and defer non-essential scripts like YouTube player and Facebook tracking until after page load. Use dynamic imports for components only needed on user interaction.

0Poor

What This Score Means

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

13.2s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

233ms
Needs Improvement

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.02
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 score of just 33/100, indicating major problems that are hurting user experience. The biggest issue is excessive JavaScript execution taking over 4.6 seconds, which is blocking the main thread and preventing users from interacting with the page for nearly 24 seconds. The site is also suffering from render-blocking resources that delay the first paint by 2.4 seconds, and has a massive 4MB+ payload with duplicated TinyMCE editor files and unused code. Reducing JavaScript execution time, removing duplicate resources, and deferring non-critical scripts could potentially improve the performance score by 40+ points and dramatically speed up page loading.

Other Optimization Recommendations

Eliminate Render Blocking Resources

High Impact+25 points estimated

Why It Matters:

Render blocking CSS is delaying first paint by 2.4 seconds and severely impacting user experience.

How to Fix:

Inline critical CSS for above-the-fold content directly in the HTML head. Defer non-critical CSS like forms.css and filament stylesheets using media='print' onload='this.media="all"'. Move JavaScript files to load after critical rendering path is complete.

Fix LCP Image Loading

High Impact+15 points estimated

Why It Matters:

The hero image has lazy loading applied which delays LCP by 3.9 seconds and hurts user perception.

How to Fix:

Remove loading='lazy' attribute from the hero image (VitaliQ image). Add fetchpriority='high' to prioritize loading. Ensure image dimensions are set to prevent layout shift and consider using a placeholder while loading.

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