Website review, no card needed

estatesales.org logo

estatesales.org website review

Visit site (opens in a new tab)Reviewed 11 October 202635 issues · 89 checks

This review found 35 issues worth fixing on estatesales.org, 11 of them high impact, across 89 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.0 s889 msApr 18Oct 3948 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026935 ms
Apr 25, 2026960 ms
May 2, 2026971 ms
May 9, 2026980 ms
May 16, 2026978 ms
May 23, 2026974 ms
May 30, 2026975 ms
Jun 6, 2026992 ms
Jun 13, 20261.0 s
Jun 20, 2026989 ms
Jun 27, 2026970 ms
Jul 4, 2026966 ms
Jul 11, 2026950 ms
Jul 18, 2026922 ms
Jul 25, 2026905 ms
Aug 1, 2026904 ms
Aug 8, 2026905 ms
Aug 15, 2026946 ms
Aug 22, 2026964 ms
Aug 29, 2026959 ms
Sep 5, 2026977 ms
Sep 12, 2026979 ms
Sep 19, 2026980 ms
Sep 26, 2026973 ms
Oct 3, 2026948 ms
Real-visitor tap response (INP)75th percentile, phones
71 ms63 msApr 18Oct 364 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202668 ms
Apr 25, 202667 ms
May 2, 202667 ms
May 9, 202665 ms
May 16, 202664 ms
May 23, 202664 ms
May 30, 202666 ms
Jun 6, 202669 ms
Jun 13, 202670 ms
Jun 20, 202669 ms
Jun 27, 202669 ms
Jul 4, 202669 ms
Jul 11, 202669 ms
Jul 18, 202666 ms
Jul 25, 202666 ms
Aug 1, 202666 ms
Aug 8, 202667 ms
Aug 15, 202669 ms
Aug 22, 202669 ms
Aug 29, 202668 ms
Sep 5, 202668 ms
Sep 12, 202667 ms
Sep 19, 202667 ms
Sep 26, 202666 ms
Oct 3, 202664 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 estatesales.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix44
  • Reduce unused JavaScript

    5.1 s · 901 KiB

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 5.0 s

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

  • 4,106 HTML elements

    The page has 4,106 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 (Google Tag Manager, Google CDN and confiant-integrations.net and others), adding 2.1 MB and 1.5 s of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 323 KiB

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

  • Reduce unused CSS

    430 ms · 68 KiB

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

  • Google Tag Manager adds 409 ms

    409 ms

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

  • Google CDN adds 368 ms

    368 ms

    Google CDN costs a phone 368 ms of main-thread work and 763 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.

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Google/Doubleclick Ads adds 136 ms

    136 ms

    Google/Doubleclick Ads costs a phone 136 ms of main-thread work and 319 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

    200 ms · 48 KiB

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

  • 19 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 19 KiB

    2 images could be 19 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.

  • Phones get a much slower page than desktops

    Desktop scores 70 but mobile only 44. 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: 134 ms

    134 ms

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

Core Web Vitals

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

  • First Contentful Paint: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 14.3 s

    14.3 s

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

  • Time to Interactive: 31.0 s

    31.0 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 472 ms

    472 ms

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 169 ms

    169 ms

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

    1.7 s

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

  • 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.3 MB in 372 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 372 requests on a phone: scripts 2.3 MB (36), other files 544 KiB (216) and HTML 131 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.94 g

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

4 to fixGoogle 9394
  • 64 text elements with low contrast

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

  • 6 tap targets too small

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

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

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

  • 3 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 91 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 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 9294
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 660 internal links, 12 external

    The homepage links to 660 pages on estatesales.org and 12 external pages.

7 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “The leading estate sale marketplace. Search for local estate sales, shop online and connect with local estate sale comp…”.

  • One H1 headline

    Your main headline reads: “Find local estate sales & estate sale companies”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “EstateSales.org: Find Estate Sales or Shop Online Auctions”.

  • 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://estatesales.org/sitemap-index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://estatesales.org/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.

3 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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 3 linked pages hidden from search

    https://estatesales.org/estate-sales/mo/imperial/63052/2-start-massive-sports-pokemon-2466241/gallery, https://estatesales.org/estate-sales/nh/londonderry/03053/turtle-treasure-auctions-ma-nh-2467623/gallery and https://estatesales.org/estate-sales/co/denver/80238/premium-collector-sale-4-godzilla-2467586/gallery are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 8 pages share a meta description

    https://estatesales.org/advertise and https://estatesales.org/estate-sales use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 196 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5483
  • 14 small tap targets

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

  • 7 third-party cookies

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

  • 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 “Failed to load resource: the server responded with a status of 403 ()”.

  • 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

3 to fix83
  • 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 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 3,034 words of copy

    The homepage carries about 3,034 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop” and “Shop Online Sales & Auctions”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Register”, “Shop Online Sales & Auctions” and “Buy now $400.00 $500.00 (20% off)”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 2 mores (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.

  • 56 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2009.

Stack

Framework
jQuery
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 35 issues on estatesales.org, including 18 speed issues, 2 SEO issues 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