Website review, no card needed

jeffmartinauctioneers.com logo

jeffmartinauctioneers.com website review

Visit site (opens in a new tab)Reviewed 21 October 202638 issues · 78 checks

This review found 38 issues worth fixing on jeffmartinauctioneers.com, 9 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
5.2 s3.5 sMay 2Oct 175.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.1 s
May 9, 20264.0 s
May 16, 20264.1 s
May 23, 20264.0 s
May 30, 20263.9 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.3 s
Jul 11, 20264.3 s
Jul 18, 20264.2 s
Jul 25, 20264.1 s
Aug 1, 20263.9 s
Aug 8, 20263.8 s
Aug 15, 20263.7 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.8 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20264.7 s
Oct 17, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
277 ms228 msMay 2Oct 17256 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026256 ms
May 9, 2026247 ms
May 16, 2026246 ms
May 23, 2026238 ms
May 30, 2026234 ms
Jun 6, 2026236 ms
Jun 13, 2026237 ms
Jun 20, 2026246 ms
Jun 27, 2026248 ms
Jul 4, 2026248 ms
Jul 11, 2026249 ms
Jul 18, 2026242 ms
Jul 25, 2026245 ms
Aug 1, 2026245 ms
Aug 8, 2026251 ms
Aug 15, 2026260 ms
Aug 22, 2026269 ms
Aug 29, 2026270 ms
Sep 5, 2026269 ms
Sep 12, 2026269 ms
Sep 19, 2026271 ms
Sep 26, 2026270 ms
Oct 3, 2026262 ms
Oct 10, 2026262 ms
Oct 17, 2026256 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 jeffmartinauctioneers.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix66
  • Use efficient cache lifetimes

    850 ms · 194 KiB

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

  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    170 ms · 726 KiB

    About 726 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 170 ms faster on a phone.

  • Render-blocking requests

    850 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (YouTube, tidio.co and Cloudflare CDN and others), adding 2.8 MB and 484 ms of main-thread time.

  • YouTube adds 349 ms

    349 ms

    YouTube costs a phone 349 ms of main-thread work and 973 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.

  • Amazon Web Services adds 23 ms

    23 ms

    Amazon Web Services costs a phone 23 ms of main-thread work and 1.3 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.

  • tidio.co adds 70 ms

    70 ms

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

  • Reduce unused CSS

    150 ms · 192 KiB

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

  • Improve image delivery

    150 ms · 13 KiB

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

  • 3 long tasks on the main thread

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

  • Document request latency

    100 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 564 ms of it running JavaScript. That is comfortably low.

  • Server response: 47 ms

    47 ms

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

    5.4 s

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Time to Interactive: 17.3 s

    17.3 s

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use necessary cookies and services to operate this websi…”.

  • Speed Index: 7.0 s

    7.0 s

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

  • Real-user INP: 228 ms

    228 ms

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

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

    +21%

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

3 checks passed
  • Real-user CLS: 0.09

    0.09

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

  • Total Blocking Time: 79 ms

    79 ms

    Scripts block the page for only 79 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

1 to fix85
  • Page weight: 3.0 MB in 171 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 171 requests on a phone: scripts 1.4 MB (111), images 1.1 MB (14) and HTML 222 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.86 g

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

5 to fixGoogle 8292
  • 31 tap targets too small

    31 tap targets are too small or too close together to hit reliably with a finger.

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (26 elements).

  • 13 text elements with low contrast

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

  • 5 form fields without a label

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Headings skip levels

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

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

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 25 automated accessibility rules passed

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

SEO

5 to fixGoogle 10065
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (23 characters)

    Your title is only 23 characters: “Jeff Martin Auctioneers”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No robots.txt

    There is no robots.txt at jeffmartinauctioneers.com/robots.txt, the first file search crawlers ask for.

  • Open Graph partly set

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 28 internal links, 18 external

    The homepage links to 28 pages on jeffmartinauctioneers.com and 18 external pages.

2 checks passed
  • Canonical URL set

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.jeffmartinauctioneers.com/sitemap.xml.

AI search readiness

1 to fix69
  • 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.jeffmartinauctioneers.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.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

2 to fixGoogle 7389
  • 5 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

  • 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

4 to fix69
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 37 words

    The homepage has only about 37 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Online Bidding Login/Register”, “Buy Now” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 1 cookie set on arrival

    1

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

  • 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 jeffmartinauctioneers.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 38 issues on jeffmartinauctioneers.com, including 19 speed issues, 5 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