Website review, no card needed

hibid.com logo

hibid.com website review

Visit site (opens in a new tab)Reviewed 11 October 202641 issues · 88 checks

This review found 41 issues worth fixing on hibid.com, 15 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
2.1 s1.7 sApr 18Oct 31.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.8 s
Apr 25, 20261.8 s
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
192 ms147 msApr 18Oct 3187 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026155 ms
Apr 25, 2026154 ms
May 2, 2026154 ms
May 9, 2026152 ms
May 16, 2026152 ms
May 23, 2026152 ms
May 30, 2026153 ms
Jun 6, 2026154 ms
Jun 13, 2026154 ms
Jun 20, 2026154 ms
Jun 27, 2026154 ms
Jul 4, 2026154 ms
Jul 11, 2026154 ms
Jul 18, 2026158 ms
Jul 25, 2026162 ms
Aug 1, 2026168 ms
Aug 8, 2026173 ms
Aug 15, 2026179 ms
Aug 22, 2026181 ms
Aug 29, 2026184 ms
Sep 5, 2026186 ms
Sep 12, 2026187 ms
Sep 19, 2026187 ms
Sep 26, 2026187 ms
Oct 3, 2026187 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 hibid.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hibid.com at 0.9 s0.9 s
  2. hibid.com at 1.7 s1.7 s
  3. hibid.com at 2.6 s2.6 s
  4. hibid.com at 3.5 s3.5 s
  5. hibid.com at 4.3 s4.3 s
  6. hibid.com at 5.2 s5.2 s
  7. hibid.com at 6.1 s6.1 s
  8. hibid.com at 6.9 s6.9 s

Speed

11 to fix32
  • Render-blocking requests

    3.3 s

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

  • Reduce unused JavaScript

    1.4 s · 1.2 MB

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

  • Mobile performance score: 32

    32/100

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

  • Main-thread work: 4.8 s

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

  • 8 third-party services on the page

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

  • Improve image delivery

    150 ms · 293 KiB

    11 images could be 293 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.

  • Google Tag Manager adds 364 ms

    364 ms

    Google Tag Manager costs a phone 364 ms of main-thread work and 530 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 · 116 KiB

    About 116 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.

  • Use efficient cache lifetimes

    384 KiB

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

  • 16 long tasks on the main thread

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

  • Google/Doubleclick Ads adds 154 ms

    154 ms

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

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

    95 ms

    Your server sent the HTML in 95 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 CLS: 0.45

    0.45

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

  • First Contentful Paint: 8.2 s

    8.2 s

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

  • Time to Interactive: 26.5 s

    26.5 s

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

  • Largest Contentful Paint: 8.6 s

    8.6 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Real-user INP: 227 ms

    227 ms

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

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

    +21%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

3 checks passed
  • 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 FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

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

    3.8 MB

    Your homepage downloads 3.8 MB in 97 requests on a phone: scripts 2.6 MB (34), images 452 KiB (19) and fonts 428 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    img.axd 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).

  • About 1.1 g of CO₂ per visit

    1.07 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9795
  • 9 tap targets too small

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

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

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

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

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

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

SEO

4 to fixGoogle 9281
  • No H1 headline

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

  • No structured data

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

  • No social preview image

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

  • 16 links crawlers can't follow

    16 links have no real href, so search engines can't follow them.

  • 123 internal links, 13 external

    The homepage links to 123 pages on hibid.com and 13 external pages.

5 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “The leading online auction platform. Sell, search, bid, and win on Antiques, Collectibles, Coins, Estate & Personal Pro…”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Live and Online Auctions on HiBid.com”.

  • Canonical URL set

    The canonical URL is https://hibid.com/.

  • 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://cdn.hibid.com/cdn/sitemaps/sitemap.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://hibid.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 (492 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 3 pages share a title

    /, https://hibid.com/auctions and https://hibid.com/lots all use the title “Live and Online Auctions on HiBid.com”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://hibid.com/auctions, https://hibid.com/home/stateauctions, https://hibid.com/email/subscribe and https://hibid.com/notifications/manage 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 56 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.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=16003842&tm=gtm002&Ver=2&mid=096d3270-4ad2-4aba-a3ad-71477b2274cc&bo=1&sid=3f796a10c5c611f1ac29bdadb7323e06&vid=3f7963a0c5c611f1bfdfdffff7163128&vids=1&msclkid=N&pi=91.

  • 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 “ERROR Error: Uncaught (in promise): TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    110 of 137 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

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

    The homepage carries about 633 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Join Our Mailing List” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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

Privacy and tracking

  • 7 trackers load before any consent

    7

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

  • 15 cookies set on arrival

    15

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

  • 35 other companies contacted

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

1 checks passed
  • Consent tool: Didomi

    A consent management tool (Didomi) 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 hibid.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 41 issues on hibid.com, including 21 speed issues, 4 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