petcubes.my website review

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

YouTube costs a phone 5.3 s of main-thread work and 9.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 10.7 MB and 5.8 s of main-thread time.

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

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

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

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

Google Fonts costs a phone 0 ms of main-thread work and 346 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.

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

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

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.

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

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero Banner V2 Image 1”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 14.2 MB in 258 requests on a phone: scripts 9.3 MB (87), images 2.4 MB (64) and HTML 818 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

5 images (267 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 4.04 g of CO₂e: 484.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

10 frames have no title, so screen-reader users cannot tell what they contain.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“12% Off Each Order” and “Real Stories from Real Customers”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and VideoObject) but with 1 problem, for example “VideoObject: thumbnailUrl is not an absolute URL ("Liquid error (snippets/json-ld line 36): invalid…”.

7 links have no real href, so search engines can't follow them.

The homepage links to 211 pages on petcubes.my and 12 external pages.

https://petcubes.my/collections/all-cat-products, https://petcubes.my/collections/all-dog-products, https://petcubes.my/pages/contact, https://petcubes.my/products/petcubes-puppy-food-chicken, https://petcubes.my/products/petcubes-gently-cooked-dog-food-chicken and https://petcubes.my/collections/cat-food-gently-cooked and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://petcubes.my/collections/all-dog-products and https://petcubes.my/pages/contact took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 583 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, 1 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.