Tools & Wizards About Us
ww2.greenhouse.io screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ww2.greenhouse.io

Applicant tracking software & hiring platform | Greenhouse

Page Load Speed

3.6 sec in total

First Response

51 ms

Resources Loaded

1.3 sec

Page Rendered

2.2 sec

ww2.greenhouse.io screenshot

About Website

Click here to check amazing Ww 2 Greenhouse content for United States. Otherwise, check out these important facts you probably never knew about ww2.greenhouse.io

More than an applicant tracking software, Greenhouse is a hiring software solution. Hire better with our talent acquisition support and applicant…

Visit ww2.greenhouse.io

Key Findings

We analyzed Ww2.greenhouse.io page load time and found that the first response time was 51 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 55% of websites can load faster.

Performance Metrics

ww2.greenhouse.io performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value3,000 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

ww2.greenhouse.io

51 ms

www.greenhouse.io

63 ms

6si.min.js

165 ms

117871812.js

213 ms

otSDKStub.js

175 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ww2.greenhouse.io, 39% (26 requests) were made to Sharp.services.greenhouse.io and 26% (17 requests) were made to Greenhouse.io. The less responsive or slowest element that took the longest time to load (546 ms) relates to the external source Sharp.services.greenhouse.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 408.5 kB (8%)

Content Size

5.4 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ww2.greenhouse.io main page is 5.4 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 172.3 kB

  • Original 200.1 kB
  • After minification 175.2 kB
  • After compression 27.7 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. This page needs HTML code to be minified as it can gain 24.9 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 172.3 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 53.0 kB

  • Original 4.9 MB
  • After minification 4.8 MB

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. Ww 2 Greenhouse images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 7.7 kB

  • Original 115.2 kB
  • After minification 115.2 kB
  • After compression 107.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-81%

Potential reduce by 175.5 kB

  • Original 217.6 kB
  • After minification 217.6 kB
  • After compression 42.1 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. Ww2.greenhouse.io needs all CSS files to be minified and compressed as it can save up to 175.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (37%)

Requests Now

59

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ww 2 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 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ww2.greenhouse.io

ww2.greenhouse.io

51 ms

www.greenhouse.io

www.greenhouse.io

63 ms

6si.min.js

6si.min.js

165 ms

117871812.js

117871812.js

213 ms

otSDKStub.js

otSDKStub.js

175 ms

styles.min.css

styles.min.css

33 ms

polyfill.min.js

polyfill.min.js

144 ms

htmx.min.js

htmx.min.js

174 ms

answers.css

answers.css

142 ms

answerstemplates.compiled.min.js

answerstemplates.compiled.min.js

171 ms

answers.min.js

answers.min.js

193 ms

forms2.min.js

forms2.min.js

316 ms

demo.min.js

demo.min.js

79 ms

smoothScroll.min.js

smoothScroll.min.js

127 ms

imagesLoaded.min.js

imagesLoaded.min.js

127 ms

main.min.js

main.min.js

127 ms

4b7f52bf-a8f7-4020-85f2-a9bf76903f1d.json

4b7f52bf-a8f7-4020-85f2-a9bf76903f1d.json

179 ms

conv_v3.js

conv_v3.js

218 ms

gtm.js

gtm.js

213 ms

logo.svg

logo.svg

172 ms

Talent-Makers-book-cover-n.png

Talent-Makers-book-cover-n.png

380 ms

stars

stars

448 ms

Greenhouse-Pride-tshirt-n.jpg

Greenhouse-Pride-tshirt-n.jpg

380 ms

Man-sitting-on-desk-while-working-on-laptop-with-a-botanical-plant-behind-nav-image-m.png

Man-sitting-on-desk-while-working-on-laptop-with-a-botanical-plant-behind-nav-image-m.png

440 ms

Greenhouse-two-women-working.jpg

Greenhouse-two-women-working.jpg

454 ms

Three-coworkers-talking-in-a-corporte-office-environment.jpg

Three-coworkers-talking-in-a-corporte-office-environment.jpg

457 ms

Greenhouse-homepage-sourcing-automation-product-image.png

Greenhouse-homepage-sourcing-automation-product-image.png

452 ms

Greenhouse-Recruiting-scorecard-and-task-list.png

Greenhouse-Recruiting-scorecard-and-task-list.png

447 ms

Greenhouse-Recruiting-job-marketing-tools.png

Greenhouse-Recruiting-job-marketing-tools.png

506 ms

Greenhouse-Recruiting-DEI-tools.png

Greenhouse-Recruiting-DEI-tools.png

455 ms

Greenhouse-Recruiting-job-kickoff-form.png

Greenhouse-Recruiting-job-kickoff-form.png

521 ms

Greenhouse-Recruiting-candidate-survey-results.png

Greenhouse-Recruiting-candidate-survey-results.png

517 ms

Greenhouse-Recruiting-Scorecard2.jpg

Greenhouse-Recruiting-Scorecard2.jpg

506 ms

Pinterest-career-page.jpg

Pinterest-career-page.jpg

508 ms

Greenhouse-Recruiting-pipeline-report.jpg

Greenhouse-Recruiting-pipeline-report.jpg

515 ms

Home-Image-5-1.png

Home-Image-5-1.png

517 ms

Greenhouse-Recruiting-reporting.jpg

Greenhouse-Recruiting-reporting.jpg

519 ms

Greenhouse-Onboarding-meet-your-team.png

Greenhouse-Onboarding-meet-your-team.png

522 ms

Greenhouse-Onboarding-customization.png

Greenhouse-Onboarding-customization.png

524 ms

Greenhouse-Onboarding-welcome-experience.png

Greenhouse-Onboarding-welcome-experience.png

521 ms

Greenhouse-Onboarding-tasks_2022-04-14-025706_aqkn.png

Greenhouse-Onboarding-tasks_2022-04-14-025706_aqkn.png

524 ms

Greenhouse-Onboarding-feedback-results.png

Greenhouse-Onboarding-feedback-results.png

546 ms

DHome-Image-7_2x.png

DHome-Image-7_2x.png

540 ms

Greenhouse-Onboarding-welcome-experience.jpg

Greenhouse-Onboarding-welcome-experience.jpg

541 ms

Greenhouse-Onboarding-process.jpg

Greenhouse-Onboarding-process.jpg

536 ms

Greenhouse-Onboarding-tasks.jpg

Greenhouse-Onboarding-tasks.jpg

543 ms

Greenhouse-Onboarding-new-hire-survey.jpg

Greenhouse-Onboarding-new-hire-survey.jpg

540 ms

getForm

getForm

202 ms

location

location

288 ms

search.svg

search.svg

38 ms

hamburger.svg

hamburger.svg

39 ms

UntitledSansWeb-Regular.woff

UntitledSansWeb-Regular.woff

103 ms

UntitledSansWeb-Medium.woff

UntitledSansWeb-Medium.woff

179 ms

UntitledSansWeb-Light.woff

UntitledSansWeb-Light.woff

178 ms

UntitledSerifWeb-Regular.woff

UntitledSerifWeb-Regular.woff

180 ms

brightedge3.php

brightedge3.php

221 ms

prefooter-image3.png

prefooter-image3.png

139 ms

getForm

getForm

114 ms

chevron-down-white.svg

chevron-down-white.svg

69 ms

external-link-arrow-white.svg

external-link-arrow-white.svg

67 ms

forms2.css

forms2.css

118 ms

forms2-theme-glow.css

forms2-theme-glow.css

142 ms

otBannerSdk.js

otBannerSdk.js

34 ms

en.json

en.json

321 ms

styles.min.css

styles.min.css

82 ms

forms2.css

forms2.css

144 ms

Accessibility Review

ww2.greenhouse.io accessibility score

80

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

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

Low

No form fields have multiple labels

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

ww2.greenhouse.io best practices score

75

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

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ww2.greenhouse.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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ww2.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 Ww2.greenhouse.io main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ww2.greenhouse.io

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