refash.sg website review

113 images could be 17.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, elfsight.com and Privy and others), adding 3.4 MB and 1.0 s of main-thread time.

42 files are served with short cache lifetimes, so returning visitors download them again (1,001 KiB).

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

Shopify costs a phone 444 ms of main-thread work and 1.9 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.

elfsight.com costs a phone 288 ms of main-thread work and 411 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.

Privy costs a phone 117 ms of main-thread work and 408 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.

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

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

About 63 KiB of CSS is downloaded but never applied on this page.

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

19 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “mobile (15).gif__PID:f5c49850-0586-4388-bf3b-91fc392527cb”.

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

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

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

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

Real visitors wait 212 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your homepage downloads 21.4 MB in 386 requests on a phone: images 18.1 MB (124), scripts 2.1 MB (115) and other files 800 KiB (96). Under 2 MB keeps phones on slow connections fast.

36 images are downloaded at several times the size a phone draws them, for example IMG_0023_clipped_rev_1_f93d5772-d345-41b8-b874-d903e2b6ee23. at 2,123 px wide, shown at 129 px. Resized copies would save about 9.1 MB.

2 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

4 images (2.3 MB) 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.

mobile_2_2a408e73-8755-4f32-9a24-031be23bebae.gif 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 6.08 g of CO₂e: 729.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Scrollable region must have keyboard access: 93 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

3 elements have a tabindex above 0, which scrambles the keyboard order.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 18 pages on refash.sg and 5 external pages.

The HTML your server sends has 853 of the 2,128 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://refash.sg/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://refash.sg/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://refash.sg/collections/all and https://refash.sg/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://refash.sg/collections/dresses and https://refash.sg/collections/tops use the same meta description. A description written for each page earns more clicks.

https://refash.sg/collections/all, https://refash.sg/customer_authentication/redirect, https://refash.sg/collections/largest-online-thrift-store, https://refash.sg/collections/dresses, https://refash.sg/collections/tops and https://refash.sg/collections/designer and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://refash.sg/collections/largest-online-thrift-store and https://refash.sg/collections/dresses have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://refash.sg/customer_authentication/redirect took over 3 s to send its HTML from our server.

We fetched 7 pages linked from your homepage and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-gp01.grabpay.com/shopify/ui-js/v1/grab_widget.css' from origin 'https://refash…”.

Large scripts ship without source maps.

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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 2,128 words of visible text.

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