5.3 sec in total
1.2 sec
3.7 sec
444 ms
Click here to check amazing Jojn content. Otherwise, check out these important facts you probably never knew about jojn.net
1分赛车
Visit jojn.netWe analyzed Jojn.net page load time and found that the first response time was 1.2 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
jojn.net performance score
1176 ms
12 ms
36 ms
57 ms
216 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 10% of them (14 requests) were addressed to the original Jojn.net, 18% (25 requests) were made to Apis.google.com and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Images.sitethumbshot.com.
Page size can be reduced by 469.8 kB (53%)
882.7 kB
412.9 kB
In fact, the total size of Jojn.net main page is 882.7 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. 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. Javascripts take 602.2 kB which makes up the majority of the site volume.
Potential reduce by 150.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 150.1 kB or 77% of the original size.
Potential reduce by 6.2 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, Jojn needs image optimization as it can save up to 6.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 283.7 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 283.7 kB or 47% of the original size.
Potential reduce by 29.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. Jojn.net needs all CSS files to be minified and compressed as it can save up to 29.8 kB or 75% of the original size.
Number of requests can be reduced by 76 (60%)
127
51
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jojn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
jojn.net
1176 ms
jquery.min.js
12 ms
jquery-ui.min.js
36 ms
plusone.js
57 ms
reset.css
216 ms
960.css
218 ms
text.css
216 ms
hotaru_js_1385493989.js
210 ms
hotaru_css_1310744772.css
209 ms
style.css
312 ms
addthis_widget.js
53 ms
cb=gapi.loaded_0
31 ms
adsbygoogle.js
13 ms
FB.Share
54 ms
ga.js
27 ms
images.sitethumbshot.com
2265 ms
lg-bookmark-en.gif
14 ms
images.sitethumbshot.com
328 ms
images.sitethumbshot.com
323 ms
images.sitethumbshot.com
316 ms
images.sitethumbshot.com
374 ms
images.sitethumbshot.com
311 ms
jojn_logo.gif
247 ms
rss_10.png
245 ms
Gtry.png
237 ms
ca-pub-9830813895430270.js
139 ms
zrt_lookup.html
220 ms
show_ads_impl.js
59 ms
__utm.gif
169 ms
fastbutton
188 ms
ads
298 ms
images.sitethumbshot.com
246 ms
comment.png
166 ms
tweet-this.png
169 ms
show_ads.js
72 ms
widgets.js
141 ms
jsapi
74 ms
t13n
76 ms
ifr
70 ms
q
176 ms
element.js
89 ms
images.sitethumbshot.com
162 ms
images.sitethumbshot.com
199 ms
images.sitethumbshot.com
166 ms
poweredby_FFFFFF.gif
64 ms
rss_16.png
144 ms
jojn_twitter.gif
143 ms
cb=gapi.loaded_0
53 ms
cb=gapi.loaded_1
53 ms
osd.js
47 ms
181 ms
t13n
101 ms
xd_arbiter.php
60 ms
xd_arbiter.php
87 ms
fastbutton
93 ms
6369297.jpg
269 ms
fastbutton
84 ms
fastbutton
83 ms
m_js_controller.js
60 ms
abg.js
111 ms
fastbutton
147 ms
share_button.php
138 ms
favicon
141 ms
googlelogo_color_112x36dp.png
160 ms
nessie_icon_tiamat_white.png
90 ms
fastbutton
188 ms
s
77 ms
x_button_blue2.png
54 ms
qeKvIRsJabD.js
162 ms
7GFXgco-uzw.png
152 ms
fastbutton
142 ms
fastbutton
116 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
47 ms
fastbutton
148 ms
fastbutton
131 ms
ads
218 ms
fastbutton
72 ms
branding.css
23 ms
branding.css
6 ms
33 ms
likebox.php
240 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
105 ms
transliteration.css
18 ms
transliteration.I.js
17 ms
37 ms
css
312 ms
cb=gapi.loaded_1
19 ms
cb=gapi.loaded_2
126 ms
badge
299 ms
inputtools.js
107 ms
410ucuAGgaJ.css
221 ms
tSbl8xBI27R.css
224 ms
q68gy-v_YMF.js
275 ms
FJmpeSpHpjS.js
376 ms
0wM5s1Khldu.js
299 ms
1bNoFZUdlYZ.js
255 ms
postmessageRelay
738 ms
rs=AGLTcCPxxcsaEHPLIxgGb9au86GYFsrXHA
154 ms
slide.js
300 ms
translateelement.css
708 ms
main.js
775 ms
300lo.json
540 ms
counter.5524cceca805eb4b9b2b.js
113 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
650 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
740 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
148 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
342 ms
sh.8e5f85691f9aaa082472a194.html
125 ms
nessie_icon_magazine_black.png
216 ms
nessie_icon_magazine_white.png
493 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
441 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
462 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
498 ms
shares.json
439 ms
11150768_913604162035440_6040748064486114833_n.png
452 ms
555774_576045812457945_1392855791_n.jpg
509 ms
1157534_523508634403467_1384652355_n.jpg
534 ms
11152353_961764353843040_4363530480365130001_n.jpg
528 ms
10372787_1572756439709820_8416803634971498722_n.jpg
532 ms
10980735_866179700091437_8844254468209751152_n.jpg
860 ms
12439054_1682037972068642_2487194048653965749_n.jpg
539 ms
wL6VQj7Ab77.png
339 ms
s7jcwEQH7Sx.png
338 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
363 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
397 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
85 ms
activeview
116 ms
3193398744-postmessagerelay.js
176 ms
rpc:shindig_random.js
149 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
77 ms
element_main.js
116 ms
syndication
170 ms
364481870987137026
406 ms
cb=gapi.loaded_0
39 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
76 ms
translate_24dp.png
17 ms
l
47 ms
googlelogo_color_42x16dp.png
12 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
7 ms
jojn.net SEO score
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jojn.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Jojn.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.
jojn.net
Open Graph description is not detected on the main page of Jojn. 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: