Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize zifornd.com
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
Set proper cache headers for video files (home-banner-animation.webm and manufacturing videos) with max-age of 31536000 (1 year). Configure CDN caching rules in NitroPack or CloudFlare for .webm files. Consider compressing videos further or using different formats for mobile devices.
A score of 64 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 64/100, primarily due to slow loading of critical resources. The biggest problem is render-blocking JavaScript files that are delaying the First Contentful Paint by 750ms, while also suffering from extremely large video files (over 70MB total) that lack proper caching. The site is experiencing forced reflows that hurt user experience, and there's significant unused JavaScript and CSS that could be removed to improve loading times. Implementing proper caching for video content, deferring non-critical JavaScript, and removing unused code could dramatically improve both the performance score and user experience.
Why It Matters:
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
How to Fix:
Add async or defer attributes to non-critical JavaScript files, especially jQuery and Elementor scripts. Move jQuery to load after initial render using wp_enqueue_script with 'defer' parameter. Configure NitroPack to defer JavaScript execution until after FCP.
Why It Matters:
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
How to Fix:
Audit Google Tag Manager containers (GTM-TZ239QN and GTM-MB2LXBPM) to remove unused tags and triggers. Consolidate duplicate GTM containers if possible. Use Partytown to run analytics scripts in web workers to avoid blocking main thread execution.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
18MB of video content lacks proper caching headers, forcing re-downloads on repeat visits and contributing to the 5-second LCP.
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.