ghrr.com website review

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

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

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

8 third-party services load with your homepage (Osano CMP, Google Tag Manager and Hotjar and others), adding 949 KiB and 1.0 s of main-thread time.

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

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

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

Osano CMP costs a phone 299 ms of main-thread work and 72 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.

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

About 151 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.

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

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

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 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Want to make better hiring decisions? Upgrade to a more int…”.

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

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

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

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

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

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

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-31, real Chrome visitors' tap response (inp) went from 101 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.1 MB in 79 requests on a phone: scripts 948 KiB (43), images 846 KiB (9) and fonts 143 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example home-title-alt.png at 1,920 px wide, shown at 301 px. Resized copies would save about 109 KiB.

1 image (140 KiB) is 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 0.58 g of CO₂e: 69.9 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”.

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

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

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

1 form field has 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.

Your title is 70 characters, so Google will cut it off around 60: “Background Checks, Employment… | DISA Global Solutions - Formerly GHRR”.

Structured data found (BreadcrumbList, LocalBusiness, Organization and WebPage) but with 2 problems, for example “LocalBusiness: missing name”.

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

The homepage links to 19 pages on ghrr.com and 3 external pages.

Your Organization JSON-LD is missing name, url, logo, 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.

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

/contact/contact-sales, /resources/blog and /contact-us/contact-sales declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/invite-us-to-tour-next-bid is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, /contact/contact-sales, /resources/blog and /contact-us/contact-sales all use the title “Background Checks, Employment… | DISA Global Solutions - Formerly GHRR”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/contact-us/applicant-support, /support, /contact-us, /contact-us/customer-support, /contact-us/compliance and /contact-us/contact-us and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/contact/contact-sales, /resources/blog and /contact-us/contact-sales use the same meta description. A description written for each page earns more clicks.

/contact/contact-sales, /resources/blog and /contact-us/contact-sales have no <h1> headline, so visitors and search engines get no clear main topic.

/contact-us, /invite-us-to-tour-next-bid, /solutions, /technology/partners and /contact/contact-sales took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://service.force.com/embeddedservice/5.0/esw.min.css' from origin 'https://ghrr.com' …”.

Chrome logged issues while loading the page (“Content security policy”).

4 links go through two or more redirects, for example https://ghrr.com/invite-us-to-tour-next-bid.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

ghrr.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

ghrr.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage has only about 118 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

DMARC is set to p=none, so mail pretending to be ghrr.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

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