Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize tutoriaux.excalibur.com
Main thread is blocked for 3.9 seconds with excessive style/layout work preventing user interactions and degrading INP.
Identify and eliminate forced reflows causing 89ms of blocking time. Defer non-critical JavaScript execution using async/defer attributes. Break up long-running tasks into smaller chunks using setTimeout or requestIdleCallback to allow browser breathing room.
A score of 82 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 website has good performance with a score of 82/100, but there's significant room for improvement. The biggest issue is excessive main-thread work (3.9 seconds) caused primarily by style and layout calculations, which creates a concerning 1,270ms delay for user interactions. The site is also wasting 33KB of unused CSS and has render-blocking stylesheets that delay initial page rendering by nearly 500ms. Cleaning up the CSS, optimizing the layout calculations, and deferring non-critical styles could easily push this site into the 90+ performance range and dramatically improve user responsiveness.
Why It Matters:
Two CSS files are blocking initial render for 484ms each, delaying both FCP and LCP metrics.
How to Fix:
Inline critical above-the-fold CSS directly in the HTML head section. Load non-critical CSS asynchronously using media='print' onload technique. Split the 51KB CSS bundle into critical and non-critical portions to reduce render blocking time.
Why It Matters:
33KB of unused CSS (82% waste) increases download time and parsing overhead without providing value.
How to Fix:
Use CSS coverage tools in Chrome DevTools to identify unused rules. Remove unused selectors from the main CSS bundle. Consider CSS tree-shaking tools or manual cleanup of framework CSS that's not being utilized on 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 Generic Speed Tests
Oversized images waste 458 KiB and delay LCP by 1,750ms, with the banner image being 4x larger than needed for its display size.
The redirect from zoho.com to www.zoho.com adds 780ms delay to both LCP and FCP, immediately impacting all Core Web Vitals.
JavaScript execution takes 4.5 seconds and blocks the main thread for 6.3 seconds, severely delaying user interactions and contributing 2,200ms to Total Blocking Time.
Logo image is 20x larger than needed and missing dimensions cause layout shifts affecting CLS.