2.1 sec in total
16 ms
1.9 sec
119 ms
Visit greenhouse.io now to see the best up-to-date Greenhouse content for United States and also check out these interesting facts you probably never knew about greenhouse.io
Get everything you need to hire better and achieve strategic growth, all-together with the Greenhouse hiring platform.
Visit greenhouse.ioWe analyzed Greenhouse.io page load time and found that the first response time was 16 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
greenhouse.io performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value7.3 s
4/100
25%
Value10.7 s
7/100
10%
Value3,830 ms
1/100
30%
Value0.097
90/100
15%
Value25.8 s
0/100
10%
16 ms
162 ms
24 ms
23 ms
45 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Greenhouse.io, 50% (48 requests) were made to Cdn2.hubspot.net and 8% (8 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (787 ms) relates to the external source Cdn2.hubspot.net.
Page size can be reduced by 1.1 MB (34%)
3.3 MB
2.1 MB
In fact, the total size of Greenhouse.io main page is 3.3 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 49.1 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 49.1 kB or 79% of the original size.
Potential reduce by 173.2 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. Greenhouse images are well optimized though.
Potential reduce by 606.7 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 606.7 kB or 69% of the original size.
Potential reduce by 272.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. Greenhouse.io needs all CSS files to be minified and compressed as it can save up to 272.9 kB or 84% of the original size.
Number of requests can be reduced by 44 (56%)
79
35
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenhouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
greenhouse.io
16 ms
www.greenhouse.io
162 ms
jquery-1.7.1.js
24 ms
public_common.css
23 ms
setup-style.min.css
45 ms
content_download.min.css
34 ms
jquery-1.10.2.js
505 ms
modernizr.js
111 ms
froogaloop2.min.js
46 ms
stylesheet.css
95 ms
owl.carousel.min.js
323 ms
moment.js
126 ms
scripts.js
114 ms
current.js
30 ms
public_common.js
20 ms
Greenhouse-main.min.js
335 ms
oct.js
53 ms
conversion.js
30 ms
slick.min.css
27 ms
analytics.js
100 ms
loader_index.gif
100 ms
logoWhite.png
95 ms
indexBgRight.png
114 ms
indexBgLeft.png
93 ms
modIndexBlock1.png
93 ms
arrowRightSmallWhite.png
90 ms
modIndexBlock2.png
263 ms
modIndexBlock3.png
294 ms
arrowRightSmallWhite.png
233 ms
gettingStartedCalculator.png
246 ms
gettingStartedTraining.png
245 ms
gettingStartedMigration.png
249 ms
gettingStartedSecurity.png
321 ms
gettingStartedSupport.png
353 ms
zenefits-logo@2x.png
462 ms
customersLogoPinterest.jpg
367 ms
customersLogoAirbnb.jpg
402 ms
customersLogoBrightroll.jpg
410 ms
customersLogoVimeo.jpg
425 ms
customersLogoEvernote.jpg
425 ms
customerHeadWilson.jpg
495 ms
red-ventures-logo.png
551 ms
twilio-logo.png
486 ms
customersLogoSurveyMonkey.jpg
613 ms
customersLogoOptimizely.jpg
537 ms
customersLogoWarriors.jpg
551 ms
customersLogoDocusign.jpg
647 ms
logoWhite.png
634 ms
analytics-bg@2x.png
614 ms
logoWhite.png
627 ms
footerHiringBg.png
568 ms
blog-cta-left.png
634 ms
blog-cta-right.png
743 ms
twitter.png
700 ms
facebook.png
787 ms
linkedin.png
682 ms
db59127b-ecde-4b4d-8da8-97aa98407bc1
107 ms
372554.js
81 ms
insight.min.js
73 ms
adsct
201 ms
adsct
96 ms
bat.js
170 ms
163 ms
lineto-akkurat-regular-s.woff
151 ms
lineto-akkurat-light-s.woff
168 ms
lineto-akkurat-bold-s.woff
187 ms
collect
136 ms
47 ms
ga-audiences
21 ms
roundtrip.js
35 ms
__ptq.gif
22 ms
__ptq.gif
12 ms
ALR7I4Q2L5B7DLW5MRDAFK.js
157 ms
16 ms
l
70 ms
out
17 ms
tr
117 ms
21 ms
49 ms
tr
135 ms
out
35 ms
out
35 ms
out
34 ms
out
46 ms
out
49 ms
out
49 ms
44 ms
u.php
53 ms
adsct
32 ms
18 ms
pixel
33 ms
sync
8 ms
377928.gif
10 ms
tap.php
7 ms
in
6 ms
sd
28 ms
greenhouse.io accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
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
No form fields have multiple labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
greenhouse.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
greenhouse.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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenhouse.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 Greenhouse.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.
greenhouse.io
Open Graph data is detected on the main page of Greenhouse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: