Website review, no card needed
hotair.com website review
Visit site (opens in a new tab)Reviewed 11 October 202640 issues · 89 checks
This review found 40 issues worth fixing on hotair.com, 14 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 943 ms |
| Apr 25, 2026 | 947 ms |
| May 2, 2026 | 953 ms |
| May 9, 2026 | 952 ms |
| May 16, 2026 | 955 ms |
| May 23, 2026 | 951 ms |
| May 30, 2026 | 948 ms |
| Jun 6, 2026 | 945 ms |
| Jun 13, 2026 | 937 ms |
| Jun 20, 2026 | 932 ms |
| Jun 27, 2026 | 925 ms |
| Jul 4, 2026 | 929 ms |
| Jul 11, 2026 | 933 ms |
| Jul 18, 2026 | 928 ms |
| Jul 25, 2026 | 930 ms |
| Aug 1, 2026 | 928 ms |
| Aug 8, 2026 | 927 ms |
| Aug 15, 2026 | 932 ms |
| Aug 22, 2026 | 931 ms |
| Aug 29, 2026 | 929 ms |
| Sep 5, 2026 | 934 ms |
| Sep 12, 2026 | 943 ms |
| Sep 19, 2026 | 973 ms |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 91 ms |
| Apr 25, 2026 | 89 ms |
| May 2, 2026 | 88 ms |
| May 9, 2026 | 88 ms |
| May 16, 2026 | 89 ms |
| May 23, 2026 | 91 ms |
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 92 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 94 ms |
| Aug 1, 2026 | 94 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 97 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
Speed
Reduce unused JavaScript
4.3 s · 745 KiBAbout 745 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Use efficient cache lifetimes
3.9 s · 1.1 MB56 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Render-blocking requests
2.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 89). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (osano.com, piano and Google/Doubleclick Ads and others), adding 1,009 KiB and 1.5 s of main-thread time.
osano.com adds 316 ms
316 msosano.com costs a phone 316 ms of main-thread work and 105 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 299 ms. During a long task the page ignores taps.
piano adds 283 ms
283 mspiano costs a phone 283 ms of main-thread work and 146 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/Doubleclick Ads adds 251 ms
251 msGoogle/Doubleclick Ads costs a phone 251 ms of main-thread work and 277 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.
Reduce unused CSS
250 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 250 ms faster on a phone.
Improve image delivery
245 KiB7 images could be 245 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
111 KiBPolyfills for old browsers add 111 KiB JavaScript that modern phones do not need.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Phones get a much slower page than desktops
Desktop scores 89 but mobile only 37. 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.0 s
16.0 sYour largest element takes 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.5 s
20.5 sThe page becomes fully interactive after 20.5 s. Good is under 3.8 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 926 ms
926 msScripts block taps and scrolling for 926 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 91 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 92 ms
92 msReal visitors wait 92 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 300 ms
300 msReal visitors wait 300 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 179 requests
2.6 MBYour homepage downloads 2.6 MB in 179 requests on a phone: scripts 1.8 MB (52), images 368 KiB (36) and fonts 214 KiB (7). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
b9841910-cf34-44ab-a4a9-261a83af676e-536x311.jpeg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (68 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.
About 0.7 g of CO₂ per visit
0.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.73 g of CO₂e: 87.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
57 images without alt text
57 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (78 characters)
Your title is 78 characters, so Google will cut it off around 60: “HotAir – Politics, Culture, Media, Breaking News from a conservative viewpoint”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (182 characters)
Your meta description is 182 characters; Google truncates after about 160, so the end of your pitch is cut.
207 internal links, 31 external
The homepage links to 207 pages on hotair.com and 31 external pages.
5 checks passed
One H1 headline
Your main headline reads: “HotAir: Breaking Conservative News and Opinion”.
Canonical URL set
The canonical URL is https://hotair.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://hotair.com/sitemaps/sitemapindex-hotair.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,212 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hotair.com/llms.txt (1 KiB, 7 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://hotair.com/authors, which answers with an error. Visitors hit a dead end and search engines drop it.
4 pages share a title
/, https://hotair.com/newsletters, https://hotair.com/hotair-tv-ed-morrissey-show and https://hotair.com/contact-us all use the title “HotAir – Politics, Culture, Media, Breaking News from a conservative …”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://hotair.com/subscribe and https://hotair.com/vip have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://hotair.com/newsletters, https://hotair.com/hotair-tv-ed-morrissey-show and https://hotair.com/contact-us use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://hotair.com/subscribe has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://hotair.com/podcasts, https://hotair.com/subscribe and https://hotair.com/newsletters have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 81 found) and read each the way a search engine does.
3 checks passed
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 14 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 21 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 (“The Topics API is deprecated and will be removed in a future release.”).
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”.
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
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.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 16 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 911 words of copy
The homepage carries about 911 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “JOIN VIP” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 1 more (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
59 other companies contacted
Loading the homepage contacts 59 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 hotair.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 40 issues on hotair.com, including 16 speed issues, 3 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.