Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize pulumi.com
Oversized images waste 263KB and poor cache headers force unnecessary re-downloads.
Implement responsive images using srcset to serve appropriate sizes for different viewports. Set proper cache headers with max-age of at least 31536000 (1 year) for static assets like images and fonts. Add explicit width and height attributes to prevent layout shifts during image loading.
A score of 59 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 poor performance with a score of 59/100, indicating significant user experience issues. The biggest problem is render-blocking CSS and JavaScript files that are delaying the First Contentful Paint and Largest Contentful Paint by nearly 5 seconds, making visitors wait far too long to see any content. The site is also suffering from oversized images that aren't properly optimized for their display size, inefficient caching that wastes 1.3MB of data on repeat visits, and a slow initial server response. Addressing the render-blocking resources first by deferring non-critical CSS/JS and optimizing image delivery could potentially improve load times by 4-5 seconds and boost the performance score significantly.
Why It Matters:
CSS files are blocking page rendering for 4.8 seconds, severely delaying both FCP and LCP.
How to Fix:
Inline critical CSS for above-the-fold content directly in the HTML head. Load non-critical CSS files asynchronously using media='print' onload="this.media='all'" technique. Consider using tools like Critical or PurgeCSS to extract and inline only essential styles.
Why It Matters:
The redirect chain from pulumi.com to www.pulumi.com adds 780ms delay to every Core Web Vital.
How to Fix:
Update all internal links and canonical URLs to point directly to https://www.pulumi.com/. Configure server redirects to be permanent (301) rather than temporary. Update DNS and CDN configurations to serve the www version as the primary domain.
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
The redirect chain from pulumi.com to www.pulumi.com adds 780ms delay to every Core Web Vital.
CSS files are blocking page rendering for 4.8 seconds, severely delaying both FCP and LCP.
96% of your CSS (163 KiB) and significant JavaScript (114 KiB) are unused, wasting bandwidth and blocking rendering.
Document latency of 5.3 seconds indicates severe server performance issues that delay all content loading.