LCP
Largest Contentful Paint
13.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Video Content Strategy
How to optimize daleelaqar.com
Optimize Video Content Strategy
High Impact+15 points estimated
Why It Matters
Video files consume 17.7 MB of bandwidth and the LCP element is a video that isn't properly optimized for discovery.
How to Fix
Add fetchpriority='high' to your LCP video element and ensure it's discoverable in the initial HTML. Implement proper poster images with appropriate dimensions. Consider using adaptive bitrate streaming or reduce video quality for mobile devices using Angular's responsive image techniques.
0Poor
What This Score Means
A score of 49 falls in the "Poor" 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
332ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.15
Needs Improvement
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Angular-powered real estate website has poor performance with a score of 49/100. The biggest problem is massive video files (17.6 MB total) that are unnecessarily loading on the homepage, causing the Largest Contentful Paint to suffer at 13.4 seconds - far beyond Google's recommended 2.5 seconds. The site is also experiencing significant layout shifts (0.15 CLS) due to web fonts loading late, and contains 592 KB of unused JavaScript code. Implementing video lazy loading, optimizing font delivery with proper fallbacks, and removing unused code could dramatically improve load times and user experience by several seconds.
Other Optimization Recommendations
Optimize Web Font Loading Strategy
High Impact+25 points estimatedWhy It Matters:
Web fonts cause significant layout shifts (CLS: 0.146) and delay content rendering by causing text to reflow.
How to Fix:
Implement font-display: swap in your CSS for Noto Sans Arabic fonts. Preload critical font variants using <link rel='preload'> in Angular's index.html. Consider using a font fallback strategy with size-adjust CSS property to minimize layout shifts.
Reduce Main Thread JavaScript Execution
High Impact+20 points estimatedWhy It Matters:
JavaScript execution blocks the main thread for 1.6 seconds, severely impacting Time to Interactive (14.0s) and user experience.
How to Fix:
Code-split your Angular application using lazy loading for feature modules. Remove unused JavaScript (592 KiB identified) by implementing tree-shaking and analyzing bundle with webpack-bundle-analyzer. Defer non-critical third-party scripts like Facebook Pixel and Smartlook until after page load.
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 Performance Analyses
Angular Performance Resources
Reduce Main Thread JavaScript Execution
JavaScript execution blocks the main thread for 1.6 seconds, severely impacting Time to Interactive (14.0s) and user experience.
Optimize Web Font Loading Strategy
Web fonts cause significant layout shifts (CLS: 0.146) and delay content rendering by causing text to reflow.
Eliminate Angular Layout Shifts
Multiple layout shifts (CLS: 0.135) occur from Angular components loading dynamically, especially the bottom property drawer.
Fix LCP Resource Load Delay
The LCP element experiences a 6-second resource load delay, making up 69% of the total LCP time of 8.7 seconds.