Website review, no card needed

titus-hvac.com logo

titus-hvac.com website review

Visit site (opens in a new tab)Reviewed 24 October 202645 issues · 93 checks

This review found 45 issues worth fixing on titus-hvac.com, 17 of them high impact, across 93 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
1.8 s1.4 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.5 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
123 ms62 msMay 2Oct 1771 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202670 ms
May 9, 202670 ms
May 16, 202669 ms
May 23, 202670 ms
May 30, 202669 ms
Jun 6, 202671 ms
Jun 13, 202670 ms
Jun 20, 202669 ms
Jun 27, 202671 ms
Jul 4, 202671 ms
Jul 11, 202674 ms
Jul 18, 202678 ms
Jul 25, 202677 ms
Aug 1, 202677 ms
Aug 8, 202682 ms
Aug 15, 2026100 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026116 ms
Sep 12, 202681 ms
Sep 19, 202679 ms
Sep 26, 202681 ms
Oct 3, 202671 ms
Oct 10, 202671 ms
Oct 17, 202671 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 titus-hvac.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix61
  • Use efficient cache lifetimes

    12.9 s · 2.4 MB

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

  • Improve image delivery

    9.6 s · 1.8 MB

    17 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.6 s faster on a phone.

  • Render-blocking requests

    2.2 s

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

  • Mobile performance score: 61

    61/100

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

  • Reduce unused JavaScript

    450 ms · 59 KiB

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

  • Font display

    250 ms

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

  • Reduce unused CSS

    150 ms · 13 KiB

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

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • 1 third-party service on the page

    1 third-party service load with your homepage (TrustArc), adding 116 KiB and 144 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Document request latency

    17 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 97 but mobile only 61. 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.

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.8 s

    14.8 s

    Your largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Nexus OR Suite connects air, light, and more, to delive…”.

  • Time to Interactive: 14.8 s

    14.8 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • 23 images without width and height

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

  • Cumulative Layout Shift: 0.131

    0.131

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

  • Tap response (INP) held steady for real visitors

    +1%

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

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

    +14%

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

5 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 CLS: 0.03

    0.03

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • Page weight: 2.7 MB in 60 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 60 requests on a phone: images 2.3 MB (28), scripts 204 KiB (13) and fonts 82 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (2.0 MB) 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.

  • About 0.8 g of CO₂ per visit

    0.75 g

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

2 checks passed
  • 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

14 to fixGoogle 6778
  • Certain ARIA roles must be contained by particular parents (4 elements)

    Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 4 tap targets too small

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

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

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

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 27 elements on the page fail 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.

  • 2 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

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

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

SEO

9 to fixGoogle 6756
  • 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 long (91 characters)

    Your title is 91 characters, so Google will cut it off around 60: “Titus HVAC | Engineering Innovative Air Distribution Solutions | Redefine Your Comfort Zo…”.

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • 13 links with vague text

    13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 83 internal links, 15 external

    The homepage links to 83 pages on titus-hvac.com and 15 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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://www.titus-hvac.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 (401 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    / and https://www.titus-hvac.com/Products all use the title “Titus HVAC | Engineering Innovative Air Distribution Solutions | Rede…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.titus-hvac.com/search%20reps/sales, https://www.titus-hvac.com/main/about, https://www.titus-hvac.com/main/about/Speakers, https://www.titus-hvac.com/main/about/Comfort%20Zone, https://www.titus-hvac.com/main/about/Certifications and https://www.titus-hvac.com/main/about/Our%20Legacy and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://www.titus-hvac.com/search%20reps/sales, https://www.titus-hvac.com/main/about/Comfort%20Zone, https://www.titus-hvac.com/main/about/Certifications, https://www.titus-hvac.com/main/about/Our%20Legacy, https://www.titus-hvac.com/main/about/Newsroom and https://www.titus-hvac.com/Products and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 66 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 10093
  • 25 small tap targets

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

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

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

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

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

    The homepage carries about 298 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact” and “Learn More”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Class Schedule”, “Webinar Schedule” and “Contact”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 1 other company contacted

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

2 checks passed
  • Consent tool: TrustArc

    A consent management tool (TrustArc) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 titus-hvac.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 45 issues on titus-hvac.com, including 11 speed issues, 9 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