wanderprints.com website review

24 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

About 249 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Klaviyo, freshworks.com and Shopify and others), adding 1.3 MB and 317 ms of main-thread time.

About 39 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.

Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

Klaviyo costs a phone 101 ms of main-thread work and 320 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.

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

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

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 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image”.

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

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

The first text or image appears after 3.4 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 202 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 838 ms for your server to start answering (75th percentile). Good is under 800 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 321 requests on a phone: images 2.7 MB (113), scripts 1,013 KiB (97) and other files 748 KiB (76). Under 2 MB keeps phones on slow connections fast.

15 images (1.8 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.

thanksgiving-gifts-decor-banner.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).

13 images are downloaded at several times the size a phone draws them, for example Snowman250YearsOfFreedomAmericaAnniversary-PersonalizedCusto at 408 px wide, shown at 132 px. Resized copies would save about 297 KiB.

3 images further down the page (219 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.47 g of CO₂e: 176.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 691 pages on wanderprints.com and 6 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.

There is no https://wanderprints.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://wanderprints.com/pages/personalized-christmas-gifts-decor has no meta description, so Google writes the search snippet from whatever text it finds.

https://wanderprints.com/pages/personalized-christmas-gifts-decor, https://wanderprints.com/collections/personalized-anniversary-gifts, https://wanderprints.com/collections/personalized-thanksgiving-gifts-decor, https://wanderprints.com/pages/tracking-order-page, https://wanderprints.com/pages/halloween-personalized-gifts and https://wanderprints.com/collections/fall-gifts and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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 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.

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.

The homepage carries about 1,315 words of visible text.

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