7.7 sec in total
1.7 sec
5.2 sec
885 ms
Click here to check amazing Realtygenerator content. Otherwise, check out these important facts you probably never knew about realtygenerator.com
A pioneer in lead generation and contact management systems, Market Leader has been helping agents and teams manage, grow, and thrive since 1999.
Visit realtygenerator.comWe analyzed Realtygenerator.com page load time and found that the first response time was 1.7 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
realtygenerator.com performance score
1652 ms
14 ms
33 ms
24 ms
16 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Realtygenerator.com, 20% (12 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Success.marketleader.com.
Page size can be reduced by 926.1 kB (47%)
2.0 MB
1.0 MB
In fact, the total size of Realtygenerator.com main page is 2.0 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. 75% 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 782.1 kB which makes up the majority of the site volume.
Potential reduce by 37.9 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 37.9 kB or 76% of the original size.
Potential reduce by 5.4 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. Realtygenerator images are well optimized though.
Potential reduce by 400.0 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 400.0 kB or 70% of the original size.
Potential reduce by 482.8 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. Realtygenerator.com needs all CSS files to be minified and compressed as it can save up to 482.8 kB or 87% of the original size.
Number of requests can be reduced by 33 (69%)
48
15
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Realtygenerator. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.marketleader.com
1652 ms
A.validationEngine.jquery.css,qver=2.7.pagespeed.cf.c5u28DXnmF.css
14 ms
css
33 ms
A.style.css,qver=1.2.6.pagespeed.cf.Hj4ZHGlZgV.css
24 ms
chosen.css,qver=4.4.2.pagespeed.ce.Vsa_OxYQ1h.css
16 ms
frontend.css,qver=4.4.2.pagespeed.ce.tgJFo7L34Z.css
18 ms
A.slick.css,qver=4.4.2.pagespeed.cf.msKDgHWV-o.css
21 ms
A.slick-slider-style.css,qver=4.4.2.pagespeed.cf.P3JpeXBBTE.css
32 ms
css
35 ms
A.style.css,qver=2.5.9.pagespeed.cf.Jun021dGdG.css
46 ms
A.shortcodes.css,qver=3.0.pagespeed.cf.dyVNhSjDoh.css
76 ms
A.shortcodes_responsive.css,qver=3.0.pagespeed.cf.gfG_ljpb3h.css
39 ms
A.magnific_popup.css,qver=2.5.9.pagespeed.cf.WnJCcUqpb8.css
82 ms
wp-featherlight.min.css,qver=0.3.0.pagespeed.ce.fKYf2_QEEm.css
73 ms
A.colorbox.min.css,qver=2.7.2.pagespeed.cf.FQK04LWSBq.css
82 ms
A._,Mco.9n3QwNUOdG.css.pagespeed.cf.hrR9KVVKsA.css
78 ms
A._,Mco.rRu7aySMro.css.pagespeed.cf.dgqASYNBXv.css
78 ms
jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js
108 ms
jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js
107 ms
slick.min.js,qver=4.4.2.pagespeed.jm.GAVikQOqk7.js
127 ms
ga597820.js
160 ms
frontend-builder-global-functions.js,qver=2.5.9.pagespeed.jm.E7Z3F7IoA0.js
159 ms
adrotate,_library,_jquery.adrotate.clicktracker.js+monarch,_js,_idle-timer.min.js,qver==1.2.6.pagespeed.jc.7DcPW3fwXs.js
161 ms
plugins,_monarch,_js,_custom.js,qver==1.2.6+themes,_Divi,_js,_custom.js,qver==2.5.9.pagespeed.jc.f-6RnnJfox.js
167 ms
jquery.fitvids.js,qver==2.5.9+waypoints.min.js,qver==2.5.9+jquery.magnific-popup.js,qver==2.5.9.pagespeed.jc.bki9eS3iZa.js
241 ms
frontend-builder-scripts.js,qver=2.5.9.pagespeed.jm.74SGEfrH5l.js
246 ms
wp-featherlight,_js,_wpFeatherlight.pkgd.min.js,qver==0.3.0+lightbox-plus,_js,_jquery.colorbox.1.5.9-min.js,qver==1.5.9.pagespeed.jc.PKPXqO3GRr.js
265 ms
wp-emoji-release.min.js
151 ms
4btj8l
2328 ms
4btj8s
2320 ms
4bthtx
2309 ms
analytics.js
111 ms
1.JiBnMqyl6S.gif
100 ms
xphone.png.pagespeed.ic.V7uN4ST5TM.png
101 ms
xlogo.png.pagespeed.ic.3nLTXWAAQy.png
101 ms
xagentToolshero.jpg.pagespeed.ic.tfc0AWhG98.jpg
346 ms
xleadsHero.jpg.pagespeed.ic.iXQu_-Wh_7.jpg
351 ms
xslide3.jpg.pagespeed.ic.22PRcgSEkq.jpg
109 ms
xtestimonial-bg-1.jpg.pagespeed.ic.-htw-K5UGD.jpg
108 ms
xbeInTheKnowBackground.jpg.pagespeed.ic.s1niVfWcbg.jpg
296 ms
xblurredCellphone-1.jpg.pagespeed.ic.4u3rLVJzeZ.jpg
352 ms
xblue-pattern-background-1.jpg.pagespeed.ic.wZ2Zx7gvR9.jpg
299 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
286 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
286 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
288 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
288 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
289 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
288 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
289 ms
ETmodules_v2_4.ttf
251 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
247 ms
PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf
247 ms
PRmiXeptR36kaC0GEAetxmYImPRL1w80NlYTQ8LOqf4.ttf
247 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
245 ms
PRmiXeptR36kaC0GEAetxk7Gbs5Oj9RrfpUUQRHsz5w.ttf
245 ms
collect
22 ms
xteam-tools-blue.png.pagespeed.ic.JKYnlJ5H3_.png
99 ms
xleads-blue.png.pagespeed.ic.qYZLq4LZfI.png
19 ms
xagent-tools-blue.png.pagespeed.ic.t_ReDt93mo.png
98 ms
piUtils.js
21 ms
css
17 ms
realtygenerator.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Realtygenerator.com 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 Realtygenerator.com 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.
realtygenerator.com
Open Graph description is not detected on the main page of Realtygenerator. 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: