vanhack.com website review

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.

4 images could be 725 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

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

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

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

16 long tasks block the main thread while loading, the longest for 2.1 s. During a long task the page ignores taps.

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

Google Tag Manager costs a phone 776 ms of main-thread work and 738 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 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 580 ms faster on a phone.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

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

Desktop scores 56 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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.

Your largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HIRE GET HIRED Hire World Class Tech Talent Get the quality…”.

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

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

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

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

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 6.1 MB in 133 requests on a phone: scripts 1.9 MB (45), images 1.8 MB (28) and other files 1.5 MB (49). Under 2 MB keeps phones on slow connections fast.

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

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

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

<svg> elements with an img or image role must have alternative text: 20 elements on the page fail this check, rated serious by axe-core.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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: 41 elements on the page fail this check, rated moderate 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.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 23 pages on vanhack.com and 39 external pages.

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

Your homepage links to https://vanhack.com/contact_us, which answers with an error. Visitors hit a dead end and search engines drop it.

https://vanhack.com/product, https://vanhack.com/about, https://vanhack.com/pricing, https://vanhack.com/resources, https://vanhack.com/terms-of-use and https://vanhack.com/privacy-policy all use the title “VanHack Talent Pool | Find your next great tech hire”. Search engines can't tell which page to show for a search, so each competes with the others.

https://vanhack.com/product, https://vanhack.com/talent, https://vanhack.com/success-stories, https://vanhack.com/about, https://vanhack.com/pricing and https://vanhack.com/resources and 3 others use the same meta description. A description written for each page earns more clicks.

https://vanhack.com/product, https://vanhack.com/success-stories, https://vanhack.com/pricing, https://vanhack.com/get-hired, https://vanhack.com/vanna and https://vanhack.com/resources and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

50 of 68 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.

Social proof on the homepage: “520+ companies”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 744 words of visible text.

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