vsadesigns.com website review

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

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 570 ms faster on a phone.

8 third-party services load with your homepage (Klaviyo, Yotpo and rebuyengine.com and others), adding 2.7 MB and 934 ms of main-thread time.

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

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

5 images could be 138 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

Yotpo costs a phone 189 ms of main-thread work and 501 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 2,338 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

rebuyengine.com costs a phone 157 ms of main-thread work and 746 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.

Azure Web Services costs a phone 103 ms of main-thread work and 352 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 141 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

28 KiB JavaScript is shipped twice across bundles.

10 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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.

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

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

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

Your homepage downloads 13.3 MB in 349 requests on a phone: media 8.2 MB (2), scripts 2.7 MB (139) and other files 1.1 MB (125). Under 2 MB keeps phones on slow connections fast.

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

2 tap targets are too small or too close together to hit reliably with a finger.

ARIA tooltip nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

There are 3 <h1> headlines (“Virgins Saints & Angels”, “Virgins Saints & Angels” and “Virgins Saints & Angels”). One clear main headline is easier for people and search engines.

Your meta description is 288 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at vsadesigns.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 145 pages on vsadesigns.com and 10 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://vsadesigns.com/collections/maddie, https://vsadesigns.com/collections/all-products, https://vsadesigns.com/collections/collections, https://vsadesigns.com/collections/all-necklaces, https://vsadesigns.com/collections/beaded-necklaces and https://vsadesigns.com/collections/medallions and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://vsadesigns.com/collections/maddie, https://vsadesigns.com/collections/all-products, https://vsadesigns.com/collections/collections, https://vsadesigns.com/collections/all-necklaces, https://vsadesigns.com/collections/beaded-necklaces and https://vsadesigns.com/collections/medallions and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 1 testimonial or review block. 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 778 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 33 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.