onevsalonpro.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Hotjar and Klaviyo and others), adding 2.0 MB and 1.9 s of main-thread time.

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

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

Shopify costs a phone 522 ms of main-thread work and 735 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.

Hotjar costs a phone 507 ms of main-thread work and 65 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 465 ms. During a long task the page ignores taps.

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

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

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

About 38 KiB of CSS is downloaded but never applied on this page.

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

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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 4.5 MB in 361 requests on a phone: scripts 2.1 MB (157), images 1.1 MB (27) and other files 1,020 KiB (140). Under 2 MB keeps phones on slow connections fast.

d1bcf23a-a7ad-43e7-8f71-c2960c420f3b.jpeg weighs 578 KiB. On a phone connection a single image that size takes seconds.

1 image (578 KiB) is 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.

1 image is downloaded at several times the size a phone draws it, for example d1bcf23a-a7ad-43e7-8f71-c2960c420f3b.jpeg at 500 px wide, shown at 100 px. Resized copies would save about 370 KiB.

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

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

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 15 characters: “ONE V SALON PRO”. Between 30 and 65 characters leaves room to say what you do and for whom.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 160 pages on onevsalonpro.com and 11 external pages.

Your homepage links to https://onevsalonpro.com/pages/rewards, which answers with an error. Visitors hit a dead end and search engines drop it.

https://onevsalonpro.com/pages/reviews is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://onevsalonpro.com/pages/lash-v-bulk-order-discounts, whose canonical is https://onevsalonpro.com/pages/wholesale-bulk-order-lash-brow-supplies-discounts. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'variants')”.

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 1,309 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 Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 mores (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 24 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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.