cutebuddi.com website review

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

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

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

About 206 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (Shopify, Google Tag Manager and cornercart.io and others), adding 1.1 MB and 384 ms of main-thread time.

Shopify costs a phone 215 ms of main-thread work and 838 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 1,696 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

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.

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

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

2 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 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.9 MB in 271 requests on a phone: images 1.1 MB (34), other files 885 KiB (143) and scripts 681 KiB (57). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example money-back.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 136 KiB.

1 image further down the page (216 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

Your <h1> is empty.

The homepage links to 57 pages on cutebuddi.com and 2 external pages.

https://cutebuddi.com/apps/17TRACK, https://cutebuddi.com/pages/our-story, https://cutebuddi.com/pages/contact, https://cutebuddi.com/collections/all and https://cutebuddi.com/pages/shipping have no meta description, so Google writes the search snippet from whatever text it finds.

https://cutebuddi.com/products/3d-print-custom-pet-figurines and https://cutebuddi.com/products/custom-sleeping-pet-figurines 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://cutebuddi.com/apps/17TRACK, whose canonical is https://cutebuddi.com/apps/17track. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://cutebuddi.com/collections/gifts-for-pet-lovers, https://cutebuddi.com/products/3d-print-custom-pet-figurines, https://cutebuddi.com/products/custom-3d-printed-pet-portraits-with-a-bow-tie, https://cutebuddi.com/products/custom-pet-mugs, https://cutebuddi.com/pages/our-story and https://cutebuddi.com/pages/contact and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://cutebuddi.com/collections/gifts-for-pet-lovers, https://cutebuddi.com/products/3d-print-custom-pet-figurines, https://cutebuddi.com/products/custom-3d-printed-pet-portraits-with-a-bow-tie, https://cutebuddi.com/products/custom-pet-mugs, https://cutebuddi.com/products/chibi-pet-figurine and https://cutebuddi.com/products/custom-sleeping-pet-figurines and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://cutebuddi.com/apps/17TRACK, https://cutebuddi.com/pages/our-story, https://cutebuddi.com/pages/contact, https://cutebuddi.com/collections/all, https://cutebuddi.com/products/chibi-pet-figurine and https://cutebuddi.com/products/custom-sleeping-pet-figurines took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://cutebuddi.com/.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage has only about 237 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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