Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize mangabaka.org
Forced reflows cause layout thrashing that blocks the main thread and degrades user interaction responsiveness.
Review the Vue components causing reflows in your app chunks, particularly around DOM measurements. Batch DOM reads and writes in Vue lifecycle hooks. Use Vue's $nextTick() to defer DOM queries until after style changes are committed, preventing forced synchronous layout calculations.
A score of 60 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Vue-powered manga site has poor performance with a score of 60/100, indicating significant user experience issues. The biggest problem is extremely slow loading times, with your Largest Contentful Paint taking 6.6 seconds and First Contentful Paint at 4.6 seconds - both well beyond acceptable limits. The main culprits are oversized images (particularly a manga cover that's twice as large as needed), 50KB of unused JavaScript code, and inefficient caching of analytics scripts. Optimizing image sizes, removing unused JavaScript, and implementing proper caching could easily improve your score by 25+ points and dramatically speed up page loading for your users.
Why It Matters:
Oversized images waste 37KB and delay LCP by 600ms, significantly impacting your largest contentful paint score.
How to Fix:
Configure your image proxy to serve appropriately sized images based on display dimensions - the cover image should be 241x349, not 483x700. Implement Vue's responsive image components or use srcset attributes. Add proper image optimization middleware to automatically resize images based on viewport.
Why It Matters:
50KB of unused JavaScript delays both FCP and LCP by 150ms while blocking the main thread unnecessarily.
How to Fix:
Analyze the Datadog RUM bundle (28KB unused) and app chunks (22KB unused) to remove dead code. Use Vue's tree-shaking capabilities and dynamic imports for code splitting. Configure your build process to eliminate unused portions of third-party libraries like Datadog if monitoring isn't critical for this page.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Performance Analyses