Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize app.dev.viact.net
CSS and JavaScript files are blocking initial page render, delaying both FCP and LCP by 1.75 seconds.
Inline critical CSS for above-the-fold content directly in HTML. Move non-critical CSS like video-react.css to load asynchronously using media='print' onload technique. Defer the Autodesk viewer CSS (60KB) until the 3D viewer component is actually needed by the user.
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.
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 app has poor performance with a score of 42/100, indicating significant user experience issues. The biggest problem is an enormous amount of unused JavaScript (7.6 MB of wasted code) that's blocking the page and causing a painfully slow Time to Interactive of over 61 seconds. The site is loading massive libraries for PDFs and 3D viewers that aren't being used, while also suffering from render-blocking CSS files and inefficient caching. Removing unused JavaScript bundles and implementing code splitting could dramatically improve load times and reduce the current 2.8-second blocking time that's preventing users from interacting with the page.
Why It Matters:
7.6MB of unused JavaScript is delaying LCP by 1.05 seconds and blocking user interactions for 2.77 seconds.
How to Fix:
Implement code splitting to load PDF and Excel libraries only when needed. Use dynamic imports for pdfmake (853KB) and Autodesk viewer (754KB unused). Configure webpack to create separate chunks for these heavy libraries and load them on-demand when users access those features.
Why It Matters:
JavaScript is forcing expensive layout recalculations that block the main thread and degrade user experience.
How to Fix:
Batch DOM reads and writes to avoid layout thrashing in your fingerprinting code. Cache geometric properties like offsetWidth instead of querying them repeatedly. Use requestAnimationFrame for DOM measurements and consider replacing @fingerprintjs/fingerprintjs with a lighter alternative or lazy-load it after critical rendering is complete.
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
Font files create a 423ms critical chain dependency that delays content rendering and impacts Speed Index.
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.