Tools & Wizards About Us
checkr.io screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

checkr.io

Checkr – Employee Background Screening for Companies

Page Load Speed

1.3 sec in total

First Response

56 ms

Resources Loaded

646 ms

Page Rendered

553 ms

checkr.io screenshot

About Website

Click here to check amazing Checkr content for United States. Otherwise, check out these important facts you probably never knew about checkr.io

Checkr platform uses AI to make background screening more efficient, speed up the hiring process, fill roles faster & drive more revenue. ✓ Start for free!

Visit checkr.io

Key Findings

We analyzed Checkr.io page load time and found that the first response time was 56 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

checkr.io performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value6,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.11

87/100

15%

TTI (Time to Interactive)

Value26.8 s

0/100

10%

Network Requests Diagram

checkr.io

56 ms

checkr.com

132 ms

gtm.js

190 ms

j.php

184 ms

munchkin.js

159 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Checkr.io, 83% (54 requests) were made to A-us.storyblok.com and 6% (4 requests) were made to Checkr.com. The less responsive or slowest element that took the longest time to load (416 ms) relates to the external source A-us.storyblok.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 485.8 kB (71%)

Content Size

687.6 kB

After Optimization

201.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Checkr.io main page is 687.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. HTML takes 546.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 461.7 kB

  • Original 546.7 kB
  • After minification 546.4 kB
  • After compression 85.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 461.7 kB or 84% of the original size.

Image Optimization

-13%

Potential reduce by 16.9 kB

  • Original 128.5 kB
  • After minification 111.6 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Checkr needs image optimization as it can save up to 16.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 7.2 kB

  • Original 12.4 kB
  • After minification 12.1 kB
  • After compression 5.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 7.2 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (11%)

Requests Now

62

After Optimization

55

  • Images
  • JavaScript

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Checkr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

checkr.io

checkr.io

56 ms

checkr.com

checkr.com

132 ms

gtm.js

gtm.js

190 ms

j.php

j.php

184 ms

munchkin.js

munchkin.js

159 ms

A5323877-8760-429f-86ee-e47f13ca89671.js

A5323877-8760-429f-86ee-e47f13ca89671.js

253 ms

logo-uber-gray.svg

logo-uber-gray.svg

232 ms

webpack-runtime-17485b7dc6eea59bf3eb.js

webpack-runtime-17485b7dc6eea59bf3eb.js

196 ms

framework-f07f3433e97ab0257523.js

framework-f07f3433e97ab0257523.js

271 ms

app-8097ba491f7c1fcaf379.js

app-8097ba491f7c1fcaf379.js

278 ms

logo-uber-dark.svg

logo-uber-dark.svg

163 ms

dominos-pizza-logo-slate.svg

dominos-pizza-logo-slate.svg

188 ms

199 ms

208 ms

logo-warby-parker-gray.svg

logo-warby-parker-gray.svg

185 ms

logo-warby-parker-dark.svg

logo-warby-parker-dark.svg

178 ms

logo-kimpton-gray.svg

logo-kimpton-gray.svg

181 ms

logo-kimpton-dark.svg

logo-kimpton-dark.svg

190 ms

logo-doordash-gray.svg

logo-doordash-gray.svg

193 ms

logo-doorash-dark.svg

logo-doorash-dark.svg

195 ms

logo-angi-gray.svg

logo-angi-gray.svg

198 ms

logo-angi-dark.svg

logo-angi-dark.svg

207 ms

candidate-portal_completereport-mobile-no-device.svg

candidate-portal_completereport-mobile-no-device.svg

200 ms

dashboard_customer-desktop-no-device.svg

dashboard_customer-desktop-no-device.svg

211 ms

242 ms

209 ms

ecosystem-icon.svg

ecosystem-icon.svg

223 ms

speed-icon.svg

speed-icon.svg

220 ms

global-icon.svg

global-icon.svg

226 ms

229 ms

242 ms

240 ms

240 ms

241 ms

243 ms

261 ms

245 ms

416 ms

244 ms

261 ms

244 ms

260 ms

260 ms

260 ms

266 ms

munchkin.js

munchkin.js

93 ms

104 ms

visitWebPage

visitWebPage

102 ms

90 ms

89 ms

84 ms

91 ms

77 ms

87 ms

79 ms

75 ms

73 ms

70 ms

70 ms

71 ms

71 ms

65 ms

61 ms

57 ms

54 ms

Accessibility Review

checkr.io accessibility score

100

Accessibility Issues

Best Practices

checkr.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

checkr.io SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Checkr.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Checkr.io main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

checkr.io

Open Graph data is detected on the main page of Checkr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: