robinsons.com.sg website review

Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 9.8 s on main-thread work while loading, 5.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Insider, Google Tag Manager and insightech.com and others), adding 6.4 MB and 2.0 s of main-thread time.

About 990 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

Insider costs a phone 818 ms of main-thread work and 857 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.

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

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

Shopify costs a phone 85 ms of main-thread work and 4.4 MB 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.

Google Tag Manager costs a phone 405 ms of main-thread work and 526 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.

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

20 long tasks block the main thread while loading, the longest for 286 ms. During a long task the page ignores taps.

insightech.com costs a phone 273 ms of main-thread work and 23 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.

Yotpo costs a phone 146 ms of main-thread work and 297 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

50 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 48 KiB JavaScript that modern phones do not need.

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.

For real visitors the layout shifts by 0.31 (75th percentile). Good is under 0.1.

Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 30.8 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 97.3 s. Good is under 3.8 s.

The first text or image appears after 4.6 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 23.9 MB in 537 requests on a phone: images 15.4 MB (158), other files 5.0 MB (226) and scripts 2.6 MB (110). Under 2 MB keeps phones on slow connections fast.

9 images weigh 7.1 MB together. On a phone connection a single image that size takes seconds.

13 images are downloaded at several times the size a phone draws them, for example 5_2c279c7c-5d0c-4856-8b15-084193d3485f_120x120_crop_center.s at 300 px wide, shown at 63 px. Resized copies would save about 5.0 MB.

1 image further down the page (41 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

7 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 14 elements on the page fail this check, rated minor by axe-core.

2 tap targets are too small or too close together to hit reliably with a finger.

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 frame has no title, so screen-reader users cannot tell what it contains.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 83 characters, so Google will cut it off around 60: “Online Shopping - The Leader Among Online Stores in Singapore – Robinsons Singapore”.

Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

17 links have no real href, so search engines can't follow them.

The homepage links to 715 pages on robinsons.com.sg and 2 external pages.

Your homepage links to https://www.robinsons.com.sg/pages/delivery-and-collection, https://www.robinsons.com.sg/pages/r-list-rewards, https://www.robinsons.com.sg/a/wishlist, https://www.robinsons.com.sg/collections/a-month-in-pink and https://www.robinsons.com.sg/pages/robinsons-brand-discovery-page, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.robinsons.com.sg/collections/sitewide-sale and https://www.robinsons.com.sg/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.robinsons.com.sg/pages/returns-and-exchanges, https://www.robinsons.com.sg/collections/sitewide-sale and https://www.robinsons.com.sg/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.robinsons.com.sg/pages/returns-and-exchanges, https://www.robinsons.com.sg/collections/sitewide-sale and https://www.robinsons.com.sg/pages/contact took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=137008214&tm=gtm002&Ver=2&mid=8a4e949d-35ba-434d-a798-0433188465c8&bo=1&sid=6e204ee0cc4311f19dad5d7f93c71f51&vid=6e2080c0cc4311f1bcc5271b385c94f9&vids=1&msclkid=N&pi=9.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

25 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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 20 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 56 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.