Website review, no card needed

omijewelry.com logo

omijewelry.com website review

Visit site (opens in a new tab)Reviewed 8 November 202619 issues · 53 checks

This review found 19 issues worth fixing on omijewelry.com, 2 of them high impact, across 53 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
441 ms153 msMay 16Oct 31371 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026195 ms
May 23, 2026187 ms
May 30, 2026186 ms
Jun 6, 2026196 ms
Jun 13, 2026229 ms
Jun 20, 2026272 ms
Jun 27, 2026347 ms
Jul 4, 2026378 ms
Jul 11, 2026399 ms
Jul 18, 2026402 ms
Jul 25, 2026408 ms
Aug 1, 2026407 ms
Aug 8, 2026395 ms
Aug 15, 2026381 ms
Aug 22, 2026353 ms
Aug 29, 2026354 ms
Sep 5, 2026360 ms
Sep 12, 2026369 ms
Sep 19, 2026372 ms
Sep 26, 2026370 ms
Oct 3, 2026362 ms
Oct 10, 2026347 ms
Oct 17, 2026345 ms
Oct 24, 2026355 ms
Oct 31, 2026371 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

3 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 378 ms

    378 ms

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

  • Tap response (INP) got 90% slower for real visitors

    +90%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 555 ms

    555 ms

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

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

    -17%

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

Images and page weight

2 to fix78
  • Page weight: 3.9 MB

    3.9 MB

    Your homepage downloads 3.9 MB on a phone, 2.0 MB of it images (50%). Under 2 MB keeps phones on slow connections fast.

  • 14 images below the first screen load straight away

    14 images further down the page (387 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.12 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fix98
  • 19 links without text

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

2 checks passed
  • Every image has alt text

    All 89 images in the HTML carry an alt attribute.

  • 18 automated accessibility rules passed

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

SEO

3 to fix87
  • 5 H1 headlines

    There are 5 <h1> headlines (“”, “shop by category” and “watches”). One clear main headline is easier for people and search engines.

  • Meta description is long (163 characters)

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

  • No social preview image

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

  • 99 internal links, 6 external

    The homepage links to 99 pages on omijewelry.com and 6 external pages.

5 checks passed
  • Title: 64 characters

    Your title is a healthy 64 characters: “Luxury Jewelry | Real Gold Chains | Luxury Watches | OMI Jewelry”.

  • Canonical URL set

    The canonical URL is https://omijewelry.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://omijewelry.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 (672 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix78
  • 2 pages share a title

    https://omijewelry.com/pages/watch-collections and https://omijewelry.com/pages/watch-collection all use the title “Watch Collections – OMI Jewelry”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://omijewelry.com/pages/watch-collections, https://omijewelry.com/pages/womens-jewelry, https://omijewelry.com/pages/mens-jewelry, https://omijewelry.com/pages/watch-collection and https://omijewelry.com/apps/ring-creator/rb-get-started have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://omijewelry.com/pages/womens-jewelry, whose canonical is https://omijewelry.com/pages/womens-jewelry-collections. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://omijewelry.com/pages/watch-collections, https://omijewelry.com/pages/womens-jewelry, https://omijewelry.com/pages/mens-jewelry, https://omijewelry.com/pages/chains, https://omijewelry.com/collections/rolex-collection and https://omijewelry.com/pages/watch-collection and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://omijewelry.com/collections/diamond-watch took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 fix87
  • 13 small tap targets

    13 of 46 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 “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • About 767 words of copy

    The homepage carries about 767 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE ROLEX COLLECTION” and “SHOP ALL WATCH COLLECTIONS”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Sign in/ Register”, “SHOP THE ROLEX COLLECTION” and “SHOP ALL WATCH COLLECTIONS”.

  • 9 short forms

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 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.

  • 39 other companies contacted

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

Apps your storefront loads

Black Crow Ai That Delivers · Avada Seo Suite · P4dl8b832 Opensend · Attentive · Zepto Product Personalizer · Power Tools Filter Menu · Klaviyo Email Marketing Sms · Gempages Builder · Tipo Related Products · Gempages Cro · Globo Also Bought Cross Sell · Avada Cookie Bar · Mega Menu Creator Pro · Announcement Bar With Slider · Page Speed Optimizer · getsitecontrol.com · zonos.com · loox.io · hukcommerce.com · attn.tv · kxcdn.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

Framework
Tailwind CSS
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 19 issues on omijewelry.com, including 3 speed issues, 3 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