Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize scraperapi.com
Poor font-display settings cause 50ms FCP delay and create invisible text during load.
Add font-display: swap to @font-face declarations for FontAwesome and custom fonts. Preload critical fonts using <link rel='preload'> in WordPress header. Use font metric overrides in CSS to reduce layout shift when fonts load.
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 WordPress site has poor performance with a score of 64/100, indicating significant user experience issues. The biggest problem is excessive JavaScript bloat - the site loads 329 KiB of unused JavaScript code, primarily from Google Analytics and tracking scripts, which delays page interactivity to a painful 16.8 seconds. The main thread is overwhelmed with 4.3 seconds of JavaScript processing, causing the largest content to appear after 4.4 seconds instead of the recommended 2.5 seconds. Removing or deferring unnecessary tracking scripts and optimizing JavaScript delivery could improve the score by 15-20 points and dramatically reduce loading times.
Why It Matters:
Unused JavaScript wastes 329 KiB and delays LCP by 300ms while blocking the main thread.
How to Fix:
Review Google Tag Manager container GTM-K4CBW6S and remove unused tracking tags. Use GTM's built-in tag assistant to identify firing triggers. Implement conditional loading for conversion tracking scripts only on relevant pages. Consider moving non-critical analytics to load after page interactive.
Why It Matters:
4.3 seconds of main-thread work creates 540ms of blocking time, preventing user interactions.
How to Fix:
Install WP Rocket or Autoptimize to defer JavaScript execution. Split large jQuery tasks into smaller chunks using setTimeout. Move heavy script evaluation to web workers where possible. Audit WordPress plugins for performance impact and remove unnecessary ones.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
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.