Website review, no card needed

leondiamond.com logo

leondiamond.com website review

Visit site (opens in a new tab)Reviewed 8 November 202642 issues · 86 checks

This review found 42 issues worth fixing on leondiamond.com, 14 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
4.9 s1.7 sMay 16Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.7 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.5 s
Aug 1, 20263.4 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20262.7 s
Aug 29, 20263.2 s
Sep 5, 20263.4 s
Sep 12, 20264.5 s
Sep 19, 20264.5 s
Sep 26, 20264.3 s
Oct 3, 20264.2 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Oct 24, 20263.4 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
456 ms171 msMay 16Oct 31359 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026212 ms
May 23, 2026236 ms
May 30, 2026220 ms
Jun 6, 2026220 ms
Jun 13, 2026217 ms
Jun 20, 2026204 ms
Jun 27, 2026217 ms
Jul 4, 2026219 ms
Jul 11, 2026230 ms
Jul 18, 2026212 ms
Jul 25, 2026246 ms
Aug 1, 2026250 ms
Aug 8, 2026245 ms
Aug 15, 2026244 ms
Aug 22, 2026213 ms
Aug 29, 2026279 ms
Sep 5, 2026272 ms
Sep 12, 2026420 ms
Sep 19, 2026423 ms
Sep 26, 2026386 ms
Oct 3, 2026420 ms
Oct 10, 2026371 ms
Oct 17, 2026395 ms
Oct 24, 2026415 ms
Oct 31, 2026359 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 leondiamond.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. leondiamond.com at 0.9 s0.9 s
  2. leondiamond.com at 1.7 s1.7 s
  3. leondiamond.com at 2.6 s2.6 s
  4. leondiamond.com at 3.4 s3.4 s
  5. leondiamond.com at 4.3 s4.3 s
  6. leondiamond.com at 5.1 s5.1 s
  7. leondiamond.com at 6.0 s6.0 s
  8. leondiamond.com at 6.9 s6.9 s

Speed

10 to fix63
  • Improve image delivery

    4.5 s · 804 KiB

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

  • Reduce unused JavaScript

    1.8 s · 458 KiB

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

  • 4,280 HTML elements

    The page has 4,280 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, Affirm and Accessibe Accessibility Overlay and others), adding 10.7 MB and 687 ms of main-thread time.

  • Shopify adds 189 ms

    189 ms

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

  • Mobile performance score: 63

    63/100

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

  • Render-blocking requests

    900 ms

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

  • Main-thread work: 3.9 s

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

  • Legacy JavaScript

    300 ms · 46 KiB

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

  • tidio.co adds 68 ms

    68 ms

    tidio.co costs a phone 68 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.

  • Use efficient cache lifetimes

    150 ms · 203 KiB

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

  • 6 long tasks on the main thread

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

  • 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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 25 ms

    25 ms

    Your server sent the HTML in 25 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 LCP: 4.1 s

    4.1 s

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

  • Largest Contentful Paint: 22.6 s

    22.6 s

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

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

    9.6 s

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

  • Real-user INP: 418 ms

    418 ms

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

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

    +73%

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

  • Largest content (LCP) got 38% slower for real visitors

    +38%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • 4 images without width and height

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

5 checks passed
  • Real-user CLS: 0.06

    0.06

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

  • Real-user TTFB: 745 ms

    745 ms

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

  • Total Blocking Time: 162 ms

    162 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.04

    0.04

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

Images and page weight

2 to fix60
  • Page weight: 12.2 MB in 299 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 299 requests on a phone: media 7.0 MB (3), images 2.2 MB (19) and scripts 1.7 MB (118). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    301 KiB

    6 images are downloaded at several times the size a phone draws them, for example gempages_520655973908481054-e5db77dc-fd64-4b1d-9da3-f94798b5 at 1,920 px wide, shown at 390 px. Resized copies would save about 301 KiB.

  • 2 images in older formats

    2 images (434 KiB) are 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.

  • 2 images below the first screen load straight away

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

  • About 3.5 g of CO₂ per visit

    3.46 g

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

Accessibility

7 to fixGoogle 8589
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

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

  • 3 images without alt text

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

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

    All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

  • 21 links without text

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

  • 11 form fields without a label

    11 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is short (12 characters)

    Your title is only 12 characters: “Leon Diamond”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “14K Two Tone Fancy Yellow & White Marquise Diamon…”). One clear main headline is easier for people and search engines.

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

  • 66 internal links, 6 external

    The homepage links to 66 pages on leondiamond.com and 6 external pages.

6 checks passed
  • Meta description: 92 characters

    Your meta description is 92 characters: “A family-owned luxury jewelry store, established in 1975, located in NYC's Diamond District.”.

  • Canonical URL set

    The canonical URL is https://leondiamond.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://leondiamond.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 (1,182 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://leondiamond.com/pages/ldbridal is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://leondiamond.com/collections/all, https://leondiamond.com/pages/contact, https://leondiamond.com/collections/new-arrivals-spring-selections-more, https://leondiamond.com/pages/ldbridal and https://leondiamond.com/pages/fancy-color-guide have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://leondiamond.com/pages/ldbridal and https://leondiamond.com/pages/fancy-color-guide have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://leondiamond.com/collections/cushion-cut took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 11 distorted images

    11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    34 of 35 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: “Trusted by 10K+ Clients”. 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • About 491 words of copy

    The homepage carries about 491 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Shop All Bridal” and “Shop Now”.

  • 6 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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
  • 5 trackers load before any consent

    5

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies, 3 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.

  • 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 leondiamond.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on leondiamond.com, including 20 speed issues, 3 SEO issues and 4 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