LCP
Largest Contentful Paint
12.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Font Display Blocking Issue
How to optimize sidf.gov.sa
Fix Font Display Blocking Issue
Medium Impact+8 points estimated
Why It Matters
Custom font loading blocks text rendering for 400ms, delaying First Contentful Paint.
How to Fix
Add font-display: swap to your @font-face declaration for the saudi_riyal font. Preload the critical font file in the document head. Consider using font metric overrides to reduce layout shift when the font loads.
0Needs Improvement
What This Score Means
A score of 63 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
218ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.01
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website has poor performance with a score of 63/100, primarily due to excessive JavaScript blocking the main thread for 2 seconds and causing a very slow Largest Contentful Paint of 12.9 seconds. The biggest opportunity for improvement is reducing unused JavaScript, which could save 518 KiB and improve loading by over 3 seconds, followed by optimizing the main image that takes over 7 seconds to load due to resource delays. Additional quick wins include removing 16 KiB of unused CSS, implementing proper font display settings to save 400ms, and updating the JavaScript build process to avoid unnecessary polyfills that add 13 KiB of legacy code. These optimizations could dramatically improve user experience and push the performance score well into the good range.
Other Optimization Recommendations
Reduce Unused JavaScript Bundle Size
High Impact+25 points estimatedWhy It Matters:
Unused JavaScript accounts for 518 KiB and delays LCP by 3.1 seconds while blocking main thread work.
How to Fix:
Implement code splitting in your Next.js build to break large chunks into smaller, route-specific bundles. Remove or defer the Google Tag Manager script (65KB unused). Use Next.js dynamic imports for non-critical components to reduce initial bundle size.
Optimize LCP Image Loading Strategy
High Impact+20 points estimatedWhy It Matters:
The hero image has a 7.3-second delay (2.3s load delay + 5s duration) causing the 12.9s LCP score.
How to Fix:
Preload the hero image using <link rel='preload' as='image'> in the document head. Optimize the image compression to reduce the 170KB file size. Consider using a smaller, optimized version specifically for above-the-fold display.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Optimize LCP Image Loading Strategy
The hero image has a 7.3-second delay (2.3s load delay + 5s duration) causing the 12.9s LCP score.
Reduce Unused JavaScript Bundle Size
Unused JavaScript accounts for 518 KiB and delays LCP by 3.1 seconds while blocking main thread work.
Minify and Reduce JavaScript
Unminified JavaScript wastes 1.4 MB and causes 2.3 seconds of blocking execution time.
Optimize Image Delivery and Sizing
Large unoptimized images cause 10.4 MB of wasted bandwidth and trigger major layout shifts affecting CLS.