vitaboutique.com website review

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

5 third-party services load with your homepage (Bigcommerce, jQuery CDN and Yotpo and others), adding 6.9 MB and 374 ms of main-thread time.

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

Bigcommerce costs a phone 259 ms of main-thread work and 6.8 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.

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

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

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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

48 KiB JavaScript is shipped twice across bundles.

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 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Join us live on Facebook! Every Monday and Thursday at 7 pm…”.

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

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

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

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

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

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

Your homepage downloads 7.0 MB in 53 requests on a phone: images 6.4 MB (30), scripts 431 KiB (15) and stylesheets 62 KiB (3). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example FB_Live_Banner_2026.gif at 1,600 px wide, shown at 390 px. Resized copies would save about 2.0 MB.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Your title is only 13 characters: “Vita Boutique”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 7 <h1> headlines (“”, “SHOP THE LIVE” and “CATCH THE REPLAY”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://vitaboutique.com/sitemap.xml, so Google discovers your pages only by following links.

3 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 131 pages on vitaboutique.com and 3 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://vitaboutique.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://vitaboutique.com/shop-all/dresses and https://vitaboutique.com/clothing/dresses/casual-dresses use the same meta description. A description written for each page earns more clicks.

https://vitaboutique.com/new-2026-fall-collection, https://vitaboutique.com/shop-all, https://vitaboutique.com/shop-all/pants, https://vitaboutique.com/shop-all/pants/capris, https://vitaboutique.com/clothing/bottoms/shorts and https://vitaboutique.com/shop-all/jeans 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 61 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Error: <path> attribute d: Unexpected end of attribute. Expected number, "….907L9.5 0l2.792".”.

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.

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

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

Opening the homepage sets 10 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.