Website review, no card needed

nationalrarities.com logo

nationalrarities.com website review

Visit site (opens in a new tab)Reviewed 25 October 202632 issues · 87 checks

This review found 32 issues worth fixing on nationalrarities.com, 11 of them high impact, across 87 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.9 s1.5 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
230 ms144 msMay 2Oct 17220 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026154 ms
May 9, 2026159 ms
May 16, 2026166 ms
May 23, 2026169 ms
May 30, 2026169 ms
Jun 6, 2026169 ms
Jun 13, 2026170 ms
Jun 20, 2026170 ms
Jun 27, 2026175 ms
Jul 4, 2026170 ms
Jul 11, 2026161 ms
Jul 18, 2026159 ms
Jul 25, 2026154 ms
Aug 1, 2026162 ms
Aug 8, 2026164 ms
Aug 15, 2026171 ms
Aug 22, 2026186 ms
Aug 29, 2026190 ms
Sep 5, 2026195 ms
Sep 12, 2026203 ms
Sep 19, 2026203 ms
Sep 26, 2026201 ms
Oct 3, 2026206 ms
Oct 10, 2026212 ms
Oct 17, 2026220 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 nationalrarities.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nationalrarities.com at 0.4 s0.4 s
  2. nationalrarities.com at 0.8 s0.8 s
  3. nationalrarities.com at 1.1 s1.1 s
  4. nationalrarities.com at 1.5 s1.5 s
  5. nationalrarities.com at 1.9 s1.9 s
  6. nationalrarities.com at 2.3 s2.3 s
  7. nationalrarities.com at 2.6 s2.6 s
  8. nationalrarities.com at 3.0 s3.0 s

Speed

10 to fix42
  • Reduce unused JavaScript

    3.9 s · 881 KiB

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

  • Use efficient cache lifetimes

    2.5 s · 535 KiB

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

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42 (desktop: 70). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 2.1 MB and 1.4 s of main-thread time.

  • Google Tag Manager adds 669 ms

    669 ms

    Google Tag Manager costs a phone 669 ms of main-thread work and 845 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.

  • Legacy JavaScript

    600 ms · 12 KiB

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

  • Render-blocking requests

    450 ms

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

  • Facebook adds 371 ms

    371 ms

    Facebook costs a phone 371 ms of main-thread work and 312 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: 3.1 s

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

  • quickchat.ai adds 20 ms

    20 ms

    quickchat.ai costs a phone 20 ms of main-thread work and 471 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

    270 ms · 31 KiB

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

  • Improve image delivery

    50 ms · 181 KiB

    6 images could be 181 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • 12 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 70 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 6 ms

    6 ms

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

Core Web Vitals

7 to fix100
  • First Contentful Paint: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 20.8 s

    20.8 s

    Your largest element takes 20.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Estate Jewelry Appraisal Expert Inspecting a Diamond Ring”.

  • Time to Interactive: 24.6 s

    24.6 s

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

  • Speed Index: 7.9 s

    7.9 s

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

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

    +38%

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

  • Total Blocking Time: 593 ms

    593 ms

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

7 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: 1.7 s

    1.7 s

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

  • Real-user INP: 183 ms

    183 ms

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

  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (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.

  • Real-user TTFB: 438 ms

    438 ms

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

  • Cumulative Layout Shift: 0.047

    0.047

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

Images and page weight

2 to fix81
  • Page weight: 3.8 MB in 270 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 270 requests on a phone: scripts 2.2 MB (80), other files 836 KiB (143) and images 497 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    newhome-hero-mobile_24fbfc92-bada-47ae-8345-218241ef247d_460 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).

  • 1 image in older formats

    1 image (47 KiB) is 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.

  • About 1.1 g of CO₂ per visit

    1.08 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9093
  • 8 text elements with low contrast

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

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

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 49 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: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 8598
  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 48 internal links, 30 external

    The homepage links to 48 pages on nationalrarities.com and 30 external pages.

8 checks passed
  • Meta description: 84 characters

    Your meta description is 84 characters: “National Rarities Is a Leading Buyer and Seller of Gold, Silver, and Diamond Jewelry”.

  • One H1 headline

    Your main headline reads: “NATION’S MOST TRUSTED ESTATE BUYERS”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “National Rarities: Trusted Estate Buyers”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, LocalBusiness, Organization and SpeakableSpecification.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.nationalrarities.com/collections/jeweler-portal has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.nationalrarities.com/pages/get-an-offer has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.nationalrarities.com/pages/find-an-event, https://www.nationalrarities.com/pages/get-an-offer and https://www.nationalrarities.com/collections/jeweler-portal 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 25 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

2 to fixGoogle 7391
  • 9 third-party cookies

    9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    11 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 334 words of visible text.

6 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Learn More”, “Shop” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 6 customer or partner logos, a star rating and “300,000+ Happy Customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, HubSpot and LinkedIn Insight.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies (measured from a US location before any click).

  • 48 other companies contacted

    Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 nationalrarities.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
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on nationalrarities.com, including 17 speed issues, 1 SEO issue 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