Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize turczynski.com
Render-blocking CSS is delaying First Contentful Paint by 160ms and preventing faster page rendering.
Extract above-the-fold CSS styles and inline them directly in the HTML head. Use tools like Critical or Critters to automatically identify critical CSS. Load the remaining CSS asynchronously using media='print' onload technique or preload with rel='preload'.
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 website has poor performance with a score of 60/100, indicating significant room for improvement. The biggest problem is excessive unused JavaScript, which is wasting 233 KB of data and slowing down page loading by over a second - this is the primary culprit behind the very slow 7.3-second Largest Contentful Paint and 4.5-second First Contentful Paint times. The site is also suffering from render-blocking CSS that could save another 160ms if optimized, and images that are unnecessarily large for their display size. Removing or deferring unused JavaScript code and properly sizing images would likely improve the performance score by 15-20 points and dramatically enhance the user experience.
Why It Matters:
233 KiB of unused JavaScript is delaying LCP by 1.35 seconds and blocking user interactions.
How to Fix:
Analyze your bundled JavaScript to identify unused code using webpack-bundle-analyzer. Implement code splitting to load only necessary components initially. Remove or defer Google Analytics and other tracking scripts until after page load. Consider tree-shaking to eliminate dead code from your build process.
Why It Matters:
The navigation logo is 81KB but displays at only 56x56 pixels, wasting bandwidth and delaying LCP by 350ms.
How to Fix:
Resize the logo image from 2362x2362 to the actual display size of 56x56 pixels using an image editor. Convert to WebP format for better compression. Generate multiple sizes for different device pixel ratios using responsive images with srcset attribute.
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 backdrop video poster image can save 24KB (55% reduction) and improve LCP by 150ms.
JavaScript dependency chain takes 1.3 seconds to complete, directly impacting both FCP (3.2s) and LCP (3.5s).
104 KiB of unused JavaScript is delaying LCP by 150ms and blocking the main thread unnecessarily.
The navigation logo is 81KB but displays at only 56x56 pixels, wasting bandwidth and delaying LCP by 350ms.