Website review, no card needed

airefco.com logo

airefco.com website review

Visit site (opens in a new tab)Reviewed 20 October 202657 issues · 101 checks

This review found 57 issues worth fixing on airefco.com, 24 of them high impact, across 101 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
4.3 s3.7 sMay 2Oct 173.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.8 s
May 9, 20263.9 s
May 16, 20263.9 s
May 23, 20263.9 s
May 30, 20264.0 s
Jun 6, 20264.1 s
Jun 13, 20264.2 s
Jun 20, 20264.3 s
Jun 27, 20264.2 s
Jul 4, 20264.1 s
Jul 11, 20264.0 s
Jul 18, 20264.0 s
Jul 25, 20264.0 s
Aug 1, 20264.0 s
Aug 8, 20263.9 s
Aug 15, 20263.9 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
349 ms174 msMay 2Oct 17329 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026194 ms
May 9, 2026195 ms
May 16, 2026194 ms
May 23, 2026195 ms
May 30, 2026196 ms
Jun 6, 2026196 ms
Jun 13, 2026199 ms
Jun 20, 2026201 ms
Jun 27, 2026204 ms
Jul 4, 2026214 ms
Jul 11, 2026224 ms
Jul 18, 2026233 ms
Jul 25, 2026238 ms
Aug 1, 2026239 ms
Aug 8, 2026253 ms
Aug 15, 2026263 ms
Aug 22, 2026280 ms
Aug 29, 2026298 ms
Sep 5, 2026305 ms
Sep 12, 2026311 ms
Sep 19, 2026316 ms
Sep 26, 2026319 ms
Oct 3, 2026326 ms
Oct 10, 2026328 ms
Oct 17, 2026329 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 airefco.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. airefco.com at 0.8 s0.8 s
  2. airefco.com at 1.6 s1.6 s
  3. airefco.com at 2.3 s2.3 s
  4. airefco.com at 3.1 s3.1 s
  5. airefco.com at 3.9 s3.9 s
  6. airefco.com at 4.7 s4.7 s
  7. airefco.com at 5.4 s5.4 s
  8. airefco.com at 6.2 s6.2 s

Speed

13 to fix35
  • Use efficient cache lifetimes

    1.6 s · 5.3 MB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 6.9 s

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

  • Improve image delivery

    3.9 MB

    25 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    300 ms · 1.4 MB

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

  • Google Tag Manager adds 756 ms

    756 ms

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

  • Reduce unused CSS

    460 ms · 110 KiB

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

  • 20 long tasks on the main thread

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

  • 2,940 HTML elements

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

  • Wistia adds 176 ms

    176 ms

    Wistia costs a phone 176 ms of main-thread work and 394 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 Maps adds 141 ms

    141 ms

    Google Maps costs a phone 141 ms of main-thread work and 383 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.

  • Minify JavaScript

    150 ms · 19 KiB

    19 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    32 KiB

    Polyfills for old browsers add 32 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.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

13 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 LCP: 4.6 s

    4.6 s

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • Time to Interactive: 36.1 s

    36.1 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Real-user INP: 353 ms

    353 ms

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

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

    +69%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.136

    0.136

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

  • 17 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

1 checks passed
  • Real-user CLS: 0.01

    0.01

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

Images and page weight

4 to fix28
  • Page weight: 10.7 MB in 417 requests

    10.7 MB

    Your homepage downloads 10.7 MB in 417 requests on a phone: images 6.7 MB (225), scripts 3.6 MB (77) and other files 192 KiB (95). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    3.7 MB

    12 images are downloaded at several times the size a phone draws them, for example Corporate_2023_Residential-Trade_2023_OAA0214OK01-187H at 8,000 px wide, shown at 137 px. Resized copies would save about 3.7 MB.

  • 19 images below the first screen load straight away

    19 images further down the page (4.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.0 g of CO₂ per visit

    3.03 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 8988
  • 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.

  • 3 tap targets too small

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

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4, h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 8593
  • 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.

  • 9 links with vague text

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

  • 4 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 582 internal links, 21 external

    The homepage links to 582 pages on airefco.com and 21 external pages.

7 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Discover top-notch heating, ventilation, and air conditioning products and services for professional contractors and bu…”.

  • One H1 headline

    Your main headline reads: “HVAC”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “HVAC Parts Supply, Heating & Cooling Equipment | Ferguson”.

  • Canonical URL set

    The canonical URL is https://www.ferguson.com/content/industry-solutions/hvac/.

  • Structured data in place

    Structured data found: Article.

  • 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.ferguson.com/sitemap_index.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://www.ferguson.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 (8,666 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix70
  • 2 pages without a title

    https://www.ferguson.com/s/orders and https://www.ferguson.com/s/myLists have no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://www.ferguson.com/s/orders and https://www.ferguson.com/s/myLists have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ferguson.com/stores, whose canonical is https://www.ferguson.com/stores?showMap=true&horizontalView=true&isForm=true. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.ferguson.com/stores, https://www.ferguson.com/s/orders and https://www.ferguson.com/s/myLists have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.ferguson.com/stores took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

6 to fixGoogle 5068
  • 2 broken images

    2 images failed to load on a phone, for example https://i.liadm.com/s/63537?bidder_id=242861&bidder_uuid=3E4E3C-4B0C495B-C516-40E7-BE67-8AFBDFE77107.

  • 6 small tap targets

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

  • 3 third-party cookies

    3 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.”).

  • 2 JavaScript errors while loading

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

  • 1 distorted image

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

  • Missing source maps

    Large scripts ship without source maps.

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

  • About 701 words of copy

    The homepage carries about 701 words of visible text.

5 checks passed
  • 24 calls to action

    The homepage has 24 calls to action, for example “Visit Shop By Job Page”, “Shop Premium Toilet Options from KOHLER®” and “Shop By Industry”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.

  • 45 cookies set on arrival

    45

    Opening the homepage sets 45 cookies (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 airefco.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
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 57 issues on airefco.com, including 26 speed issues, 3 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