fortunefood.sg website review

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

The page has 1,798 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

18 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

2 images could be 139 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

3 third-party services load with your homepage (smile.io, Shopify and shop.app), adding 228 KiB and 72 ms of main-thread time.

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

About 50 KiB of JavaScript is downloaded but never used on this page.

5 files are served with short cache lifetimes, so returning visitors download them again (12 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 817 ms for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Traditional popiah, made by hand the time-honoured way. Ord…”.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 97 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

fortune-food-popiah.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

3 elements hidden from screen readers can still receive keyboard focus.

2 links inside paragraphs rely on colour alone to stand out.

1 image has no alt text, which hurts accessibility and image search.

6 visible links have no text or label, so screen readers cannot say where they go.

Elements with visible text labels do not have matching accessible names. (24 elements).

The homepage links to 157 pages on fortunefood.sg and 10 external pages.

https://fortunefood.sg/pages/shop-all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://fortunefood.sg/pages/shop-all has no meta description, so Google writes the search snippet from whatever text it finds.

https://fortunefood.sg/collections/fortune-bundles and https://fortunefood.sg/collections/mini-buffet took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 59 found) and read each the way a search engine does.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,022 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.

Opening the homepage sets 12 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.