LCP
Largest Contentful Paint
6.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Long-term Asset Caching
How to optimize dmsuniverse.com
Implement Long-term Asset Caching
Medium Impact+12 points estimated
Why It Matters
Short 4-hour cache lifetime wastes 217 KiB on repeat visits, slowing LCP by 1050ms.
How to Fix
Configure your build system to add content hashes to asset filenames for cache busting. Set cache headers to 1 year for hashed assets (main-website-*.js, flags@2x-*.webp). Update server configuration to serve assets with 'Cache-Control: public, max-age=31536000, immutable' headers.
0Needs Improvement
What This Score Means
A score of 72 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
INP
Interaction to Next Paint
53ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.03
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website has concerning performance issues with a score of 72/100, particularly struggling with loading speed. The biggest problem is an extremely slow Largest Contentful Paint of 6 seconds, meaning users wait far too long to see the main content - this should be under 2.5 seconds for good performance. The site is also loading 77KB of unnecessary JavaScript code that isn't being used, which contributes to the 6-second Time to Interactive delay. Quick wins include removing unused JavaScript, optimizing image compression (could save 34KB), and implementing better caching strategies, which together could significantly improve load times and user experience.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
77 KiB of unused JavaScript is delaying LCP by 300ms and blocking the main thread.
How to Fix:
Analyze your bundle with webpack-bundle-analyzer to identify unused PostHog and survey features. Remove unused imports from posthog-featureflags.ts and posthog-core.ts. Implement code splitting to load survey extensions only when needed. Consider lazy loading analytics scripts after critical content renders.
Fix Forced Reflow Performance
High Impact+15 points estimatedWhy It Matters:
JavaScript is causing 34ms of forced reflows in main-website-41slwGrA.js, blocking user interactions.
How to Fix:
Batch DOM reads and writes in your JavaScript code at line 24, column 5170. Replace synchronous offsetWidth/offsetHeight queries with getBoundingClientRect() calls outside of style changes. Use requestAnimationFrame for any geometry calculations that follow DOM mutations.
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
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Fix Forced Reflow Performance
JavaScript is causing 34ms of forced reflows in main-website-41slwGrA.js, blocking user interactions.
Eliminate Unused JavaScript Code
77 KiB of unused JavaScript is delaying LCP by 300ms and blocking the main thread.
Implement Proper Browser Caching
No cache headers are set for critical assets totaling 1.35MB, forcing full downloads on every visit.
Implement Proper Asset Caching
No cache headers on static assets forces unnecessary re-downloads and slows repeat visits.