magneticlashes.com website review

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

moxielash.com costs a phone 1.8 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (moxielash.com, Google Tag Manager and Facebook and others), adding 2.6 MB and 2.9 s of main-thread time.

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

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

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

Polyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

Facebook costs a phone 290 ms of main-thread work and 253 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.

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

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

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

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

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

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

Your largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Level UP your lash game with Moxie!”.

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

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

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

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

Your homepage downloads 4.4 MB in 322 requests on a phone: scripts 2.5 MB (159), images 1.2 MB (90) and other files 375 KiB (49). Under 2 MB keeps phones on slow connections fast.

2 images (123 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.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The robots meta tag says “noindex”: Google is told not to list this page at all.

Your canonical URL points to shop.moxielash.com, not magneticlashes.com, so Google may credit that host instead.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“WELCOME TO THE FUTURE OF LASHES” and “/'MÄKSE/”). One clear main headline is easier for people and search engines.

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

The homepage links to 89 pages on magneticlashes.com and 43 external pages.

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.

Your homepage links to https://magneticlashes.com/products/lashies-starter-bundle, which answers with an error. Visitors hit a dead end and search engines drop it.

https://magneticlashes.com/pages/moxie-education, https://magneticlashes.com/pages/rewards, https://magneticlashes.com/collections/lash-clusters, https://magneticlashes.com/collections/featured-nano, https://magneticlashes.com/collections/magnetic-lashes and https://magneticlashes.com/collections/xtend-lash-brow-serum-mascara and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://magneticlashes.com/pages/moxie-education, https://magneticlashes.com/pages/lash-quiz, https://magneticlashes.com/pages/contact-us-final and https://magneticlashes.com/pages/smartbox-membership have no meta description, so Google writes the search snippet from whatever text it finds.

https://magneticlashes.com/pages/moxie-education, https://magneticlashes.com/pages/rewards, https://magneticlashes.com/collections/lash-clusters, https://magneticlashes.com/collections/featured-nano, https://magneticlashes.com/collections/xtend-lash-brow-serum-mascara and https://magneticlashes.com/collections/make-up-removers and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

25 of 81 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage carries about 755 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, Klaviyo 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 25 cookies, 8 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.