Website review, no card needed
foodline.sg website review
Visit site (opens in a new tab)Reviewed 23 October 202649 issues · 99 checks
This review found 49 issues worth fixing on foodline.sg, 22 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 188 ms |
| May 9, 2026 | 183 ms |
| May 16, 2026 | 176 ms |
| May 23, 2026 | 172 ms |
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 171 ms |
| Jun 20, 2026 | 175 ms |
| Jun 27, 2026 | 173 ms |
| Jul 4, 2026 | 174 ms |
| Jul 11, 2026 | 175 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 172 ms |
| Aug 8, 2026 | 178 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 190 ms |
| Oct 3, 2026 | 192 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 195 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
1.4 s
2.8 s
4.2 s
5.6 s
7.0 s
8.4 s
9.8 s
11.2 s
Speed
Reduce unused JavaScript
11.1 s · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.1 s faster on a phone.
Use efficient cache lifetimes
8.4 s · 3.3 MB270 files are served with short cache lifetimes, so returning visitors download them again (3.3 MB).
Improve image delivery
2.4 s · 2.5 MB84 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
2.8 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Reduce unused CSS
1.6 s · 282 KiBAbout 282 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
YouTube adds 1.1 s
1.1 sYouTube costs a phone 1.1 s of main-thread work and 2.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.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 45). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.1 s
A phone's processor spends 8.1 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,928 HTML elements
The page has 3,928 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 3.7 MB and 1.9 s of main-thread time.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Google Tag Manager adds 302 ms
302 msGoogle Tag Manager costs a phone 302 ms of main-thread work and 371 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Facebook adds 235 ms
235 msFacebook costs a phone 235 ms of main-thread work and 318 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 23 KiB23 KiB could be saved by minifying JavaScript.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 210 ms
210 msYour server sent the HTML in 210 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 37.7 s
37.7 sYour largest element takes 37.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “We help you to find the best caterer. FoodLine - Singapore'…”.
Time to Interactive: 58.8 s
58.8 sThe page becomes fully interactive after 58.8 s. Good is under 3.8 s.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 478 ms
478 msScripts block taps and scrolling for 478 ms in total while the page loads. Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 188 ms to 195 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-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 682 ms
682 msReal visitors wait 682 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.066
0.066The layout barely moves while loading (CLS 0.066, good is under 0.1).
Images and page weight
Page weight: 15.3 MB in 458 requests
15.3 MBYour homepage downloads 15.3 MB in 458 requests on a phone: images 6.0 MB (289), scripts 4.9 MB (74) and other files 2.3 MB (54). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
838 KiB6 images are downloaded at several times the size a phone draws them, for example FLxQuickBuySGOV - Mobile Banner_743_.webp at 2,580 px wide, shown at 390 px. Resized copies would save about 838 KiB.
25 images below the first screen load straight away
25 images further down the page (822 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (30 KiB) is 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.
About 4.3 g of CO₂ per visit
4.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.34 g of CO₂e: 521.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
10 elements use ARIA attributes their role does not allow, which confuses screen readers.
60 text elements with low contrast
60 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
49 images without alt text
49 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (88 elements)
All page content should be contained by landmarks: 88 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
15 form fields without a label
15 form fields have no label, so screen readers announce an empty box and autofill guesses.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (19 elements)
Alternative text of images should not be repeated as text: 19 elements on the page fail this check, rated minor by axe-core.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 12 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Top 50 Catering | Find the Best Caterers in Singapore - FoodLine.sg | Official Site”.
22 links crawlers can't follow
22 links have no real href, so search engines can't follow them.
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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
508 internal links, 26 external
The homepage links to 508 pages on foodline.sg and 26 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Biggest Catering Platform in Singapore”.
Canonical URL set
The canonical URL is https://www.foodline.sg/.
Structured data in place
Structured data found: Organization and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.foodline.sg/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.foodline.sg/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (2,785 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.foodline.sg/tingkat/promotions is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://www.foodline.sg/dailyCoins and https://www.foodline.sg/best-catering/131-Best-Catering-for-October-2026 have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.foodline.sg/collect-promo-codes has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.foodline.sg/tingkat/promotions took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 163 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5219019&Ver=2&mid=0af1d5e7-a070-4499-a484-a8ec339d1a55&bo=1&sid=ef29cba0cee211f187aba74113d7d32d&vid=ef29f770cee211f1af0b650477fa9afa&vids=1&msclkid=N&pi=918639831&lg=.
39 small tap targets
39 of 134 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'controller')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 13-field form
Your longest form asks for 13 fields (0 required). Every extra field lowers completion.
About 1,554 words of copy
The homepage carries about 1,554 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Sign up now” and “Chat / Call”.
19 calls to action
The homepage has 19 calls to action, for example “Sign up now”, “Must Try” and “Request Quotations”.
Social proof on the page
Social proof on the homepage: 136 testimonial or review blocks, 37 customer or partner logos, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 8 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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, 1 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.
26 other companies contacted
Loading the homepage contacts 26 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 foodline.sg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on foodline.sg, including 19 speed issues, 4 SEO issues and 1 conversion gap. 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.