LCP
Largest Contentful Paint
6.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix LCP Resource Load Delay
How to optimize staging.daleelaqar.com
Fix LCP Resource Load Delay
High Impact+20 points estimated
Why It Matters
The LCP element experiences a 6-second resource load delay, making up 69% of the total LCP time of 8.7 seconds.
How to Fix
Add preconnect for api.staging.daleelaqar.com which shows 465ms potential savings. Implement resource hints for critical image CDN endpoints. Move the LCP image (property card image) to eager loading with fetchpriority='high' and ensure it's not lazy loaded.
0Poor
What This Score Means
A score of 39 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
313ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.14
Needs Improvement
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Angular real estate site has poor performance with a score of 39/100. The biggest problem is excessive JavaScript execution taking 2.8 seconds, which is blocking user interactions and causing a 9.1-second delay before the page becomes fully interactive. The site is loading too many JavaScript files in a chain reaction (over 10 seconds of network dependencies), and there's significant layout shifting as content loads, making the page feel unstable. Reducing unused JavaScript code (176 KiB could be removed) and optimizing the resource loading sequence would be the most impactful fixes to improve user experience.
Other Optimization Recommendations
Reduce Angular JavaScript Bundle Size
High Impact+25 points estimatedWhy It Matters:
Excessive JavaScript execution (2.8s) severely blocks the main thread and delays Time to Interactive by 9.1 seconds.
How to Fix:
Implement Angular lazy loading for route modules to reduce the initial bundle. Use Angular CLI's built-in code splitting with dynamic imports for large components. Remove unused code from main.js (877KB) and optimize the 460.js chunk (625KB) through tree shaking and dead code elimination.
Eliminate Angular Layout Shifts
Medium Impact+8 points estimatedWhy It Matters:
Multiple layout shifts (CLS: 0.135) occur from Angular components loading dynamically, especially the bottom property drawer.
How to Fix:
Reserve space for the app-bottom-drawer component with fixed CSS dimensions before Angular renders it. Add skeleton placeholders for the search input component during initialization. Use Angular's OnPush change detection strategy to prevent unnecessary re-renders that cause layout shifts.
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 Angular Speed Tests
Angular Performance Resources
Optimize Video Content Strategy
Video files consume 17.7 MB of bandwidth and the LCP element is a video that isn't properly optimized for discovery.
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.