pabloandco.net website review

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

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

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

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

8 third-party services load with your homepage (Hotjar, Yotpo and Klaviyo and others), adding 1.2 MB and 1.8 s of main-thread time.

Hotjar costs a phone 875 ms of main-thread work and 65 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.

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

Yotpo costs a phone 511 ms of main-thread work and 667 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.

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

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

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

Klaviyo costs a phone 266 ms of main-thread work and 311 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 66 KiB of CSS is downloaded but never applied on this page.

36 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 314 requests on a phone: images 1.3 MB (44), scripts 1.1 MB (95) and other files 769 KiB (118). Under 2 MB keeps phones on slow connections fast.

IMG_2379.jpg 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).

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 1 element on the page fails 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 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

Your <h1> is empty.

The homepage links to 196 pages on pabloandco.net and 10 external pages.

https://pabloandco.net/collections/christmas-accessories-copy, https://pabloandco.net/collections/christmas, https://pabloandco.net/collections/christmas-treats, https://pabloandco.net/collections/gifts-for-dog-people-copy and https://pabloandco.net/collections/collars have no meta description, so Google writes the search snippet from whatever text it finds.

https://pabloandco.net/products/shit-happens-doo-doo-holder, https://pabloandco.net/products/strawberry-doo-doo-holder, https://pabloandco.net/products/pink-bow-doo-doo-holder, https://pabloandco.net/products/sunflower-doo-doo-holder, https://pabloandco.net/products/howdy-doo-doo-holder and https://pabloandco.net/products/wiener-dog-doo-doo-holder and 1 other use the same meta description. A description written for each page earns more clicks.

https://pabloandco.net/products/shit-happens-doo-doo-holder, https://pabloandco.net/products/strawberry-doo-doo-holder, https://pabloandco.net/products/pink-bow-doo-doo-holder, https://pabloandco.net/products/sunflower-doo-doo-holder, https://pabloandco.net/products/howdy-doo-doo-holder and https://pabloandco.net/products/cowgirl-boot-doo-doo-holder and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

7 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/Product/917707487/807362142/square.jpg?1771199841.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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: a star rating. 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.

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 991 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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 25 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 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.