cocomo.sg website review

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

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

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

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

8 third-party services load with your homepage (Shopify, nice-team.net and Facebook and others), adding 3.7 MB and 760 ms of main-thread time.

About 155 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.

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

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

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

nice-team.net costs a phone 177 ms of main-thread work and 356 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.

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

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

9 KiB could be saved by minifying CSS.

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

38 KiB could be saved by minifying JavaScript.

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

Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CELDOT Diamond Micro Polish Enzyme Cleanser, Liquid Lift Mu…”. Most of its time is resource load delay (4.5 s).

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

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

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

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

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 5.8 MB in 233 requests on a phone: images 2.4 MB (52), scripts 1.9 MB (76) and other files 959 KiB (82). Under 2 MB keeps phones on slow connections fast.

cocomo-october-week3-banner-repairon-v1.webp 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).

19 images (811 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.

4 images further down the page (116 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (44 elements).

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

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

Your <h1> is empty.

The homepage links to 1,992 pages on cocomo.sg and 8 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.cocomo.sg/collections/october-2026-week-5-cocomo-weekly-spotlight, https://www.cocomo.sg/collections/newly-curated, https://www.cocomo.sg/collections/october-2026-k-beauty-sale, https://www.cocomo.sg/collections/october-2026-week-3-15-21-october, https://www.cocomo.sg/collections/october-2026-week-1-1-7-october and https://www.cocomo.sg/collections/september-2026-k-beauty-sale and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.cocomo.sg/collections/october-2026-k-beauty-sale took over 3 s to send its HTML from our server.

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

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=cocomo65.myshopify.com&has_volume…”.

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