Website review, no card needed
housedigest.com website review
Visit site (opens in a new tab)Reviewed 11 October 202631 issues · 83 checks
This review found 31 issues worth fixing on housedigest.com, 10 of them high impact, across 83 checks. The most urgent: improve image delivery. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.0 s |
| Apr 25, 2026 | 992 ms |
| May 2, 2026 | 951 ms |
| May 9, 2026 | 909 ms |
| May 16, 2026 | 884 ms |
| May 23, 2026 | 873 ms |
| May 30, 2026 | 875 ms |
| Jun 6, 2026 | 865 ms |
| Jun 13, 2026 | 874 ms |
| Jun 20, 2026 | 879 ms |
| Jun 27, 2026 | 877 ms |
| Jul 4, 2026 | 888 ms |
| Jul 11, 2026 | 890 ms |
| Jul 18, 2026 | 894 ms |
| Jul 25, 2026 | 896 ms |
| Aug 1, 2026 | 899 ms |
| Aug 8, 2026 | 902 ms |
| Aug 15, 2026 | 922 ms |
| Aug 22, 2026 | 924 ms |
| Aug 29, 2026 | 927 ms |
| Sep 5, 2026 | 920 ms |
| Sep 12, 2026 | 910 ms |
| Sep 19, 2026 | 922 ms |
| Sep 26, 2026 | 928 ms |
| Oct 3, 2026 | 952 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 179 ms |
| Apr 25, 2026 | 173 ms |
| May 2, 2026 | 171 ms |
| May 9, 2026 | 164 ms |
| May 16, 2026 | 159 ms |
| May 23, 2026 | 158 ms |
| May 30, 2026 | 159 ms |
| Jun 6, 2026 | 159 ms |
| Jun 13, 2026 | 158 ms |
| Jun 20, 2026 | 156 ms |
| Jun 27, 2026 | 152 ms |
| Jul 4, 2026 | 149 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 161 ms |
| Aug 22, 2026 | 167 ms |
| Aug 29, 2026 | 168 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 168 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 173 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.4 s · 619 KiB20 images could be 619 KiB 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.
Use efficient cache lifetimes
750 ms · 645 KiB12 files are served with short cache lifetimes, so returning visitors download them again (645 KiB).
Reduce unused JavaScript
320 ms · 790 KiBAbout 790 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 320 ms faster on a phone.
Mobile performance score: 71
71/100Your mobile performance score is 71 (desktop: 81). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (adthrive.com, Google Tag Manager and Google/Doubleclick Ads and others), adding 1.7 MB and 705 ms of main-thread time.
adthrive.com adds 260 ms
260 msadthrive.com costs a phone 260 ms of main-thread work and 731 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 Tag Manager adds 188 ms
188 msGoogle Tag Manager costs a phone 188 ms of main-thread work and 308 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 220 ms. During a long task the page ignores taps.
Reduce unused CSS
14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.1 s of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 15.2 s
15.2 sThe page becomes fully interactive after 15.2 s. Good is under 3.8 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Red-hot heater in a garage, placed next to various items.”.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 294 ms
294 msScripts block taps and scrolling for 294 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 179 ms to 173 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 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: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 109 ms
109 msReal visitors wait 109 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: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 349 ms
349 msReal visitors wait 349 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.7 MB in 153 requests
2.7 MBYour homepage downloads 2.7 MB in 153 requests on a phone: scripts 1.6 MB (21), images 935 KiB (35) and other files 101 KiB (85). Under 2 MB keeps phones on slow connections fast.
16 images below the first screen load straight away
16 images further down the page (521 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
84 KiB3 images are downloaded at several times the size a phone draws them, for example intro-1791432891.webp at 780 px wide, shown at 170 px. Resized copies would save about 84 KiB.
About 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.1 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
81 text elements with low contrast
81 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
30 tap targets too small
30 tap targets are too small or too close together to hit reliably with a finger.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “House Digest | Home Improvement, Design, DIY, & Celebrity Interviews”.
31 links with vague text
31 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 H1 headlines
There are 2 <h1> headlines (“” and “Gas Or Electric: Which Is The Cheaper Option For …”). One clear main headline is easier for people and search engines.
208 internal links, 20 external
The homepage links to 208 pages on housedigest.com and 20 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “The best tips, guides, and inspiration on home improvement, decor, DIY projects, and interviews with celebrities from y…”.
Canonical URL set
The canonical URL is https://www.housedigest.com/.
Structured data in place
Structured data found: Organization.
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://www.housedigest.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.housedigest.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,822 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages slow to respond
https://www.housedigest.com/category/exclusives, https://www.housedigest.com/category/home-improvement and https://www.housedigest.com/category/interior-remodel took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 76 found) and read each the way a search engine does.
7 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://pixel.rubiconproject.com/token?pid=49096&us_privacy=1YNY.
58 small tap targets
58 of 107 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener') https://www.housedigest.com/:1000:8”.
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 731 words of copy
The homepage carries about 731 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Comscore, Criteo, Google Ads, Google Analytics and Google Tag Manager and 1 more (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 2 of them by other companies (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.
41 other companies contacted
Loading the homepage contacts 41 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 housedigest.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- 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 31 issues on housedigest.com, including 11 speed issues, 3 SEO issues and 6 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.