Website review, no card needed

argolehne.com logo

argolehne.com website review

Visit site (opens in a new tab)Reviewed 5 November 202648 issues · 96 checks

This review found 48 issues worth fixing on argolehne.com, 19 of them high impact, across 96 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
3.9 s2.5 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.1 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.3 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.5 s
Aug 29, 20263.8 s
Sep 5, 20263.5 s
Sep 12, 20263.4 s
Sep 19, 20263.2 s
Sep 26, 20262.6 s
Oct 3, 20262.8 s
Oct 10, 20262.9 s
Oct 17, 20262.7 s
Oct 24, 20262.8 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
117 ms73 msMay 16Oct 31110 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026104 ms
May 30, 2026102 ms
Jun 6, 202696 ms
Jun 13, 202691 ms
Jun 20, 202696 ms
Jun 27, 202697 ms
Jul 4, 2026100 ms
Jul 11, 202696 ms
Jul 18, 202694 ms
Jul 25, 202687 ms
Aug 1, 202678 ms
Aug 8, 202690 ms
Aug 15, 2026102 ms
Aug 22, 2026104 ms
Aug 29, 2026111 ms
Sep 5, 2026104 ms
Sep 12, 2026110 ms
Sep 19, 2026104 ms
Sep 26, 2026104 ms
Oct 3, 2026112 ms
Oct 10, 2026104 ms
Oct 17, 2026104 ms
Oct 24, 2026111 ms
Oct 31, 2026110 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 argolehne.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. argolehne.com at 0.5 s0.5 s
  2. argolehne.com at 0.9 s0.9 s
  3. argolehne.com at 1.4 s1.4 s
  4. argolehne.com at 1.9 s1.9 s
  5. argolehne.com at 2.4 s2.4 s
  6. argolehne.com at 2.8 s2.8 s
  7. argolehne.com at 3.3 s3.3 s
  8. argolehne.com at 3.8 s3.8 s

Speed

11 to fix47
  • Reduce unused JavaScript

    5.8 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 341 KiB

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

  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. 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 (YouTube, Google Tag Manager and Google Maps and others), adding 2.3 MB and 1.2 s of main-thread time.

  • YouTube adds 426 ms

    426 ms

    YouTube costs a phone 426 ms of main-thread work and 991 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

    300 ms · 187 KiB

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

  • Google Tag Manager adds 319 ms

    319 ms

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

  • Minify JavaScript

    300 ms · 63 KiB

    63 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.8 s

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

  • Google Maps adds 196 ms

    196 ms

    Google Maps costs a phone 196 ms of main-thread work and 468 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.

  • 12 long tasks on the main thread

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

  • Improve image delivery

    100 ms · 106 KiB

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

  • Minify CSS

    150 ms · 27 KiB

    27 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    50 ms · 35 KiB

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

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

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

11 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 TTFB: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 23.8 s

    23.8 s

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

  • First Contentful Paint: 7.0 s

    7.0 s

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

  • Time to Interactive: 23.9 s

    23.9 s

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

  • Speed Index: 11.7 s

    11.7 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user CLS: 0.20

    0.20

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Total Blocking Time: 382 ms

    382 ms

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

2 checks passed
  • Real-user INP: 107 ms

    107 ms

    Real visitors wait 107 ms for the page to respond to a tap (75th percentile). 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 fix60
  • Page weight: 4.1 MB in 167 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 167 requests on a phone: scripts 2.5 MB (68), images 704 KiB (31) and fonts 469 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    127 KiB

    2 images are downloaded at several times the size a phone draws them, for example ewelers-vigilance-committee.png at 3,547 px wide, shown at 208 px. Resized copies would save about 127 KiB.

  • 5 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.15 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

12 to fixGoogle 7484
  • 1 button without a name

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

  • 22 text elements with low contrast

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

  • Positive tabindex

    3 elements have a tabindex above 0, which scrambles the keyboard order.

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 9 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 8595
  • No social preview image

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

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

  • 127 internal links, 14 external

    The homepage links to 127 pages on argolehne.com and 14 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “We are your trusted local jewelry store in Columbus, OH. Shop our collection of jewelry, diamonds, bridal & wedding jew…”.

  • One H1 headline

    Your main headline reads: “Top Rated Jewelry Store In Columbus, OH”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Jewelry Store In Columbus, OH | Argo & Lehne Jewelers | Jewelry”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage 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://argolehne.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.argolehne.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://www.argolehne.com/were-hiring, https://www.argolehne.com/join-email-list and https://www.argolehne.com/custom-engagement-rings 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 84 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 14 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5469
  • 1 broken image

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

  • 5 third-party cookies

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

  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Unexpected token ','”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

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

    The homepage carries about 587 words of visible text.

7 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Pre-Order Ornaments”, “Contact” and “Shop Vintage”.

  • 3 short forms

    3 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

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

  • 29 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on argolehne.com, including 22 speed issues, 2 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