livewelles.com website review

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

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

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

8 third-party services load with your homepage (route.com, replocdn.com and Google Tag Manager and others), adding 3.3 MB and 1.4 s of main-thread time.

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

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

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

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

route.com costs a phone 298 ms of main-thread work and 542 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.

replocdn.com costs a phone 261 ms of main-thread work and 476 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 197 ms of main-thread work and 1.0 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.

Google Tag Manager costs a phone 214 ms of main-thread work and 445 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.

rebuyengine.com costs a phone 173 ms of main-thread work and 330 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 108 KiB of CSS is downloaded but never applied on this page.

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

18 KiB could be saved by minifying CSS.

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

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

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Person in blue scrubs sitting on a park bench with greenery…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.1 MB in 280 requests on a phone: scripts 2.9 MB (89), other files 983 KiB (145) and images 939 KiB (17). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (539 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images (362 KiB) 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 1.45 g of CO₂e: 174.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

2 dropdowns have no label.

ARIA commands must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

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

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

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

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

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.

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 75 pages on livewelles.com and 4 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://livewelles.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://livewelles.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://livewelles.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://livewelles.com/collections/womens-1, https://livewelles.com/collections/mens-1, https://livewelles.com/collections/bestsellers and https://livewelles.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://livewelles.com/collections/womens-1, https://livewelles.com/collections/mens-1, https://livewelles.com/collections/bestsellers and https://livewelles.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

3 errors were logged to the browser console while the page loaded, for example “Received "error" from https://livewelles.com/start _.<anonymous> (https://livewelles.com/web-pixels/strict/app/web-pixel-697204990@0fb8039459…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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