Optimize JavaScript Bundle Size

How to optimize newstore.webyan.sa

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

Optimize JavaScript Bundle Size

High Impact+18 points estimated

Why It Matters

Plugin.min.js contains 63KB of unused code and blocks main thread, causing poor user experience and delayed interactivity.

How to Fix

Remove unused JavaScript code from plugin.min.js (55% unused). Implement code splitting to load only required modules. Minify all JavaScript files to save additional 40KB. Use dynamic imports for non-critical features and defer loading until needed.

0Needs Improvement

What This Score Means

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

11.5s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

25ms
Good

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 Arabic e-commerce website has poor performance with a score of 56/100, indicating significant user experience issues. The biggest problem is extremely slow loading times - your First Contentful Paint takes 9.6 seconds and Largest Contentful Paint takes 11.5 seconds, which means visitors wait nearly 12 seconds before seeing meaningful content. The primary culprit is render-blocking CSS files that are delaying page rendering by over 9 seconds, combined with 184 KB of unused CSS code that's unnecessarily slowing down the site. Additionally, large font files (over 900 KB total) and unoptimized JavaScript are contributing to the sluggish performance, making immediate CSS optimization and font loading improvements critical for better user experience.

Other Optimization Recommendations

Eliminate Render Blocking CSS

High Impact+25 points estimated

Why It Matters:

Critical CSS files are blocking page render for 9.4 seconds, severely delaying FCP and LCP by 9.45 seconds.

How to Fix:

Inline critical above-the-fold CSS directly in the HTML head. Split large CSS files (main.rtl.css at 60KB, plugin.min.css at 87KB) into critical and non-critical parts. Load non-critical CSS asynchronously using media='print' onload='this.media="all"' technique. Remove unused CSS rules which account for 94-98% of these files.

Implement Font Loading Optimization

Medium Impact+8 points estimated

Why It Matters:

Large font files (466KB fa-thin-100.woff2, 328KB fa-solid-900.woff2) delay FCP by 100ms and cause layout shifts.

How to Fix:

Add font-display: swap to all @font-face declarations to show fallback text immediately. Preload only essential fonts using <link rel='preload' as='font'>. Subset Arabic fonts to include only required characters. Consider using system fonts for non-brand critical text 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

More Generic Speed Tests

Generic Performance Resources

Frequently Asked Questions