LCP
Largest Contentful Paint
16.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Network Dependency Chains
How to optimize partner.foodpanda.com
Fix Network Dependency Chains
High Impact+18 points estimated
Why It Matters
Critical resources are loading sequentially in 4-second chains instead of in parallel, severely impacting LCP.
How to Fix
Preload critical CSS and JavaScript files using <link rel='preload'> tags in the HTML head. Bundle critical CSS inline to eliminate render-blocking requests. Remove unused preconnect hints for d2xzidqie5hn2y.cloudfront.net and sentry.io domains.
0Poor
What This Score Means
A score of 33 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
340ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This foodpanda partner site has severe performance issues with a critically low score of 33/100. The biggest problem is an extremely slow server response time of 820ms, which is causing a devastating 16.7-second Largest Contentful Paint and making the page nearly unusable for visitors. The site is also bloated with 3.5MB of resources including 743KB of unused JavaScript code and inefficient resource loading that creates long dependency chains. Fixing the server response time alone could improve load speeds by 700ms, while removing unused code and optimizing the resource loading sequence could dramatically enhance user experience and bring this site back to acceptable performance levels.
Other Optimization Recommendations
Reduce Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
743 KiB of unused JavaScript is blocking page rendering and delaying LCP by 2.15 seconds.
How to Fix:
Remove unused Google Tag Manager scripts and optimize Material-UI bundle by importing only required components. Implement code splitting for authentication module using dynamic imports. Defer non-critical third-party scripts like analytics until after page load.
Optimize Server Response Time
High Impact+20 points estimatedWhy It Matters:
Initial server response takes 820ms, delaying all subsequent resource loading and Core Web Vitals.
How to Fix:
Implement server-side caching with Redis or Memcached to reduce database queries. Optimize database queries and add proper indexing. Consider using a CDN for static assets and enable gzip compression for HTML responses.
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 Server Response Time
Initial server response takes 820ms, delaying all subsequent resource loading and Core Web Vitals.
Reduce Unused JavaScript Code
743 KiB of unused JavaScript is blocking page rendering and delaying LCP by 2.15 seconds.
Optimize HTMX Library Usage
HTMX is triggering layout recalculations that could delay user interactions and hurt INP scores.
Optimize Speed Index Performance
Speed Index of 3.8s indicates slow visual content population, affecting user perceived performance despite good overall score.