proof.com.sg website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and bc-solutions.net and others), adding 1.1 MB and 1.3 s of main-thread time.

Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

About 482 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.

Google Tag Manager costs a phone 539 ms of main-thread work and 520 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 images could be 234 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

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

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

41 KiB could be saved by minifying CSS.

12 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.

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

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 3.7 MB in 284 requests on a phone: scripts 1.6 MB (84), images 940 KiB (24) and other files 836 KiB (124). Under 2 MB keeps phones on slow connections fast.

01-blisscape-sofa.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).

1 image (107 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.05 g of CO₂e: 125.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 dropdowns have no label.

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

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

autocomplete attribute must be used correctly: 2 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 23 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: 2 elements on the page fail this check, rated moderate by axe-core.

31 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.

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

Your title is 95 characters, so Google will cut it off around 60: “Discover Exquisite Designer Furniture for Luxurious Home Decor | Proof – Proof Living Sin…”.

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

Your <h1> is empty.

The homepage links to 305 pages on proof.com.sg and 6 external pages.

https://proof.com.sg/pages/new-contact-us and https://proof.com.sg/pages/contact-us all use the title “Contact Us – Proof Living Singapore”. Search engines can't tell which page to show for a search, so each competes with the others.

https://proof.com.sg/pages/new-contact-us and https://proof.com.sg/pages/contact-us use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://proof.com.sg/pages/new-contact-us, whose canonical is https://proof.com.sg/pages/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://proof.com.sg/pages/new-contact-us, https://proof.com.sg/pages/contact-us, https://proof.com.sg/collections/clearance-sale, https://proof.com.sg/collections/in-stock, https://proof.com.sg/collections/bestsellers and https://proof.com.sg/collections/furniture and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

14 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://dvbv96fvxd6o6.cloudfront.net/assets/css/shopify.min.css' from origin 'https://proo…”.

1 image is served at too low a resolution for sharp phone screens.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 10 fields (5 required). Every extra field lowers completion.

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

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