Website review, no card needed
hgtv.com website review
Visit site (opens in a new tab)Reviewed 11 October 202629 issues · 88 checks
This review found 29 issues worth fixing on hgtv.com, 12 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.1 s |
| Apr 25, 2026 | 1.3 s |
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 136 ms |
| Apr 25, 2026 | 137 ms |
| May 2, 2026 | 137 ms |
| May 9, 2026 | 137 ms |
| May 16, 2026 | 136 ms |
| May 23, 2026 | 136 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 139 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 138 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 138 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
Render-blocking requests
1.9 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Reduce unused JavaScript
1.4 s · 304 KiBAbout 304 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
3,154 HTML elements
The page has 3,154 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
700 ms · 158 KiB52 files are served with short cache lifetimes, so returning visitors download them again (158 KiB).
5 third-party services on the page
5 third-party services load with your homepage (sndimg.com, Optanon and Skimbit and others), adding 1.2 MB and 350 ms of main-thread time.
sndimg.com adds 128 ms
128 mssndimg.com costs a phone 128 ms of main-thread work and 792 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.
Optanon adds 90 ms
90 msOptanon costs a phone 90 ms of main-thread work and 302 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 97 ms. During a long task the page ignores taps.
Reduce unused CSS
20 KiBAbout 20 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
19 KiB2 images could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Phones get a much slower page than desktops
Desktop scores 94 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 464 ms of it running JavaScript. That is comfortably low.
Server response: 42 ms
42 msYour server sent the HTML in 42 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.6 s
9.6 sYour largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Halloween Front Porch”.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Time to Interactive: 9.6 s
9.6 sThe page becomes fully interactive after 9.6 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
38 images without width and height
38 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 136 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 124 ms
124 msReal visitors wait 124 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 468 ms
468 msReal visitors wait 468 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 57 ms
57 msScripts block the page for only 57 ms while loading. Good is under 200 ms.
Images and page weight
2 images below the first screen load straight away
2 images further down the page (89 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.35 g of CO₂e: 42.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.2 MB in 88 requests
1.2 MBYour homepage downloads 1.2 MB in 88 requests on a phone: scripts 537 KiB (7), images 434 KiB (47) and fonts 90 KiB (4). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (7 elements)
Certain ARIA roles must contain particular children: 7 elements on the page fail this check, rated critical by axe-core.
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 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 (90 elements)
All page content should be contained by landmarks: 90 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
ARIA role should be appropriate for the element (7 elements)
ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h6 and h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 122 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (93 characters)
Your title is 93 characters, so Google will cut it off around 60: “Home Design, Decorating and Remodeling Ideas, Landscaping, Kitchen and Bathroom Design | …”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
Open Graph partly set
Open Graph is missing 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.
178 internal links, 74 external
The homepage links to 178 pages on hgtv.com and 74 external pages.
6 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Let HGTV help you transform your home with pictures and inspiration for interior design, home decor, landscape design, …”.
One H1 headline
Your main headline reads: “HGTV Homepage”.
Canonical URL set
The canonical URL is https://www.hgtv.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.hgtv.com/sitemaps/sitemap_hgtv_index.xml.
AI search readiness
No llms.txt
There is no https://www.hgtv.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,870 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.hgtv.com/shows/tv-schedule has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 115 found) and read each the way a search engine does.
6 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.
Titles are unique
Every page we checked has its own title.
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
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
13 of 15 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
A 10-field form
Your longest form asks for 10 fields (0 required). Every extra field lowers completion.
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 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 1,314 words of copy
The homepage carries about 1,314 words of visible text.
2 checks passed
8 calls to action
The homepage has 8 calls to action, for example “TV Schedule”, “Shop” and “See TV Schedule”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Amazon Ads, Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 hgtv.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 29 issues on hgtv.com, including 13 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.