redone.com.sg website review

65 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).

18 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.9 s.

About 775 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.5 s faster on a phone.

About 851 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

The HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.

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

Reduce initial server response time. Google estimates savings of 992 ms on a phone.

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.4 MB and 747 ms of main-thread time.

Google Tag Manager costs a phone 327 ms of main-thread work and 691 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 costs a phone 199 ms of main-thread work and 308 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.

Your server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

1 image could be 4 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

2 KiB could be saved by minifying JavaScript.

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 see the first content after 3.8 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Please note that all redONE Mobile SG subscriber lines are …”. Most of its time is element render delay (7.0 s).

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

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

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

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

The layout shifts by 0.134 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your homepage downloads 3.8 MB in 99 requests on a phone: scripts 2.0 MB (40), stylesheets 781 KiB (19) and fonts 382 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image (254 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.

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is only 13 characters: “redONE Mobile”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 56 pages on redone.com.sg and 19 external pages.

There is no https://redonemobile.com.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.

Your homepage links to https://redonemobile.com.sg/join-us, which answers with an error. Visitors hit a dead end and search engines drop it.

https://redonemobile.com.sg/news has no meta description, so Google writes the search snippet from whatever text it finds.

https://redonemobile.com.sg/idd, https://redonemobile.com.sg/contact-us, https://redonemobile.com.sg/1app, https://redonemobile.com.sg/store-locator, https://redonemobile.com.sg/about-us and https://redonemobile.com.sg/careers and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://redonemobile.com.sg/idd, https://redonemobile.com.sg/contact-us, https://redonemobile.com.sg/1app, https://redonemobile.com.sg/faq, https://redonemobile.com.sg/store-locator and https://redonemobile.com.sg/about-us and 7 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “%c MoEngage %c %c error %c %c HTTPS-NotificationManager.constructor color: white; background: #41AE55; border-radius: 5…”.

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.

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

The homepage has only about 140 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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 10 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.