homebound.com website review

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

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

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

website-files.com costs a phone 67 ms of main-thread work and 15.4 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 1.3 MB of JavaScript is downloaded but never used on this page.

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

8 images could be 314 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

15 KiB could be saved by minifying JavaScript.

6 KiB JavaScript is shipped twice across bundles.

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 18.9 MB in 198 requests on a phone: media 12.7 MB (10), scripts 3.0 MB (81) and images 1.4 MB (39). Under 2 MB keeps phones on slow connections fast.

2 images (122 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.

2 images further down the page (82 KiB) 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 5.36 g of CO₂e: 643.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.

15 visible links have no text or label, so screen readers cannot say where they go.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your meta description is 193 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 78 pages on homebound.com and 0 external pages.

There is no /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.

/inventory/2409-s-lafayette-st-denver-co-80210 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/inventory/7003-bucknell-dr-dallas-tx-75214, /inventory/1212-candlelight-ln-houston-tx-77018, /inventory/2911-w-bay-view-ave-tampa-fl-33611, /inventory/1445-27th-ave-n-saint-petersburg-fl-33704, /inventory/710-47th-ave-n-saint-petersburg-fl-33703 and /inventory/548-47th-avenue-north-st-petersburg-fl-33703 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

homebound.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

homebound.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 19 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 789 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 14 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.