Website review, no card needed

harryritchies.com logo

harryritchies.com website review

Visit site (opens in a new tab)Reviewed 25 October 202635 issues · 83 checks

This review found 35 issues worth fixing on harryritchies.com, 15 of them high impact, across 83 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.2 s986 msMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.2 s
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.0 s
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
124 ms90 msMay 2Oct 1794 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026112 ms
May 9, 2026108 ms
May 16, 2026111 ms
May 23, 2026109 ms
May 30, 2026105 ms
Jun 6, 2026112 ms
Jun 13, 2026113 ms
Jun 20, 2026116 ms
Jun 27, 2026120 ms
Jul 4, 2026112 ms
Jul 11, 2026104 ms
Jul 18, 2026102 ms
Jul 25, 202697 ms
Aug 1, 2026101 ms
Aug 8, 2026103 ms
Aug 15, 2026100 ms
Aug 22, 202696 ms
Aug 29, 202695 ms
Sep 5, 202695 ms
Sep 12, 202695 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 202696 ms
Oct 10, 202695 ms
Oct 17, 202694 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 harryritchies.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. harryritchies.com at 0.6 s0.6 s
  2. harryritchies.com at 1.2 s1.2 s
  3. harryritchies.com at 1.8 s1.8 s
  4. harryritchies.com at 2.5 s2.5 s
  5. harryritchies.com at 3.1 s3.1 s
  6. harryritchies.com at 3.7 s3.7 s
  7. harryritchies.com at 4.3 s4.3 s
  8. harryritchies.com at 4.9 s4.9 s

Speed

9 to fix56
  • Reduce unused JavaScript

    3.3 s · 596 KiB

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

  • Improve image delivery

    2.0 s · 850 KiB

    17 images could be 850 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.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56 (desktop: 52). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

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

  • Use efficient cache lifetimes

    700 ms · 89 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, TikTok and avada.io and others), adding 3.4 MB and 323 ms of main-thread time.

  • Shopify adds 162 ms

    162 ms

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

  • 2,985 HTML elements

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

  • Main-thread work: 2.5 s

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

  • Legacy JavaScript

    100 ms · 16 KiB

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

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    21 KiB

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

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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 28.1 s

    28.1 s

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

  • Time to Interactive: 29.0 s

    29.0 s

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

  • First Contentful Paint: 7.1 s

    7.1 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 121 ms

    121 ms

    Real visitors wait 121 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.0 s

    1.0 s

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

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • Total Blocking Time: 65 ms

    65 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix55
  • Page weight: 18.0 MB in 264 requests

    18.0 MB

    Your homepage downloads 18.0 MB in 264 requests on a phone: media 11.6 MB (1), images 4.0 MB (42) and scripts 1.2 MB (68). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    H_Select_Proposal.jpg weighs 2.1 MB. On a phone connection a single image that size takes seconds.

  • About 5.1 g of CO₂ per visit

    5.09 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

9 to fixGoogle 8489
  • Hidden but focusable

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

  • 2 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

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

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

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

  • 23 links without text

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

  • 1 form field without a label

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

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

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

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 8 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 9274
  • No H1 headline

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

  • Title is short (22 characters)

    Your title is only 22 characters: “Harry Ritchies Jewelry”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (220 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//www.harryritchies.com/cdn/shop/files/HarryRitchies_Da…”.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 287 internal links, 12 external

    The homepage links to 287 pages on harryritchies.com and 12 external pages.

3 checks passed
  • Canonical URL set

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

  • 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.harryritchies.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.harryritchies.com/collections/all, https://www.harryritchies.com/collections/celebrate-our-70th-anniversary-with-up-to-70-off, https://www.harryritchies.com/collections/rings, https://www.harryritchies.com/collections/earrings, https://www.harryritchies.com/collections/necklaces and https://www.harryritchies.com/collections/bracelets and 9 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 123 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

3 to fixGoogle 9671
  • 7 broken images

    7 images failed to load on a phone, for example https://lh3.googleusercontent.com/grass-cs/ACvplmMqY8G_s88oysNxLrsRBzRQ3A_xckZ7-1Ap5krwwVeGi0dJqT6eYSMjz_3xYyJTFghlQK0eoPAPSls2OoPGZV3-dVJYgn7nGn6rJfT290_vUozYeVnGfc-eXbjXkVxCVJo9TxTv=k-no.

  • 15 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.harryritchies.com/cdn/shop/t/21/assets/vendor-flickity.css?v=9961' because its…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

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

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

    The homepage carries about 738 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 Now”.

  • 29 calls to action

    The homepage has 29 calls to action, for example “Shop All”, “Shop Without Credit” and “Contact”.

  • 26 short forms

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

  • Analytics in place

    Analytics detected: TikTok Pixel.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 7 cookies set on arrival

    7

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 harryritchies.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on harryritchies.com, including 13 speed issues, 4 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