vh-info.com website review

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

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

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

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

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

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

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

Google Tag Manager costs a phone 306 ms of main-thread work and 768 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 2,395 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

7 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google/Doubleclick Ads and others), adding 831 KiB and 315 ms of main-thread time.

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

5 long tasks block the main thread while loading, the longest for 87 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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “VH Info Is A SaaS Link Building Agency Built For B2B Softwa…”. Most of its time is element render delay (6.0 s).

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.2 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.

3d-male-character-working-laptop-while-sitting-chair.svg weighs 596 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.6 MB in 130 requests on a phone: images 1.2 MB (53), scripts 964 KiB (37) and fonts 196 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

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

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

The homepage links to 106 pages on vh-info.com and 8 external pages.

https://vh-info.com/pricing and https://vh-info.com/brand-mention all use the title “Earn AI Brand Mentions and Reputation Management | VH Info”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://vh-info.com/pricing and https://vh-info.com/brand-mention use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://vh-info.com/white-label-link-building-service, whose canonical is https://vh-info.com/white-label-link-building-services. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://vh-info.com/saas-link-building-services, https://vh-info.com/seo-for-startups, https://vh-info.com/brand-mention, https://vh-info.com/brand-listicle, https://vh-info.com/vh-process and https://vh-info.com/case-study and 1 other took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Class extends value undefined is not a constructor or null”.

Your longest form asks for 21 fields (7 required). Every extra field lowers completion.

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 1,158 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.