3.8 sec in total
283 ms
2.2 sec
1.3 sec
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.ioWe analyzed Checkr.io page load time and found that the first response time was 283 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
checkr.io performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value31.4 s
0/100
25%
Value26.9 s
0/100
10%
Value64,400 ms
0/100
30%
Value0
100/100
15%
Value85.4 s
0/100
10%
283 ms
266 ms
89 ms
75 ms
97 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Checkr.io, 18% (14 requests) were made to Use.typekit.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (789 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 397.1 kB (25%)
1.6 MB
1.2 MB
In fact, the total size of Checkr.io main page is 1.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 73.3 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 73.3 kB or 79% of the original size.
Potential reduce by 30.0 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. Checkr images are well optimized though.
Potential reduce by 96.9 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 96.9 kB or 60% of the original size.
Potential reduce by 196.9 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Checkr.io needs all CSS files to be minified and compressed as it can save up to 196.9 kB or 84% of the original size.
Number of requests can be reduced by 26 (43%)
61
35
The browser has sent 61 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 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
checkr.com
283 ms
fpb5djp.js
266 ms
css
89 ms
modernizr.min.js
75 ms
jquery.js
97 ms
video.js
293 ms
main.css
7 ms
scripts-min.js
222 ms
wp-embed.min.js
8 ms
wp-emoji-release.min.js
21 ms
3f
86 ms
compatibility.css
12 ms
logo.svg
122 ms
arrow_dropdown.svg
536 ms
arrow-right_yellow.svg
532 ms
arrow-right_blue-dark.svg
675 ms
arrow-right_blue.svg
539 ms
9949035f-6226-4080-a14a-bf7d94ffb1e1.woff
444 ms
xsqfMpYt6B_LuTen4TCRKJK9iuDFFzSl_cYuLt5JY8jffOcREN32IgCjMPMfHMItgI4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.eot
440 ms
e35IMPk79TcO6B5l97mriTzV2R7-sOIe4Sds8EJC5QCffOeREN32IgCjMPMfHMItgX4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.eot
576 ms
XSyheYgdKdNq9ynWHbmxa0B1QuGUi9FMmy05Co2earbffO7REN32IgCjMPMfHMIt2q4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.eot
662 ms
u3qKkchQ5FcHygV9p5H2SLFqG0RjpkIw430Q6DrYl-wffOHREN32IgCjMPMfHMItI94MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.eot
662 ms
jf6gkVBXe4TeQke0NYAd4n1hVenrNEAOgg8Vx6RLHiMffO7REN32IgCjMPMfHMIt26.eot
787 ms
-6owP9bMnTmC4MW6Vna_ZI9JpNSVdMhY6gkk3i6mvDbffOHREN32IgCjMPMfHMItIb.eot
789 ms
o4C-WVxmLP4ZYXXr0mydTCJkCIukpUDz2lxUIGaP_N6ffOcREN32IgCjMPMfHMItgM.eot
788 ms
0DiLnJtfMeH3KN6A393wWDuNxlJeQqio_yE-P50BkMSffOeREN32IgCjMPMfHMItg3.eot
789 ms
agQCPafszZUdOOBd-mv51n-ZqVrU9XAFa-wPwUJUzBjffODGgsMdeMI6MK6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.eot
708 ms
cbj54D7s13bWa261deZKOonLqtY1Hoe4N3uYw6oW3s6ffOxGgsMdeMI6MK6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.eot
710 ms
MxSeFv_tiTq0VRSdUgAGhBR6JH0YWoz3v9Yl8dpYC0vffODGgsMdeMI6MK6g5Mb.eot
788 ms
08TGobd25Kf81yGSoLUUmf7Y6g0qpn5Q8hqbUk6CZ7IffOxGgsMdeMI6MK6g5MS.eot
788 ms
p.gif
701 ms
Checkr_Hero_poster.png
435 ms
napbs-accredited.svg
410 ms
563548.js
630 ms
analytics.js
469 ms
update.js
289 ms
checkr_header_industries-1.jpg
227 ms
checkr_home_financial2x.jpg
226 ms
checkr_home_retail2x-1.jpg
227 ms
checkr_home_transportation2x.jpg
148 ms
checkr_home_on-demand2x.jpg
202 ms
checkr_home_p2p_alt.jpg
228 ms
checkr_home_softwaretech2x.jpg
252 ms
checkr_home_healthcare2x.jpg
267 ms
checkr_home_nonprofit2x.jpg
273 ms
checkr_home_staffing2x.jpg
271 ms
checkr_home_smallbusiness2x.jpg
272 ms
checkr_home_highereducation2x.jpg
275 ms
checkr_home_manufacturing.jpg
270 ms
checkr_header_industries-1-76x20.jpg
280 ms
zenefits-76x16.gif
342 ms
instacart-logo@2x-76x15.png
268 ms
instacart-logo@2x.png
138 ms
home-computer_easy.svg
136 ms
Handy@2x-76x35.jpg
136 ms
Uber_white_2@2x-76x19.jpeg
136 ms
home-mobile.svg
137 ms
logo_grubhub_update-76x27.gif
138 ms
warby-parker-76x14.gif
139 ms
home-automation.svg
194 ms
home-user_check.svg
201 ms
home-analytics.svg
143 ms
home-magnify_glass.svg
118 ms
user-76x76.gif
118 ms
icon_twitter.svg
91 ms
fake-promo.png
78 ms
linkedin.svg
76 ms
angellist.svg
71 ms
i.png
66 ms
collect
20 ms
home-lock_alt.svg
8 ms
collect
46 ms
home-communications.svg
6 ms
ga-audiences
30 ms
instagram.svg
16 ms
facebook.svg
4 ms
__ptq.gif
24 ms
checkr.io accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
checkr.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
checkr.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
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.
checkr.io
Open Graph description is not detected on the main page of Checkr. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: