misshaus.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Yotpo and posthog.com and others), adding 25.6 MB and 865 ms of main-thread time.

videowise.com costs a phone 112 ms of main-thread work and 23.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.

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

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

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

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

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

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

Yotpo costs a phone 209 ms of main-thread work and 411 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.

Attentive costs a phone 44 ms of main-thread work and 334 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.

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

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

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

25 KiB could be saved by minifying JavaScript.

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

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

For real visitors the layout shifts by 0.81 (75th percentile). Good is under 0.1.

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

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

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

The layout shifts by 0.564 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your homepage downloads 45.6 MB in 540 requests on a phone: media 38.4 MB (5), images 2.9 MB (101) and scripts 2.2 MB (202). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example MISSHA_BB_Cream_Earthy_Skincare_Still_Life.png at 1,254 px wide, shown at 280 px. Resized copies would save about 205 KiB.

1 image further down the page (56 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 12.94 g of CO₂e: 1552.3 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”.

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

7 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 66 characters, so Google will cut it off around 60: “MISSHA US Official- Innovative K-beauty | Korean skincare | makeup”.

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

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

The homepage links to 185 pages on misshaus.com and 6 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://misshaus.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://misshaus.com/collections/all-products and https://misshaus.com/collections/glow have no meta description, so Google writes the search snippet from whatever text it finds.

https://misshaus.com/collections/all-products, https://misshaus.com/products/retinol-eye-cream, https://misshaus.com/collections/pdrn-nad and https://misshaus.com/collections/glow have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

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 323 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 26 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.