Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize asisto.io
Font files create a 423ms critical chain dependency that delays content rendering and impacts Speed Index.
Preload critical fonts using <link rel='preload' as='font'> for jetbrains-mono-variable.woff2 and fraunces-variable-italic.woff2. Add font-display: swap to CSS @font-face rules. Consider subsetting fonts to reduce file sizes if only specific characters are needed.
A score of 97 falls in the "Good" 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 performs exceptionally well with a score of 97/100, indicating excellent optimization overall. The biggest opportunity for improvement is optimizing image delivery, specifically a portrait image that's being served at nearly double the size needed (960x1163 pixels vs. 297x359 display size), which wastes about 85 KB of bandwidth. The site also experiences some forced reflows in JavaScript that could be causing minor performance hiccups, and there's a small delay in font loading that contributes to a 4.0 second Speed Index. Despite these minor issues, the site is already performing at a very high level and would benefit most from implementing responsive images to serve appropriately-sized versions based on display dimensions.
Why It Matters:
The portrait image is oversized by 87KB, wasting bandwidth and potentially impacting perceived load performance.
How to Fix:
Resize the sydney-portrait image from 960x1163 to match its display size of 297x359 pixels. Use responsive images with multiple sizes in your srcset attribute. Consider using image optimization tools like ImageOptim or implementing automatic resizing in your build process.
Why It Matters:
JavaScript is causing 48.7ms of forced reflows, blocking the main thread and degrading user experience.
How to Fix:
Identify code that reads geometric properties after DOM changes and batch these operations. Use requestAnimationFrame for layout-triggering operations. Cache DOM measurements to avoid repeated queries of offsetWidth, clientHeight, or similar properties.
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
JavaScript is causing 48.7ms of forced reflows, blocking the main thread and degrading user experience.
The portrait image is oversized by 87KB, wasting bandwidth and potentially impacting perceived load performance.
91% of your CSS is unused, adding 150ms to LCP and blocking initial render for 1.5 seconds.
The hero brand image lacks fetchpriority=high, missing an opportunity to prioritize critical resource loading.