Website review, no card needed

dehartinc.com logo

dehartinc.com website review

Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 93 checks

This review found 34 issues worth fixing on dehartinc.com, 11 of them high impact, across 93 checks. The most urgent: audioeye.com adds 2.8 s. 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.2 s1.5 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.7 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
181 ms104 msMay 30Nov 14113 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026172 ms
Jun 6, 2026130 ms
Jun 13, 2026121 ms
Jun 20, 2026120 ms
Jun 27, 2026124 ms
Jul 4, 2026135 ms
Jul 11, 2026141 ms
Jul 18, 2026146 ms
Jul 25, 2026138 ms
Aug 1, 2026145 ms
Aug 8, 2026132 ms
Aug 15, 2026125 ms
Aug 22, 2026132 ms
Aug 29, 2026136 ms
Sep 5, 2026145 ms
Sep 12, 2026132 ms
Sep 19, 2026131 ms
Sep 26, 2026126 ms
Oct 3, 2026117 ms
Oct 10, 2026128 ms
Oct 17, 2026127 ms
Oct 24, 2026126 ms
Oct 31, 2026121 ms
Nov 7, 2026120 ms
Nov 14, 2026113 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 dehartinc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dehartinc.com at 0.8 s0.8 s
  2. dehartinc.com at 1.7 s1.7 s
  3. dehartinc.com at 2.5 s2.5 s
  4. dehartinc.com at 3.4 s3.4 s
  5. dehartinc.com at 4.2 s4.2 s
  6. dehartinc.com at 5.0 s5.0 s
  7. dehartinc.com at 5.9 s5.9 s
  8. dehartinc.com at 6.7 s6.7 s

Speed

14 to fix39
  • audioeye.com adds 2.8 s

    2.8 s

    audioeye.com costs a phone 2.8 s of main-thread work and 296 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 11.0 s

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

  • Mobile performance score: 39

    39/100

    Your mobile performance score is 39. 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 (audioeye.com, servicetitan.com and Wistia and others), adding 7.4 MB and 5.8 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 2.2 MB

    About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 2.2 MB

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

  • Wistia adds 849 ms

    849 ms

    Wistia costs a phone 849 ms of main-thread work and 3.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.

  • servicetitan.com adds 882 ms

    882 ms

    servicetitan.com costs a phone 882 ms of main-thread work and 2.9 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.

  • Improve image delivery

    600 ms · 180 KiB

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

  • Google Tag Manager adds 715 ms

    715 ms

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

    500 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    279 KiB

    About 279 KiB of CSS is downloaded but never applied on this page.

  • 2,307 HTML elements

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    28 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

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

    5 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 35.2 s

    35.2 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CALIFORNIA VIEW LOCATION”.

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • Speed Index: 10.3 s

    10.3 s

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • 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 INP: 118 ms

    118 ms

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

    1.6 s

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

  • Real-user TTFB: 733 ms

    733 ms

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

  • Tap response (INP) got 23% faster for real visitors

    -23%

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

  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix60
  • Page weight: 13.3 MB in 189 requests

    13.3 MB

    Your homepage downloads 13.3 MB in 189 requests on a phone: media 7.2 MB (1), scripts 4.4 MB (71) and images 1.2 MB (56). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    104 KiB

    1 image is downloaded at several times the size a phone draws it, for example best-in-modesto-2025.webp at 2,964 px wide, shown at 75 px. Resized copies would save about 104 KiB.

  • 4 images in older formats

    4 images (313 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image below the first screen load straight away

    1 image further down the page (49 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.8 g of CO₂ per visit

    3.78 g

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

Accessibility

2 to fixGoogle 9797
  • 4 text elements with low contrast

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

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

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

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “HVAC & Plumbing Contractor | DeHart Plumbing, Heating, and Air Inc.”.

  • Meta description is long (195 characters)

    Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:title and 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.

  • 76 internal links, 1 external

    The homepage links to 76 pages on dehartinc.com and 1 external page.

5 checks passed
  • One H1 headline

    Your main headline reads: “An HVAC & Plumbing Contractor Serving The Central Valley, Modesto, CA, and Reno, NV”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • 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://www.dehartinc.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.dehartinc.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.

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

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

  • Text is in the HTML

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

Other pages

3 to fix81
  • 1 page points its canonical at the homepage

    https://www.dehartinc.com/index declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.dehartinc.com/index all use the title “HVAC & Plumbing Contractor | DeHart Plumbing, Heating, and Air Inc.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://www.dehartinc.com/shop, https://www.dehartinc.com/index and https://www.dehartinc.com/service-areas 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 25 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

4 to fixGoogle 6974
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=26267110&Ver=2&mid=e4038a26-29e1-4156-9623-d8c8b1b9f785&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=HVAC%20%26%20Plumbing%20Contractor%20%7C%20DeHart%20Plu.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    49 of 57 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • A 10-field form

    Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

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

  • About 577 words of copy

    The homepage carries about 577 words of visible text.

  • Urgency cues

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CALL 877-320-0826” and “BOOK”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Let's Get Started”, “Instant HVAC Quote” and “Water Heater Quote”.

  • Social proof on the page

    Social proof on the homepage: 53 testimonial or review blocks, 1 customer or partner logo and 8 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 of them by other companies (measured from a US location before any click).

  • 38 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 dehartinc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Rackspace

Hiring

Hiring
7 open roles
Job board
careers page

Company

Headquarters
Modesto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on dehartinc.com, including 18 speed issues, 3 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