joeflyco.com website review

About 1,002 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.5 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Squarespace, Google CDN and Google Tag Manager and others), adding 2.6 MB and 1.4 s of main-thread time.

Squarespace costs a phone 696 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.

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

Polyfills for old browsers add 140 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.

Google CDN costs a phone 353 ms of main-thread work and 734 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.

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 8.4 MB in 146 requests on a phone: images 5.2 MB (19), scripts 2.2 MB (84) and other files 469 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

1 tap target is too small or too close together to hit reliably with a finger.

Your title is only 12 characters: “joeflyco.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 15 <h1> headlines (“Providing Clean Air Since 1967”, “Texas” and “•”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/657b7d3a069e7b58ae3…”.

The homepage links to 264 pages on joeflyco.com and 8 external pages.

Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

https://www.joeflyco.com/lexington and https://www.joeflyco.com/lubbock all use the title “Lubbock | Enhance Air Quality Today — Get Started — joeflyco.com”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.joeflyco.com/lexington and https://www.joeflyco.com/lubbock use the same meta description. A description written for each page earns more clicks.

https://www.joeflyco.com/athens, https://www.joeflyco.com/dallas-fortworth, https://www.joeflyco.com/houston, https://www.joeflyco.com/lexington, https://www.joeflyco.com/lubbock and https://www.joeflyco.com/sanantonio and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.joeflyco.com/athens has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/657b7d3a069e7b58ae371094/115/5c5…”.

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

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,451 words of visible text.

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

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

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.

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