Website review, no card needed
foodpanda.ph website review
Visit site (opens in a new tab)Reviewed 28 October 202648 issues · 81 checks
This review found 48 issues worth fixing on foodpanda.ph, 20 of them high impact, across 81 checks. The most urgent: foodora.com adds 4.2 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.6 s |
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.7 s |
| Oct 24, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 647 ms |
| May 16, 2026 | 644 ms |
| May 23, 2026 | 654 ms |
| May 30, 2026 | 657 ms |
| Jun 6, 2026 | 666 ms |
| Jun 13, 2026 | 672 ms |
| Jun 20, 2026 | 680 ms |
| Jun 27, 2026 | 677 ms |
| Jul 4, 2026 | 678 ms |
| Jul 11, 2026 | 680 ms |
| Jul 18, 2026 | 682 ms |
| Jul 25, 2026 | 703 ms |
| Aug 1, 2026 | 719 ms |
| Aug 8, 2026 | 724 ms |
| Aug 15, 2026 | 720 ms |
| Aug 22, 2026 | 710 ms |
| Aug 29, 2026 | 672 ms |
| Sep 5, 2026 | 634 ms |
| Sep 12, 2026 | 593 ms |
| Sep 19, 2026 | 564 ms |
| Sep 26, 2026 | 566 ms |
| Oct 3, 2026 | 579 ms |
| Oct 10, 2026 | 599 ms |
| Oct 17, 2026 | 622 ms |
| Oct 24, 2026 | 638 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.1 s
1.7 s
2.2 s
2.8 s
3.3 s
3.9 s
4.5 s
Speed
foodora.com adds 4.2 s
4.2 sfoodora.com costs a phone 4.2 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused JavaScript
2.4 s · 961 KiBAbout 961 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.9 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Main-thread work: 12.8 s
A phone's processor spends 12.8 s on main-thread work while loading, 8.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
1.1 s · 183 KiBAbout 183 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 23). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (foodora.com, Facebook and Braze and others), adding 2.2 MB and 4.5 s of main-thread time.
Use efficient cache lifetimes
950 ms · 1.2 MB31 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.
Improve image delivery
820 KiB7 images could be 820 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Document request latency
650 msThe HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
641 msReduce initial server response time. Google estimates savings of 641 ms on a phone.
2,824 HTML elements
The page has 2,824 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 741 ms
741 msYour server takes 741 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 7.7 s
7.7 sReal visitors wait 7.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 975 ms
975 msReal visitors wait 975 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 17.0 s
17.0 sYour largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Get 50% off your first order with FREE delivery!”.
Total Blocking Time: 5.1 s
5.1 sScripts block taps and scrolling for 5.1 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 30.6 s
30.6 sThe page becomes fully interactive after 30.6 s. Good is under 3.8 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 647 ms to 638 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.6 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 188 requests
4.4 MBYour homepage downloads 4.4 MB in 188 requests on a phone: scripts 2.5 MB (47), images 1.0 MB (26) and fonts 333 KiB (9). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (712 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
1 image far larger than shown
142 KiB1 image is downloaded at several times the size a phone draws it, for example rlp-nc-banner-logo-mweb.webp at 592 px wide, shown at 140 px. Resized copies would save about 142 KiB.
About 1.3 g of CO₂ per visit
1.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.25 g of CO₂e: 150.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (3 elements)
Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Online Food Delivery from Restaurants in the Philippines | foodpanda”.
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 1 internal link
The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
4 checks passed
One H1 headline
Your main headline reads: “Food Delivery in the Philippines”.
Canonical URL set
The canonical URL is https://www.foodpanda.ph/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.foodpanda.ph/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
Some text only appears after JavaScript runs
38%The HTML your server sends has 1,200 of the 3,187 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.foodpanda.ph/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
Opted out of AI training for 1 crawler
robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Best practices
1 broken image
1 image failed to load on a phone, for example https://logo.page-source.com/resizeimage.ashx?ig=www.foodpanda.ph&sz=263422.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
54 of 54 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 3,187 words of copy
The homepage carries about 3,187 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Sign up”.
1 call to action
The homepage has 1 call to action, for example “Sign up for free delivery”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 2 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
35 other companies contacted
Loading the homepage contacts 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at foodpanda.ph, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on foodpanda.ph, including 25 speed issues, 6 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.