elevationemobispa.com website review

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

24 images could be 1,017 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Google Tag Manager, loox.io and Klaviyo and others), adding 862 KiB and 642 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Rejuvenating skin care experience, just outside your door.”.

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

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

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

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.

4 images are downloaded at several times the size a phone draws them, for example Men_Kit_wBag_c1351b14-e584-489a-bf63-a57414ef8f73.png at 1,943 px wide, shown at 273 px. Resized copies would save about 720 KiB.

Your homepage downloads 3.8 MB in 253 requests on a phone: images 2.0 MB (91), scripts 830 KiB (59) and other files 683 KiB (84). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 7 characters: “mobispa”. 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 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 54 pages on elevationemobispa.com and 5 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.

https://elevationemobispa.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

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

https://elevationemobispa.com/pages/about, https://elevationemobispa.com/collections, https://elevationemobispa.com/pages/events, https://elevationemobispa.com/blogs/news, https://elevationemobispa.com/customer_authentication/redirect and https://elevationemobispa.com/collections/repair-your-youth and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://elevationemobispa.com/pages/about, https://elevationemobispa.com/collections, https://elevationemobispa.com/products/mobi-gift, https://elevationemobispa.com/pages/events, https://elevationemobispa.com/blogs/news and https://elevationemobispa.com/customer_authentication/redirect 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 18 found) and read each the way a search engine does.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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