etude.com website review

192 files are served with short cache lifetimes, so returning visitors download them again (7.7 MB).

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

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

About 526 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.

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

Reduce initial server response time. Google estimates savings of 1.5 s on a phone.

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

32 images could be 7.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and tiktokcdn-us.com and others), adding 4.4 MB and 555 ms of main-thread time.

tiktokcdn-us.com costs a phone 130 ms of main-thread work and 3.8 MB 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.

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

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

Google Tag Manager costs a phone 224 ms of main-thread work and 413 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,441 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Your server takes 1.6 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

42 KiB could be saved by minifying CSS.

18 KiB could be saved by minifying JavaScript.

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

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

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.

Real visitors wait 13.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 8.3 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 52.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dear Darling Marker Tint Looks like Marker, Works like Magic”.

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

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

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

Your homepage downloads 19.5 MB in 268 requests on a phone: images 12.6 MB (56), media 3.9 MB (6) and scripts 2.0 MB (88). Under 2 MB keeps phones on slow connections fast.

배너2_pc-1.jpg weighs 877 KiB. On a phone connection a single image that size takes seconds.

6 images (1.9 MB) 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 5.53 g of CO₂e: 663.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

9 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 358 pages on etude.com and 55 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.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/product/category/all, /product/category/eye/eye-all and /product/category/lip/lip-all all use the title “All – ETUDE GLOBAL OFFICIAL WEBSITE”. Search engines can't tell which page to show for a search, so each competes with the others.

/product/category/all, /product/category, /product/category/eye, /product/category/eye/eye-all, /product/category/eye/single-shadow and /product/category/eye/eye-palette and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/product/category/all, /product/category, /product/category/eye, /product/category/eye/eye-all, /product/category/eye/single-shadow and /product/category/eye/eye-palette and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/product/category, /product/category/eye, /product/category/eye/eye-all, /product/category/eye/single-shadow, /product/category/eye/eye-palette and /product/category/eye/eyeliner took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “selectShop is not defined”.

Chrome logged issues while loading the page (“Cookie”).

1 link to other sites is dead, for example http://www.amazon.com/stores/page/1C7D4DBC-FF51-4270-B7C7-8E32049EAC2A?ingress=2&visitId=14624c54-53bb-4512-a0a2-61d86846cc45&store_ref=bl_ast_dp_brandLogo_sto&ref_=ast_bln (503).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://etude.com goes through 2 redirects before the homepage loads.

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.

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

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

The homepage carries about 288 words of visible text.

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

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

etude.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 Analytics, Google Tag Manager and TikTok 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 5 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.