756 ms in total
83 ms
543 ms
130 ms
Click here to check amazing Mixpanel Greenhouse content for United States. Otherwise, check out these important facts you probably never knew about mixpanel.greenhouse.io
Visit mixpanel.greenhouse.ioWe analyzed Mixpanel.greenhouse.io page load time and found that the first response time was 83 ms and then it took 673 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
mixpanel.greenhouse.io performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value5.8 s
15/100
25%
Value5.8 s
49/100
10%
Value250 ms
84/100
30%
Value0.093
91/100
15%
Value8.0 s
42/100
10%
83 ms
74 ms
40 ms
96 ms
16 ms
Our browser made a total of 24 requests to load all elements on the main page. We found that 13% of them (3 requests) were addressed to the original Mixpanel.greenhouse.io, 83% (20 requests) were made to Mixpanel.okta.com and 4% (1 request) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (105 ms) relates to the external source Mixpanel.okta.com.
Page size can be reduced by 630.4 kB (74%)
853.2 kB
222.8 kB
In fact, the total size of Mixpanel.greenhouse.io main page is 853.2 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. 40% of websites need less resources to load. Javascripts take 532.2 kB which makes up the majority of the site volume.
Potential reduce by 9.8 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 9.8 kB or 63% of the original size.
Potential reduce by 0 B
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. Mixpanel Greenhouse images are well optimized though.
Potential reduce by 375.3 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 375.3 kB or 71% of the original size.
Potential reduce by 245.4 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. Mixpanel.greenhouse.io needs all CSS files to be minified and compressed as it can save up to 245.4 kB or 81% of the original size.
Number of requests can be reduced by 10 (63%)
16
6
The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mixpanel 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 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
mixpanel.greenhouse.io
83 ms
mixpanel.greenhouse.io
74 ms
auth
40 ms
login.htm
96 ms
saasure-min.3820e172545e4d9175871a26f55c4d26.css
16 ms
okta.23baa6f922d537fe2643ee41bb6d4f43.css
32 ms
login.5879ace522334d8f8a828372538107f4.css
25 ms
loginbookmark.b41abff7f7dc0319e76e9540f73d776e.css
32 ms
underscore-1.5.2.1d4e786b5e92a3c936043bd5d0981000.js
25 ms
jquery-1.5.2.min.e85aed5c30d734f1e30646e030d7a817.js
53 ms
jquery.color.8738618224090e7a179a6248cb00d1bb.js
28 ms
jquery-ui-1.8.15.custom.min.802ac99c294f022e9b4ff5ff4ad5750d.js
64 ms
saasure.min.ba60f12fe3cfbcda7dd2ca0aa4f07d98.js
73 ms
respond.min.ff4676c49703a66df7a5ff8dfe5aa444.js
105 ms
security.09d0bb2f0fb4747f6986015df663e08d.js
50 ms
users-1.0.js
61 ms
ajax-loader-big.gif
37 ms
globalFileStoreRecord
38 ms
fileStoreRecord
42 ms
unknown.32c549060b1ade345c06717ffc4067fb.png
24 ms
proximanova-reg-webfont.4bcd85b755307175b40b8e565d4c0bea.woff
27 ms
proximanova-light-webfont.322ffd0cef0cbf426ee2f9b920023271.woff
19 ms
proximanova-sbold-webfont.52a14e27c692ecc32620aada5ac9b0af.woff
31 ms
okticon.dcb81e8766abef779624e2bbcc52d297.woff
37 ms
mixpanel.greenhouse.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.
mixpanel.greenhouse.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mixpanel.greenhouse.io SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mixpanel.greenhouse.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mixpanel.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.
mixpanel.greenhouse.io
Open Graph description is not detected on the main page of Mixpanel Greenhouse. 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: