Website review, no card needed

ettika.com logo

ettika.com website review

Visit site (opens in a new tab)Reviewed 7 November 202643 issues · 90 checks

This review found 43 issues worth fixing on ettika.com, 18 of them high impact, across 90 checks. The most urgent: page weight: 11.8 MB in 549 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.5 s1.7 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.7 s
Jun 27, 20262.9 s
Jul 4, 20263.0 s
Jul 11, 20263.1 s
Jul 18, 20263.2 s
Jul 25, 20263.3 s
Aug 1, 20263.2 s
Aug 8, 20263.3 s
Aug 15, 20263.2 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
177 ms135 msMay 16Oct 31153 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026146 ms
May 23, 2026146 ms
May 30, 2026146 ms
Jun 6, 2026153 ms
Jun 13, 2026155 ms
Jun 20, 2026159 ms
Jun 27, 2026163 ms
Jul 4, 2026163 ms
Jul 11, 2026167 ms
Jul 18, 2026169 ms
Jul 25, 2026167 ms
Aug 1, 2026169 ms
Aug 8, 2026172 ms
Aug 15, 2026171 ms
Aug 22, 2026171 ms
Aug 29, 2026169 ms
Sep 5, 2026154 ms
Sep 12, 2026148 ms
Sep 19, 2026145 ms
Sep 26, 2026140 ms
Oct 3, 2026145 ms
Oct 10, 2026146 ms
Oct 17, 2026150 ms
Oct 24, 2026153 ms
Oct 31, 2026153 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of ettika.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ettika.com at 0.8 s0.8 s
  2. ettika.com at 1.5 s1.5 s
  3. ettika.com at 2.3 s2.3 s
  4. ettika.com at 3.0 s3.0 s
  5. ettika.com at 3.8 s3.8 s
  6. ettika.com at 4.6 s4.6 s
  7. ettika.com at 5.3 s5.3 s
  8. ettika.com at 6.1 s6.1 s

Speed

11 to fix17
  • 11,343 HTML elements

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

  • Mobile performance score: 17

    17/100

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

  • Main-thread work: 9.0 s

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

  • Improve image delivery

    1.8 MB

    40 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, rebuyengine.com and iovation and others), adding 2.9 MB and 1.0 s of main-thread time.

  • Reduce unused JavaScript

    816 KiB

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

  • Render-blocking requests

    500 ms

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

  • Google Tag Manager adds 270 ms

    270 ms

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

  • 20 long tasks on the main thread

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

  • Shopify adds 112 ms

    112 ms

    Shopify costs a phone 112 ms of main-thread work and 1.2 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.

  • rebuyengine.com adds 163 ms

    163 ms

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

  • Reduce unused CSS

    150 ms · 114 KiB

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

  • Use efficient cache lifetimes

    101 KiB

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

  • Legacy JavaScript

    72 KiB

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

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 151 ms

    151 ms

    Your server sent the HTML in 151 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • Fails Core Web Vitals for real visitors

    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-user CLS: 0.80

    0.80

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

  • Largest Contentful Paint: 13.9 s

    13.9 s

    Your largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero Image”.

  • Speed Index: 16.0 s

    16.0 s

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

  • Time to Interactive: 31.4 s

    31.4 s

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

  • Cumulative Layout Shift: 0.813

    0.813

    The layout shifts by 0.813 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 784 ms

    784 ms

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

3 checks passed
  • Real-user INP: 187 ms

    187 ms

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

  • Real-user TTFB: 653 ms

    653 ms

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

  • Largest content (LCP) got 21% faster for real visitors

    -21%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

3 to fix53
  • Page weight: 11.8 MB in 549 requests

    11.8 MB

    Your homepage downloads 11.8 MB in 549 requests on a phone: images 6.0 MB (195), scripts 2.4 MB (140) and other files 2.0 MB (155). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    20_Off_Cash_Back_Banner_mobile.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images far larger than shown

    64 KiB

    3 images are downloaded at several times the size a phone draws them, for example N3247TEY_IMG_01_600x.jpg at 600 px wide, shown at 165 px. Resized copies would save about 64 KiB.

  • 1 image in older formats

    1 image (66 KiB) is 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.

  • About 3.3 g of CO₂ per visit

    3.34 g

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

Accessibility

10 to fixGoogle 8187
  • 2 buttons without a name

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

  • Hidden but focusable

    10 elements hidden from screen readers can still receive keyboard focus.

  • 4 text elements with low contrast

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 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)

    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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 401 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 9 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9283
  • No H1 headline

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

  • Meta description is long (194 characters)

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

  • 12 links crawlers can't follow

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

  • 595 internal links, 0 external

    The homepage links to 595 pages on ettika.com and 0 external pages.

6 checks passed
  • Title: 49 characters

    Your title is a healthy 49 characters: “Ettika | On Trend Jewelry & Accessories for Women”.

  • Canonical URL set

    The canonical URL is https://www.ettika.com/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.ettika.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,350 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.ettika.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 11 pages without a meta description

    https://www.ettika.com/collections/18k-gold-plated-chains, https://www.ettika.com/collections/back-necklaces, https://www.ettika.com/collections/beaded-necklaces, https://www.ettika.com/collections/black-jewelry, https://www.ettika.com/collections/bezel-crystal and https://www.ettika.com/collections/best-sellers and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 62 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.ettika.com/cdn/shop/t/350/assets/custom-defer.css?v=128570' because its MIME t…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

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

  • No risk reducer

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

  • About 790 words of copy

    The homepage carries about 790 words of visible text.

  • Urgency cues

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Open account Signin/Signup drawer” and “Join Now”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Shop All”, “Shop All Best Sellers” and “Shop All Necklaces”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity (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.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 4 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 57 other companies contacted

    Loading the homepage contacts 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ettika.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Intelligems A B Testing · Klaviyo Email Marketing Sms · Kx Ai Collections · Triplewhale · Kimonix · Frontend · Gdpr Backpack · Rebuy Personalization Engine · covet.pics · azureedge.net · shareasale.com · socialsnowball.io · Swym Wishlist Plus

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Los Angeles

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on ettika.com, including 21 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25