loveseen.com website review

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

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

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

8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Google Optimize and others), adding 954 KiB and 551 ms of main-thread time.

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

cloudfront.net costs a phone 224 ms of main-thread work and 497 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.

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

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

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

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

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

1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OH HI”. Most of its time is element render delay (2.5 s).

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.6 MB in 144 requests on a phone: scripts 1.3 MB (55), other files 634 KiB (73) and images 467 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

11 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 20 characters: “LoveSeen Fake Lashes”. 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.

Your meta description is only 56 characters: “Cruelty-free natural-looking fake lashes by Jenna Lyons.”. 70 to 160 characters is enough to sell the click.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 18 pages on loveseen.com and 13 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.

https://loveseen.com/collections/all, https://loveseen.com/collections/accessories, https://loveseen.com/collections/kits, https://loveseen.com/collections/new-drop-soon, https://loveseen.com/blogs/love-notes and https://loveseen.com/pages/about and 3 others use the same meta description. A description written for each page earns more clicks.

https://loveseen.com/collections/all, https://loveseen.com/collections/lashes, https://loveseen.com/collections/accessories, https://loveseen.com/collections/kits and https://loveseen.com/collections/new-drop-soon have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

10 images failed to load on a phone, for example https://loveseen.com/.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d3hw6dc1ow8pp2.cloudfront.net/styles/main.min.css' from origin 'https://loveseen.c…”.

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.

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 (5 required). Every extra field lowers completion.

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

The homepage has only about 33 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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