2.8 sec in total
398 ms
2.2 sec
265 ms
Visit greendoor.io now to see the best up-to-date Greendoor content and also check out these interesting facts you probably never knew about greendoor.io
Greendoor is built for today's home buyer. Search homes for sale by monthly payment. Choose us to represent you and we'll pay your first month's mortgage payment*.
Visit greendoor.ioWe analyzed Greendoor.io page load time and found that the first response time was 398 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
greendoor.io performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value9.3 s
1/100
25%
Value8.0 s
22/100
10%
Value510 ms
57/100
30%
Value0.012
100/100
15%
Value11.6 s
18/100
10%
398 ms
140 ms
337 ms
392 ms
269 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 77% of them (30 requests) were addressed to the original Greendoor.io, 8% (3 requests) were made to Ssl.google-analytics.com and 5% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (907 ms) belongs to the original domain Greendoor.io.
Page size can be reduced by 472.1 kB (15%)
3.1 MB
2.7 MB
In fact, the total size of Greendoor.io main page is 3.1 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. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 50.2 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 50.2 kB or 82% of the original size.
Potential reduce by 61.8 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. Greendoor images are well optimized though.
Potential reduce by 301.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 301.2 kB or 52% of the original size.
Potential reduce by 58.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. Greendoor.io needs all CSS files to be minified and compressed as it can save up to 58.9 kB or 61% of the original size.
Number of requests can be reduced by 29 (83%)
35
6
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greendoor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
Home.aspx
398 ms
ContentHome.css
140 ms
Main.css
337 ms
font-awesome.css
392 ms
SignIn.css
269 ms
responsivemobilemenu.css
267 ms
selectric.css
276 ms
prism.css
275 ms
css
39 ms
js
93 ms
jquery.min.js
517 ms
jquery-ui.min.js
649 ms
responsivemobilemenu.js
344 ms
retina.js
343 ms
jquery.placeholder.js
404 ms
jquery.placeholder.min.js
409 ms
cookieHelper.js
410 ms
prism.js
456 ms
jquery.minicolors.min.js
473 ms
jquery.selectric.js
550 ms
WebResource.axd
549 ms
ScriptResource.axd
528 ms
ScriptResource.axd
550 ms
ScriptResource.axd
586 ms
geo.js
587 ms
jsdebug
603 ms
loginHelper.js
552 ms
2870963.js
225 ms
ga.js
438 ms
ContentHome-iPhone6.css
471 ms
sdk.js
443 ms
font
602 ms
xclose.png
431 ms
homeimg.jpg
907 ms
Main.css
429 ms
fontawesome-webfont.woff
102 ms
__utm.gif
51 ms
sdk.js
7 ms
__utm.gif
17 ms
greendoor.io accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
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 IDs are not unique
greendoor.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
greendoor.io SEO score
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
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 Greendoor.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 Greendoor.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.
greendoor.io
Open Graph description is not detected on the main page of Greendoor. 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: