lashclusters.com website review

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

moxielash.com costs a phone 2.9 s of main-thread work and 1.8 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.

About 910 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.

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

A phone's processor spends 9.3 s on main-thread work while loading, 5.7 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 3.2 MB and 4.8 s of main-thread time.

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

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

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

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

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

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

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

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

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

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

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.

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.

Your largest element takes 21.3 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!”.

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

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

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

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

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

Your homepage downloads 7.5 MB in 353 requests on a phone: images 3.5 MB (111), scripts 3.3 MB (162) and other files 393 KiB (56). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example sultry-discovery-cluster-dsc-sultry101214-6819301.png at 1,200 px wide, shown at 169 px. Resized copies would save about 67 KiB.

2 images (199 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 2.13 g of CO₂e: 256.1 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 lashclusters.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 lashclusters.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 /products/lashies-starter-bundle, which answers with an error. Visitors hit a dead end and search engines drop it.

/pages/moxie-education, /pages/rewards, /collections/lash-clusters, /collections/featured-nano, /collections/magnetic-lashes and /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.

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

/pages/moxie-education, /pages/rewards, /collections/lash-clusters, /collections/featured-nano, /collections/xtend-lash-brow-serum-mascara and /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.

3 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

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

5 links from your homepage to your own site are broken, for example https://lashclusters.com/products/lashies-starter-bundle (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

7 links go through two or more redirects, for example https://lashclusters.com/pages/try-perfx.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

lashclusters.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

lashclusters.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

The page uses urgency cues (a countdown or limited-time wording).

lashclusters.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

lashclusters.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

lashclusters.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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