testgrid.com website review

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

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

About 1.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.0 s faster on a phone.

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

8 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

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

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

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

YouTube costs a phone 386 ms of main-thread work and 984 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.

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

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

Hubspot costs a phone 263 ms of main-thread work and 546 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 HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

72 KiB could be saved by minifying JavaScript.

21 KiB could be saved by minifying CSS.

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.

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

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

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

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

Your largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hiring Intelligence Platform UX”.

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

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

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

For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.4 s to 5.1 s 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' tap response (inp) went from 128 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.4 MB in 217 requests on a phone: scripts 4.1 MB (61), images 3.1 MB (62) and stylesheets 1.1 MB (19). Under 2 MB keeps phones on slow connections fast.

tabs-3.png weighs 555 KiB. On a phone connection a single image that size takes seconds.

10 images (2.2 MB) 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.

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

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 25 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: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

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

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

There are 8 <h1> headlines (“Hire with confidence. Built on Hiring Intelligenc…”, “What do we do?” and “A solution for every stage of the recruitment pro…”). 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.

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

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

The homepage links to 89 pages on testgrid.com and 4 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://testgrid.com/candidates and https://testgrid.com/psychometric-testing/emotional-intelligence have no meta description, so Google writes the search snippet from whatever text it finds.

https://testgrid.com/assessment-builder and https://testgrid.com/on-demand use the same meta description. A description written for each page earns more clicks.

https://testgrid.com/candidates has no <h1> headline, so visitors and search engines get no clear main topic.

https://testgrid.com/candidates, https://testgrid.com/assessment-builder, https://testgrid.com/on-demand, https://testgrid.com/psychometric-testing, https://testgrid.com/psychometric-testing/aptitude-assessments and https://testgrid.com/psychometric-testing/behavioural-assessments and 7 others took over 3 s to send their HTML from our server.

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

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 559 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 2 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 32 cookies, 12 of them by other companies (measured from a US location before any click).

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