makeupbarhn.com website review

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

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

215 KiB could be saved by minifying JavaScript.

8 third-party services load with your homepage (Shopify, nfcube.com and Google CDN and others), adding 1.0 MB and 460 ms of main-thread time.

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

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

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

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

About 36 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

6 KiB JavaScript is shipped twice across bundles. 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 (20 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Real visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 2.8 MB in 383 requests on a phone: other files 1.2 MB (183), scripts 903 KiB (134) and images 385 KiB (25). Under 2 MB keeps phones on slow connections fast.

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

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

22 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: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 10 characters: “Makeup Bar”. 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.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

A phone browser shows 423 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

1 image failed to load on a phone, for example https://makeupbarhn.com/.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

Large scripts ship without source maps.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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