popular.com.sg website review

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

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

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

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

8 third-party services load with your homepage (pop-convert.com, gemcommerce.com and Shopify and others), adding 1.3 MB and 866 ms of main-thread time.

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

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

pop-convert.com costs a phone 365 ms of main-thread work and 162 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 258 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

54 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 22 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.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.0 MB in 312 requests on a phone: images 2.3 MB (59), other files 1.4 MB (168) and scripts 1,011 KiB (70). Under 2 MB keeps phones on slow connections fast.

3 images (231 KiB) 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.

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

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

Your title is 68 characters, so Google will cut it off around 60: “POPULAR Official Online Store: 10% Off for Popular Members and more!”.

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

Your <h1> is empty.

The homepage links to 215 pages on popular.com.sg and 0 external pages.

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

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://popular.com.sg/pages/stationery and https://popular.com.sg/collections/stationery all use the title “Stationery”. Search engines can't tell which page to show for a search, so each competes with the others.

https://popular.com.sg/pages/join-us, https://popular.com.sg/pages/promotions-of-the-month-tna, https://popular.com.sg/collections/preschool, https://popular.com.sg/collections/assessment-books-secondary, https://popular.com.sg/collections/o-levels and https://popular.com.sg/collections/igcse and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

22 of 49 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://cdn-bundler.nice-team.net/app/css/style.css?shop=popular-online-sg.myshopify.com&h…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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

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