loveecru.com website review

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

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

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

8 third-party services load with your homepage (vitals.app, Facebook and Google CDN and others), adding 1.8 MB and 1.2 s of main-thread time.

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

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

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

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

vitals.app costs a phone 204 ms of main-thread work and 454 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.

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

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

Google CDN costs a phone 156 ms of main-thread work and 298 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 133 ms of main-thread work and 310 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 long tasks block the main thread while loading, the longest for 156 ms. During a long task the page ignores taps.

5 KiB could be saved by minifying JavaScript.

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.

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

2 KiB could be saved by minifying CSS.

Your largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BLACK FRIDAY Up to 50% off Until 7 December Shop the sale →”.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 154 ms to 181 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 341 requests on a phone: scripts 2.1 MB (112), other files 1.2 MB (189) and images 322 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is 73 characters, so Google will cut it off around 60: “Loveecru: Tableware, Porcelain, and Furniture for Modern Homes – LoveÉcru”.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

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

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

The homepage links to 137 pages on loveecru.com and 5 external pages.

Your Organization JSON-LD is missing name, url, logo, 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.

https://loveecru.com/collections/founders-picks has no meta description, so Google writes the search snippet from whatever text it finds.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 24 cookies, 2 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.