mytwobrows.com website review

The page goes through 2 redirects before it starts loading, costing about 4.7 s. Link and advertise the final URL directly.

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and rebuyengine.com and others), adding 3.3 MB and 1.8 s of main-thread time.

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

Shopify costs a phone 573 ms of main-thread work and 557 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

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

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

rebuyengine.com costs a phone 231 ms of main-thread work and 794 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.

mediadelivery.net costs a phone 145 ms of main-thread work and 638 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.

Klaviyo costs a phone 154 ms of main-thread work and 379 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 222 ms. During a long task the page ignores taps.

The HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.

119 KiB could be saved by minifying JavaScript.

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

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

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

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

3 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 117 ms to 135 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.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.9 MB in 699 requests on a phone: other files 7.7 MB (329), scripts 3.6 MB (214) and images 1.6 MB (45). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

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

Your <h1> is empty.

The homepage links to 92 pages on mytwobrows.com and 40 external pages.

https://mytwobrows.com/products/temporary-eyebrow-tattoos2 and https://mytwobrows.com/products/temporary-eyebrow-tattoos all use the title “Temporary Realistic Eyebrow Tattoos | My Two Brows”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://mytwobrows.com/policies/shipping-policy and https://mytwobrows.com/collections/all-products have no meta description, so Google writes the search snippet from whatever text it finds.

https://mytwobrows.com/products/temporary-eyebrow-tattoos2 and https://mytwobrows.com/products/temporary-eyebrow-tattoos use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://mytwobrows.com/products/temporary-eyebrow-tattoos2, whose canonical is https://mytwobrows.com/products/temporary-eyebrow-tattoos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mytwobrows.com/collections/all, https://mytwobrows.com/products/temporary-eyebrow-tattoos2, https://mytwobrows.com/collections/all-products and https://mytwobrows.com/products/temporary-eyebrow-tattoos have no <h1> headline, so visitors and search engines get no clear main topic.

https://mytwobrows.com/products/eyebrow-stamp-kit-presale took over 3 s to send its HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Access to resource at 'https://app.abconvert.io/api/analytics/theme/originalview' from origin 'https://mytwobrows.com' …”.

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

The homepage carries about 3,417 words of visible text.

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