Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize zidianpartners.io
Custom fonts block text rendering for 340ms, delaying First Contentful Paint and creating invisible text periods.
Add font-display: swap to Inter and FunnelDisplay fonts in your WordPress theme's CSS. Use font-face declarations with fallback fonts. Consider using system fonts for body text or preload critical font files in the <head> section.
A score of 67 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 WordPress site has poor performance with a score of 67/100, primarily due to extremely slow loading times that hurt user experience. The biggest problem is the Largest Contentful Paint taking 6.8 seconds and Time to Interactive at 11.2 seconds, caused by render-blocking JavaScript (especially jQuery) that delays the page by an estimated 2.2 seconds. The site is also loading 248 KiB of unused JavaScript from HubSpot integrations and has inefficient caching that wastes 189 KiB of bandwidth on repeat visits. Fixing the render-blocking scripts, removing unused JavaScript, and implementing proper caching could dramatically improve load times and boost the performance score by 25+ points.
Why It Matters:
Blocking JavaScript delays page rendering by 2.2 seconds and prevents user interactions for over 11 seconds.
How to Fix:
Defer jQuery and non-critical JavaScript using WP Rocket or Asset CleanUp Pro. Remove unused JavaScript from HubSpot (248 KiB unused). Move render-blocking scripts to load after critical content using async/defer attributes in your WordPress theme.
Why It Matters:
Images without explicit dimensions cause layout shifts and delay LCP by preventing proper space reservation.
How to Fix:
Add width and height attributes to all logo images in your WordPress gallery blocks. Use responsive image techniques with srcset for team images. Consider using Elementor's built-in image optimization settings or install EWWW Image Optimizer plugin.
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 WordPress Speed Tests
The 2.6MB artwork image is oversized for display (1863x2560 served for 623x856) and poorly compressed, causing massive LCP delays.
The 700ms server response time delays all page resources and directly impacts both LCP and FCP by 600ms each.
The LCP image has 5.3 seconds of resource load delay and lazy loading prevents immediate discovery, causing the 16.7s LCP time.
Images without width/height attributes cause layout shifts as they load, negatively impacting CLS scores.