enflair.us website review

8 third-party services load with your homepage (Google Tag Manager, Clarity and Shopify and others), adding 8.6 MB and 1.0 s of main-thread time.

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

Shopify costs a phone 139 ms of main-thread work and 7.3 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 672 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Google Tag Manager costs a phone 452 ms of main-thread work and 774 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 3.8 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google CDN costs a phone 121 ms of main-thread work and 296 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.

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

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

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

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 14.8 s. Good is under 3.8 s.

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

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Wave Oval 63 inch is Here!”. Most of its time is element render delay (2.5 s).

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

26 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 11.4 MB in 388 requests on a phone: media 6.9 MB (3), scripts 1.7 MB (121) and images 1.5 MB (47). Under 2 MB keeps phones on slow connections fast.

3 images (531 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.

7 images are downloaded at several times the size a phone draws them, for example SB144-R-1300MB-ByronRightCorner-MatteBlack-4_f41013bb-d084-4 at 650 px wide, shown at 147 px. Resized copies would save about 305 KiB.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 10 characters: “Enflair US”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 10 characters: “Enflair US”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“” and “Shop the Latest Deals on Freestanding Bathtubs”). One clear main headline is easier for people and search engines.

Structured data found (Corporation, Organization and WebSite) but with 2 problems, for example “Corporation: logo is not an absolute URL ("https:files/Enflair_Black_rgb.png")”.

The homepage links to 99 pages on enflair.us and 4 external pages.

Your homepage links to https://enflair.us/pages/favourites and https://enflair.us/collections/eofy-sale-bathroom-kitchen-deals, which answer with an error. Visitors hit a dead end and search engines drop them.

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

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

https://enflair.us/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://enflair.us/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://enflair.us/collections/freestanding-acrylic-bathtubs, https://enflair.us/customer_authentication/redirect, https://enflair.us/collections/wave-oval-acrylic-freestanding-wide-bathtubs and https://enflair.us/collections/agora-groove-fluted-freestanding-bathtubs took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134611458&Ver=2&mid=24bff9c5-fbfb-47b1-97d1-8f36ce59c3ef&bo=1&sid=5f5ba2e0dd7e11f1a856ddbc7f361416&vid=5f5bc2b0dd7e11f18f8d2f41cfa45ed5&vids=1&msclkid=N&pi=918639831&l.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 2 customer or partner logos. 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 374 words of visible text.

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