netgearstore.sg website review

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

8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Facebook and others), adding 2.9 MB and 1.4 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 340 ms faster on a phone.

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

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

13 images could be 447 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

hsappstatic.net costs a phone 306 ms of main-thread work and 722 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.

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

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

azurefd.net costs a phone 45 ms of main-thread work and 331 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.

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

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

Polyfills for old browsers add 68 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 28.5 s. Good is under 3.8 s.

Your largest element takes 7.2 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 8.4 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

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

Your homepage downloads 5.8 MB in 377 requests on a phone: scripts 3.3 MB (197), other files 1.2 MB (126) and images 917 KiB (38). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

4 elements hidden from screen readers can still receive keyboard focus.

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “NETGEAR Store Singapore - Shop Mesh WiFi Systems, WiFi Routers, & more”.

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

Structured data found (Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.

The homepage links to 80 pages on netgearstore.sg and 5 external pages.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'marketingAllowed')”.

Chrome logged issues while loading the page (“Cookie”).

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: 123 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 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 28 cookies, 9 of them by other companies (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.