Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize turczynski.com
A redirect from turczynski.com to www.turczynski.com wastes 780ms and delays both LCP and FCP by 800ms each.
Configure your DNS/hosting provider to serve content directly from the canonical URL (www.turczynski.com). Update all internal links to point directly to the www version. Set up a 301 redirect at the server level if the non-www version must redirect.
A score of 80 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 80/100, but there are some significant opportunities for improvement. The biggest issue is a redirect from the non-www to www version of the site, which wastes 780ms and delays both First Contentful Paint (3.2s) and Largest Contentful Paint (4.1s). Removing this redirect and reducing unused JavaScript (which could save 81KB and 450ms) would have the most immediate impact on loading speed. Additionally, optimizing server response time and improving image compression could further enhance the user experience and push the performance score into the excellent range.
Why It Matters:
81KB of unused JavaScript delays LCP by 450ms and wastes bandwidth on every page load.
How to Fix:
Audit your React and markdown processing bundles to identify unused code. Use tree-shaking to eliminate dead code from markdown-jpoeBJsD.js (71% unused) and react-Bd5gNP4v.js (51% unused). Consider code-splitting to load JavaScript modules only when needed. Use dynamic imports for non-critical functionality.
Why It Matters:
Slow document request latency adds 60ms to both LCP and FCP, impacting perceived performance.
How to Fix:
Enable gzip/brotli compression on your server for HTML responses. Optimize your server configuration to reduce Time to First Byte (TTFB). Consider using a CDN to serve content closer to users. Review server-side processing to eliminate unnecessary delays.
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
Total blocking time of 530ms and max potential FID of 540ms severely impacts user interaction responsiveness.
Oversized images are wasting 31KB bandwidth and delaying LCP by 150ms with poor mobile performance.
Slow document request latency adds 60ms to both LCP and FCP, impacting perceived performance.
Main thread is blocked for 4.6 seconds by script evaluation, preventing user interactions and delaying Time to Interactive.