10.4 sec in total
2.6 sec
7.7 sec
110 ms
Welcome to stanleyjohn.net homepage info - get ready to check Stanleyjohn best content right away, or after learning these important things about stanleyjohn.net
http://www.stanleyjohn.net/wp-content/uploads/ac_uploads/x7661767.jpg.pagespeed.ic.2cqQejJnic.jpg
Visit stanleyjohn.netWe analyzed Stanleyjohn.net page load time and found that the first response time was 2.6 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
stanleyjohn.net performance score
2588 ms
45 ms
96 ms
131 ms
108 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 83% of them (76 requests) were addressed to the original Stanleyjohn.net, 8% (7 requests) were made to S9.mylivechat.com and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Stanleyjohn.net.
Page size can be reduced by 511.2 kB (65%)
792.5 kB
281.3 kB
In fact, the total size of Stanleyjohn.net main page is 792.5 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. 45% of websites need less resources to load. Javascripts take 516.7 kB which makes up the majority of the site volume.
Potential reduce by 43.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 43.1 kB or 81% of the original size.
Potential reduce by 33.3 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. Obviously, Stanleyjohn needs image optimization as it can save up to 33.3 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 328.8 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 328.8 kB or 64% of the original size.
Potential reduce by 106.0 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. Stanleyjohn.net needs all CSS files to be minified and compressed as it can save up to 106.0 kB or 84% of the original size.
Number of requests can be reduced by 61 (71%)
86
25
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stanleyjohn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.stanleyjohn.net
2588 ms
style.css
45 ms
gallery-bank.css
96 ms
prettyPhoto.css
131 ms
res_tab_icon.css
108 ms
A.jrsm.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.o7JsrTIjpV.css
87 ms
ajax-load-more.css
108 ms
A.styles.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.Io6Fs5icoS.css
227 ms
slideshow.min.css
168 ms
gspeech.css
148 ms
A.the-tooltip.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.aH_EDekbX0.css
160 ms
jquery.fancybox-1.3.4.css
180 ms
A.jquery-ui.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.ZcP7bjlGzZ.css
161 ms
style.css
171 ms
A.font-awesome.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.UDN9xC06gJ.css
174 ms
A.round_social_media_buttons.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.dy_dBoFVu2.css
194 ms
A.style.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.4TJ5oYdeBj.css
221 ms
jquery.bxslider.css
223 ms
A.sms.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.CjTeIu9h2n.css
222 ms
A.social_widget.css,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.cf.m_WrXL1wBU.css
294 ms
gallery.min.css
250 ms
style.css+admin.css.pagespeed.cc.g4LaxEOeXu.css
284 ms
jquery.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.ocognCjcS2.js
344 ms
jquery-migrate.min.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.mhpNjdU8Wl.js
268 ms
jquery.masonry.min.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.UebAqiBiKa.js
277 ms
isotope.pkgd.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.FhD4sxxTFQ.js
306 ms
imgLiquid.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.t8p8bc_gTV.js
329 ms
jquery.prettyPhoto.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.JvGyesZDEd.js
333 ms
jrsm-jquery.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.Ck_7iNHX5l.js
337 ms
youtube-class-playlist.js
370 ms
slideshow.min.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.WH3nxRduOY.js
372 ms
color.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.rzUdAlxEwW.js
375 ms
jQueryRotate.2.1.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.UrzgfKkjZS.js
380 ms
easing.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.mATJmZT0x4.js
381 ms
mediaelement-and-player.min.js
428 ms
jquery.fancybox-1.3.4.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.glAItEcrrT.js
392 ms
jquery-ui.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.rJaqGQjdLU.js
158 ms
mdocs-script.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.RamHF3vfwI.js
418 ms
functions.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.0R49EXwfiC.js
419 ms
chatinline.aspx
170 ms
mylivechat.css
432 ms
jquery.bxslider.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.O-86spNFEx.js
403 ms
jquery.cookie.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.DM4lWdVAvg.js
367 ms
jquery.validate.min.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.ZU1gPxuDoB.js
393 ms
jquery.validate.min.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.CQbw1kmD3g.js
368 ms
kpc_ajax.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.FfjTKXlze9.js
378 ms
ajax-load-more.min.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.SicZKc1HYF.js
356 ms
jquery.form.min.js,qver=25b017e79d4a0ee711ef9b151355ed80-2014.02.05.pagespeed.jm.Yi1BP7OrFU.js
374 ms
scripts.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.yzzruv2iX0.js
365 ms
bootstrap-tabdrop.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.3mWZUU_pP8.js
393 ms
livechat.aspx
202 ms
banner.js,qver=25b017e79d4a0ee711ef9b151355ed80.pagespeed.jm.VD_KEqub2_.js
376 ms
gspeech_pro.js,qver=1.0.3.pagespeed.jm.VpsResk2fy.js
364 ms
gspeech.js,qver=1.0.3.pagespeed.jm.xyT_HrnkYz.js
336 ms
ga.js
34 ms
xtop-icons-jp.png.pagespeed.ic.IOdKzVs4xf.png
66 ms
xtop-icons-mp.png.pagespeed.ic.73DiCQOs2W.png
81 ms
xtop-icons-ep.png.pagespeed.ic.CPfpcdtfjg.png
82 ms
xlogo.png.pagespeed.ic.gIIQ6Ol-wD.png
85 ms
latest-new.jpg
126 ms
xtw.png.pagespeed.ic.bXEGeFHAht.png
100 ms
xin.png.pagespeed.ic.9GY7dydLv_.png
122 ms
xgoogle.png.pagespeed.ic.y0iGvj1kgR.png
124 ms
xfb.png.pagespeed.ic.6-oc5jpzvN.png
135 ms
pinterest-icon.png
164 ms
slide31-950x280.gif
320 ms
slide1.gif
203 ms
slide2.gif
317 ms
loading.gif
198 ms
job_img.jpg
214 ms
matrimony_img.jpg
313 ms
edu_img.jpg
313 ms
fot_logo.png
314 ms
logo.png
1384 ms
1.gif
314 ms
2.gif
317 ms
6.gif
317 ms
3.gif
336 ms
8.gif
356 ms
0.gif
354 ms
page.js
38 ms
Helvetica%20CE%20Regular.ttf
371 ms
__utm.gif
21 ms
__utm.gif
11 ms
jsml.js
71 ms
resources.aspx
81 ms
InPageBubbleTop_1.png
39 ms
inpage_bubbletop_close.png
37 ms
inpage_1_exit.png
71 ms
inpage_1_up.png
104 ms
__utm.gif
34 ms
speaker32.png
55 ms
stanleyjohn.net SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stanleyjohn.net 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 Stanleyjohn.net 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.
stanleyjohn.net
Open Graph data is detected on the main page of Stanleyjohn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: