Remove Unused JavaScript Code

How to optimize profile.asa.pages.dev

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

Remove Unused JavaScript Code

High Impact+15 points estimated

Why It Matters

48% of your JavaScript bundle (167KB) is unused, wasting bandwidth and blocking page interactions.

How to Fix

Use webpack-bundle-analyzer or similar tools to identify unused code in your bundle. Implement code splitting to load only required modules initially. Use dynamic imports for features that aren't immediately needed. Consider tree-shaking to eliminate dead code during build.

0Poor

What This Score Means

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

3.8s
Needs Improvement

Good: < 2.5s

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

INP

Interaction to Next Paint

296ms
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 42/100, taking an unacceptable 26 seconds to become fully interactive for users. The biggest problem is excessive JavaScript blocking the main thread for nearly 23 seconds, with almost half (167 KB) of the JavaScript code being unused and unnecessary. The site also suffers from render-blocking CSS and font files that delay initial page rendering by over a second. Removing unused JavaScript, optimizing the loading sequence of CSS and fonts, and reducing main-thread work could dramatically improve the user experience and boost the performance score by 30+ points.

Other Optimization Recommendations

Eliminate Render Blocking Resources

High Impact+18 points estimated

Why It Matters:

CSS and font requests are delaying your LCP by 1,270ms, directly impacting page load speed.

How to Fix:

Inline critical CSS directly in the HTML head section to remove the blocking request. Use font-display: swap on Google Fonts and consider self-hosting the Inter font files. Defer non-critical CSS using media='print' onload='this.media="all"' technique.

Remove Unused Preconnect Hints

Medium Impact+8 points estimated

Why It Matters:

Unused preconnects to api.lanyard.rest and cdn.discordapp.com waste browser resources without providing benefits.

How to Fix:

Remove preconnect links for api.lanyard.rest and cdn.discordapp.com from your HTML head section. Only keep preconnects for origins you actually request during initial page load. Consider lazy loading or conditionally connecting to these services only when needed.

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