networkcapital.com website review

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

Reduce initial server response time. Google estimates savings of 1.1 s on a phone.

The HTML itself could arrive about 1.1 s sooner: redirects, a slow server response or missing compression delay everything after it.

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

Your mobile performance score is 51 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

Your server takes 1.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

2 images could be 78 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

3 third-party services load with your homepage (FontAwesome CDN, Google Fonts and Better Business Bureau), adding 211 KiB and 15 ms of main-thread time.

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

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

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Inc. Fatest growing companies list”.

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

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

The layout shifts by 0.269 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

3 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-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.3 s 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 6.8 MB in 60 requests on a phone: media 5.5 MB (2), scripts 545 KiB (40) and images 274 KiB (9). Under 2 MB keeps phones on slow connections fast.

3 images (213 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.

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

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

3 links inside paragraphs rely on colour alone to stand out.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 2 <h1> headlines (“Your best life starts here.” and “Apply for a Mortgage or Refinance your Home Online”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

3 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 29 pages on networkcapital.com and 10 external pages.

There is no https://www.networkcapital.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://www.networkcapital.com/build-credit and https://www.networkcapital.com/mortgage/equity all use the title “Home Mortgage & Refinancing Made Simple | Network Capital ®”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.networkcapital.com/energy/energy-savings, https://www.networkcapital.com/home-security/adt, https://www.networkcapital.com/build-credit, https://www.networkcapital.com/personal/light-stream and https://www.networkcapital.com/mortgage/equity have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.networkcapital.com/energy/energy-savings, whose canonical is https://www.networkcapital.com/not-found. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.networkcapital.com/about/about-us has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Large scripts ship without source maps.

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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 424 words of visible text.

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