Website review, no card needed

tokenjewelry.com logo

tokenjewelry.com website review

Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 85 checks

This review found 34 issues worth fixing on tokenjewelry.com, 14 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
1.5 s996 msMay 23Nov 71.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.4 s
Oct 24, 20261.3 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
125 ms73 msMay 23Nov 7112 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202685 ms
Jun 13, 202687 ms
Jun 20, 202695 ms
Jun 27, 2026103 ms
Jul 4, 202698 ms
Jul 11, 202697 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202697 ms
Aug 8, 202696 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026112 ms
Sep 5, 2026107 ms
Sep 12, 2026103 ms
Sep 19, 2026102 ms
Sep 26, 202697 ms
Oct 3, 2026104 ms
Oct 10, 2026105 ms
Oct 17, 2026114 ms
Oct 24, 2026119 ms
Oct 31, 2026117 ms
Nov 7, 2026112 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 tokenjewelry.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tokenjewelry.com at 1.3 s1.3 s
  2. tokenjewelry.com at 2.5 s2.5 s
  3. tokenjewelry.com at 3.8 s3.8 s
  4. tokenjewelry.com at 5.0 s5.0 s
  5. tokenjewelry.com at 6.3 s6.3 s
  6. tokenjewelry.com at 7.6 s7.6 s
  7. tokenjewelry.com at 8.8 s8.8 s
  8. tokenjewelry.com at 10.1 s10.1 s

Speed

11 to fix59
  • Reduce unused JavaScript

    3.5 s · 616 KiB

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

  • Improve image delivery

    2.0 s · 560 KiB

    18 images could be 560 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 6.7 s

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

  • 5,275 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and hikeorders.com and others), adding 2.4 MB and 866 ms of main-thread time.

  • Mobile performance score: 59

    59/100

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

  • Reduce unused CSS

    730 ms · 132 KiB

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

  • Shopify adds 570 ms

    570 ms

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

  • Legacy JavaScript

    300 ms · 25 KiB

    Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Klaviyo adds 195 ms

    195 ms

    Klaviyo costs a phone 195 ms of main-thread work and 617 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.

  • Use efficient cache lifetimes

    150 ms · 44 KiB

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

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    90 ms · 2 KiB

    2 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

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

1 checks passed
  • Server response: 32 ms

    32 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 26.6 s

    26.6 s

    Your largest element takes 26.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GET 15% OFF! Sign up for emails and texts to get first dibs…”.

  • Time to Interactive: 27.1 s

    27.1 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

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

    +45%

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

  • Total Blocking Time: 310 ms

    310 ms

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

7 checks passed
  • Real-user INP: 161 ms

    161 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 593 ms

    593 ms

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

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

    -14%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 6.1 MB in 541 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 541 requests on a phone: scripts 2.0 MB (240), images 2.0 MB (40) and other files 1.2 MB (219). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    WebReady-495.jpg 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).

  • About 1.7 g of CO₂ per visit

    1.72 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.72 g of CO₂e: 205.9 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

4 to fixGoogle 9595
  • 9 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 4 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 (200 characters)

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 310 internal links, 0 external

    The homepage links to 310 pages on tokenjewelry.com and 0 external pages.

6 checks passed
  • Title: 60 characters

    Your title is a healthy 60 characters: “Token Jewelry | Effortless Everyday Jewelry Handmade to Last”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

  • llms.txt published

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

Other pages

1 to fix95
  • 4 pages without an H1

    https://tokenjewelry.com/collections/rings, https://tokenjewelry.com/collections/necklaces, https://tokenjewelry.com/collections/earrings and https://tokenjewelry.com/collections/hoops have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://tokenjewelry.com/collections/earrings took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 87 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://tokenjewelry.com/.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'querySelector')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    82 of 91 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 678 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 ALCHEMY”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop All Jewelry”, “Book Private Event” and “Shop All Jewelry Expand menu”.

  • 1 short form

    A short form (1 field at most) is 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, Klaviyo and Meta Pixel 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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 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.

  • 36 other companies contacted

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

Apps your storefront loads

Instafeed · Inbox · Judge Me Reviews · Klaviyo Email Marketing Sms · Rivo Loyalty Rewards Referrals · Forms · Globo Product Options · hikeorders.com · cloudfront.net · 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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on tokenjewelry.com, including 18 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