pawandglory.com website review

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

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

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

8 third-party services load with your homepage (loox.io, Facebook and Shopify and others), adding 54.9 MB and 684 ms of main-thread time.

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

41 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

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

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

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

Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need.

18 KiB could be saved by minifying CSS.

11 KiB could be saved by minifying JavaScript.

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.

2 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NO.1 CUSTOM PET PORTRAITS ★★★★★ 2,200+ Verified Reviews You…”.

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

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

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

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

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

Your homepage downloads 60.3 MB in 545 requests on a phone: media 51.3 MB (8), images 5.5 MB (71) and scripts 1.8 MB (169). Under 2 MB keeps phones on slow connections fast.

3 images weigh 9.6 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example IMG_1525.webp at 2,200 px wide, shown at 98 px. Resized copies would save about 9.5 MB.

12 images (10.2 MB) 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 17.08 g of CO₂e: 2050.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 467 pages on pawandglory.com and 26 external pages.

https://www.pawandglory.com/en-us and / all use the title “Custom Pet Portraits & Dog Portraits | Paw & Glory”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 15 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.pawandglory.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.pawandglory.com/collections/pet-memorial-portraits took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17526898&tm=gtm002&Ver=2&mid=e534f50f-d101-4c25-ab4a-aae8f62b8fa9&bo=1&sid=8d9127a0dd6711f1958ac31b8bec41ec&vid=8d912450dd6711f1af6f0d186cf1d4ae&vids=1&msclkid=N&pi=91.

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

Large scripts ship without source maps.

The homepage carries about 914 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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 12 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.