coreelle.com website review

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

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

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

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

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

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

1 long task block the main thread while loading, the longest for 156 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).

8 third-party services load with your homepage (jQuery CDN, Shopify and Google Fonts and others), adding 266 KiB and 17 ms of main-thread time.

About 22 KiB of JavaScript is downloaded but never used on this page.

20 KiB could be saved by minifying CSS.

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.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

Real visitors wait 921 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

18 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 163 ms to 191 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 220 requests on a phone: images 4.9 MB (170), scripts 633 KiB (33) and fonts 211 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

3 buttons have no accessible name, so screen readers announce just “button”.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

The homepage links to 690 pages on coreelle.com and 7 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.

/collections/all, /pages/brands, /collections/gift-card, /collections/the-petite-club, /collections/trending-now and /collections/only-at-coreelle-1 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /collections/k-pop%F0%9F%92%9B, whose canonical is /collections/k-pop%f0%9f%92%9b. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/brands, /collections/the-petite-club, /collections/innerbeauty and /collections/k-pop%F0%9F%92%9B have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

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

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.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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.

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.