Website review, no card needed

eachjewels.com logo

eachjewels.com website review

Visit site (opens in a new tab)Reviewed 6 November 202639 issues · 77 checks

This review found 39 issues worth fixing on eachjewels.com, 8 of them high impact, across 77 checks. The most urgent: render-blocking 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

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

How it loaded on a phone

  1. eachjewels.com at 0.6 s0.6 s
  2. eachjewels.com at 1.2 s1.2 s
  3. eachjewels.com at 1.8 s1.8 s
  4. eachjewels.com at 2.4 s2.4 s
  5. eachjewels.com at 2.9 s2.9 s
  6. eachjewels.com at 3.5 s3.5 s
  7. eachjewels.com at 4.1 s4.1 s
  8. eachjewels.com at 4.7 s4.7 s

Speed

10 to fix69
  • Render-blocking requests

    1.4 s

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

  • Improve image delivery

    350 ms · 3.4 MB

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

  • Use efficient cache lifetimes

    400 ms · 943 KiB

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

  • Mobile performance score: 69

    69/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (route.com, tidio.co and loox.io and others), adding 1.4 MB and 597 ms of main-thread time.

  • Reduce unused JavaScript

    614 KiB

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

  • 2 long tasks on the main thread

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

  • route.com adds 287 ms

    287 ms

    route.com costs a phone 287 ms of main-thread work and 542 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.

  • Main-thread work: 2.0 s

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

  • tidio.co adds 81 ms

    81 ms

    tidio.co costs a phone 81 ms of main-thread work and 515 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

    55 KiB

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

  • Legacy JavaScript

    16 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix65
  • Largest Contentful Paint: 8.9 s

    8.9 s

    Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 21.0 s

    21.0 s

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

  • 49 images without width and height

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Total Blocking Time: 147 ms

    147 ms

    Scripts block the page for only 147 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 6.7 MB in 247 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 247 requests on a phone: images 4.1 MB (57), scripts 1.5 MB (58) and other files 801 KiB (113). Under 2 MB keeps phones on slow connections fast.

  • 25 images below the first screen load straight away

    25 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    60 KiB

    1 image is downloaded at several times the size a phone draws it, for example [email protected] at 1,060 px wide, shown at 250 px. Resized copies would save about 60 KiB.

  • About 1.9 g of CO₂ per visit

    1.91 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8591
  • Interactive controls must not be nested (11 elements)

    Interactive controls must not be nested: 11 elements on the page fail this check, rated serious by axe-core.

  • 11 tap targets too small

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

  • 31 images without alt text

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

  • All page content should be contained by landmarks (1 element)

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

  • 5 links without text

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

  • button, link, and menuitem elements do not have accessible names.

    button, link, and menuitem elements do not have accessible names. (4 elements).

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • No structured data

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

  • Meta description is long (208 characters)

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • One H1 headline

    Your <h1> is empty.

  • 87 internal links, 9 external

    The homepage links to 87 pages on eachjewels.com and 9 external pages.

5 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “Small Items Make A Big Impact – EACH Jewels”.

  • Canonical URL set

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

  • 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.eachjewels.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 13 pages without a meta description

    https://www.eachjewels.com/collections/barrettes, https://www.eachjewels.com/collections/pearl-barrette, https://www.eachjewels.com/collections/acrylic, https://www.eachjewels.com/collections/sets, https://www.eachjewels.com/collections/pony-cuffs and https://www.eachjewels.com/collections/headbands and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.eachjewels.com/collections/all-hair, https://www.eachjewels.com/collections/barrettes, https://www.eachjewels.com/collections/pearl-barrette, https://www.eachjewels.com/collections/acrylic, https://www.eachjewels.com/collections/sets and https://www.eachjewels.com/collections/pony-cuffs and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.eachjewels.com/collections/rings and https://www.eachjewels.com/collections/bracelets have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 9679
  • 23 small tap targets

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

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 analytics detected

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

  • 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 336 words of copy

    The homepage carries about 336 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “CONTACT”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “SHOP NOW” and “Contact”.

  • 3 short forms

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag 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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies (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.

  • 38 other companies contacted

    Loading the homepage contacts 38 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 eachjewels.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

powr.io · ns8.com · loox.io · chimpstatic.com · cloudfront.net · tidio.co · carti.io · route.com · nfcube.com

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
Hosting
Shopify

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on eachjewels.com, including 15 speed issues, 4 SEO issues and 3 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