Website review, no card needed

habeggercorp.com logo

habeggercorp.com website review

Visit site (opens in a new tab)Reviewed 4 November 202647 issues · 88 checks

This review found 47 issues worth fixing on habeggercorp.com, 19 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
7.2 s4.7 sMay 16Oct 315.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.1 s
May 23, 20265.2 s
May 30, 20265.5 s
Jun 6, 20265.6 s
Jun 13, 20265.5 s
Jun 20, 20265.5 s
Jun 27, 20265.6 s
Jul 4, 20265.5 s
Jul 11, 20265.4 s
Jul 18, 20265.4 s
Jul 25, 20265.4 s
Aug 1, 20265.4 s
Aug 8, 20265.6 s
Aug 15, 20265.7 s
Aug 22, 20265.8 s
Aug 29, 20265.6 s
Sep 5, 20265.7 s
Sep 12, 20266.4 s
Sep 19, 20266.9 s
Sep 26, 20266.9 s
Oct 3, 20266.6 s
Oct 10, 20265.7 s
Oct 17, 20265.0 s
Oct 24, 20265.3 s
Oct 31, 20265.7 s
Real-visitor tap response (INP)75th percentile, phones
120 ms84 msMay 16Oct 31114 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202688 ms
May 23, 202691 ms
May 30, 202696 ms
Jun 6, 202695 ms
Jun 13, 202696 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202698 ms
Aug 1, 2026101 ms
Aug 8, 2026104 ms
Aug 15, 2026103 ms
Aug 22, 202699 ms
Aug 29, 202696 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202696 ms
Sep 26, 2026102 ms
Oct 3, 2026113 ms
Oct 10, 2026113 ms
Oct 17, 2026111 ms
Oct 24, 2026116 ms
Oct 31, 2026114 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 habeggercorp.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

14 to fix7
  • Use efficient cache lifetimes

    7.8 s · 1.8 MB

    84 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

  • Render-blocking requests

    8.9 s

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

  • Reduce unused JavaScript

    3.9 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 3.9 s faster on a phone.

  • Mobile performance score: 7

    7/100

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

  • Main-thread work: 6.6 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Hubspot, Google Tag Manager and Google Analytics and others), adding 814 KiB and 1.1 s of main-thread time.

  • Reduce unused CSS

    900 ms · 186 KiB

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

  • 17 long tasks on the main thread

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

  • Hubspot adds 795 ms

    795 ms

    Hubspot costs a phone 795 ms of main-thread work and 337 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.

  • Improve image delivery

    698 KiB

    33 images could be 698 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    400 ms

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

  • Google Tag Manager adds 314 ms

    314 ms

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

    300 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 300 ms faster on a phone.

  • 1,636 HTML elements

    The page has 1,636 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Minify JavaScript

    7 KiB

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

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

    12 ms

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

Core Web Vitals

13 to fix0
  • 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: 7.4 s

    7.4 s

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

  • Real-user INP: 937 ms

    937 ms

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

  • Real-user CLS: 0.37

    0.37

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

  • Real-user FCP: 7.0 s

    7.0 s

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

  • First Contentful Paint: 10.4 s

    10.4 s

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

  • Largest Contentful Paint: 12.7 s

    12.7 s

    Your largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BIG DISTRIBUTOR INVENTORY. SMALL DISTRIBUTOR FEEL.”.

  • Speed Index: 14.0 s

    14.0 s

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

  • Time to Interactive: 17.1 s

    17.1 s

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

  • Total Blocking Time: 2.4 s

    2.4 s

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

  • Cumulative Layout Shift: 0.422

    0.422

    The layout shifts by 0.422 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

    +28%

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

  • 5 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

1 checks passed
  • Real-user TTFB: 763 ms

    763 ms

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

Images and page weight

1 to fix67
  • Page weight: 3.7 MB in 141 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 141 requests on a phone: images 1.7 MB (101), scripts 1.5 MB (18) and fonts 229 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.05 g

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

Accessibility

8 to fixGoogle 6875
  • 1 button without a name

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • Hidden but focusable

    71 elements hidden from screen readers can still receive keyboard focus.

  • 15 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 10 automated accessibility rules passed

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

SEO

4 to fixGoogle 8585
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Big Distributor Inventory. Small Distributor Feel.” and “GOING ABOVE AND BEYOND FOR HVAC PROS IS WHAT WE DO”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://www.habeggercorp.com/sitemap.xml, so Google discovers your pages only by following links.

  • 12 links crawlers can't follow

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

  • 229 internal links, 11 external

    The homepage links to 229 pages on habeggercorp.com and 11 external pages.

5 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Delivering complete HVAC solutions since 1952. Explore our products, training, and contractor resources across all Habe…”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “The Habegger Corporation | Complete HVAC Solutions”.

  • Canonical URL set

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

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

AI search readiness

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

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

Other pages

1 to fix95
  • 13 links to non-canonical URLs

    Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://www.habeggercorp.com/residential, whose canonical is https://www.habeggercorp.com/residential?page=1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages slow to respond

    https://www.habeggercorp.com/hvac-categories, https://www.habeggercorp.com/residential, https://www.habeggercorp.com/residential/air-conditioners, https://www.habeggercorp.com/residential/heat-pumps, https://www.habeggercorp.com/residential/evaporator-coils and https://www.habeggercorp.com/residential/small-packaged-products and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 7793
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 746 words of visible text.

4 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “CONTACT”, “LOGIN - APPLY FOR AN ACCOUNT” and “LEARN MORE →”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: HubSpot.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 11 cookies set on arrival

    11

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

  • 11 other companies contacted

    Loading the homepage contacts 11 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 habeggercorp.com, 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 © 2025.

Stack

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on habeggercorp.com, including 27 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