nedshome.com website review

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

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

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

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

Google Tag Manager costs a phone 668 ms of main-thread work and 1,015 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

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

Facebook costs a phone 205 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.

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

hsappstatic.net costs a phone 101 ms of main-thread work and 368 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.

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

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 CSS.

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

Your largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WELCOME TO NED'S HOME YOUR ONE-STOP SHOP FOR EXTERIOR HOME …”.

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

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

Scripts block taps and scrolling for 472 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.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 129 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 4.0 MB in 144 requests on a phone: scripts 3.0 MB (51), fonts 419 KiB (7) and images 333 KiB (25). Under 2 MB keeps phones on slow connections fast.

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

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

ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

There are 2 <h1> headlines (“Welcome to Ned's Home” and “Welcome to Ned's Home”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness, Product, Service and VideoObject) but with 2 problems, for example “Service: missing name”.

The homepage links to 85 pages on nedshome.com and 13 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) 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://nedshome.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://nedshome.com/services/gutter-cleaning, https://nedshome.com/services/gutter-installation, https://nedshome.com/services/pest-control, https://nedshome.com/services/pest-control/home, https://nedshome.com/services/pest-control/commercial and https://nedshome.com/services/pest-control/rodents and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97193349&tm=gtm002&Ver=2&mid=de139068-902c-455e-802f-ed42645106d7&bo=1&sid=4ba064e0ce3d11f1a04f879bc7585db0&vid=4ba06030ce3d11f1922c3d583e4103b3&vids=1&msclkid=N&pi=91.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 image is served at too low a resolution for sharp phone screens.

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

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.

The homepage carries about 824 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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