shopalvio.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Cloudflare CDN and others), adding 819 KiB and 1.1 s of main-thread time.

Shopify costs a phone 476 ms of main-thread work and 557 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 434 ms. During a long task the page ignores taps.

7 images could be 359 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Klaviyo costs a phone 310 ms of main-thread work and 76 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 243 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 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.

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

7 files are served with short cache lifetimes, so returning visitors download them again (14 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.

3 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 5.6 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 10.6 s. Good is under 3.8 s.

Visually, the page fills in at 4.9 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.

Your homepage downloads 2.4 MB in 169 requests on a phone: scripts 770 KiB (80), images 644 KiB (13) and other files 629 KiB (59). Under 2 MB keeps phones on slow connections fast.

Pastor_lp_5.png 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).

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

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

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

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

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

ARIA role should be appropriate for the element: 6 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).

Your <h1> is empty.

The homepage links to 32 pages on shopalvio.com and 0 external pages.

https://shopalvio.com/collections/default-collection, https://shopalvio.com/pages/contact, https://shopalvio.com/collections/all, https://shopalvio.com/products/alvio-s-little-jesus-figures, https://shopalvio.com/products/alvio-s-little-jesus-figures-copy and https://shopalvio.com/products/50x-jesus-loves-you-stickers and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://shopalvio.com/collections/default-collection, https://shopalvio.com/apps/tracking, https://shopalvio.com/pages/contact and https://shopalvio.com/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

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

Social proof on the homepage: 23 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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