66.1 sec in total
3.1 sec
62.9 sec
185 ms
Click here to check amazing Java Eye content for Japan. Otherwise, check out these important facts you probably never knew about javaeye.com
Java编程,Spring Struts Webwork框架深入,XMLHTTP Ajax开发,Java Web开发,Java企业应用,Java设计模式,Java开源框架,Java应用服务器,Rich Client讨论,Ruby编程,Ruby DSL开发,Ruby on rails实践,JavaScript编程,敏捷软件开发XP TDD,软件配置管理,软件测试,项目管理UML,数据库,C#/.ne...
Visit javaeye.comWe analyzed Javaeye.com page load time and found that the first response time was 3.1 sec and then it took 63 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
javaeye.com performance score
3090 ms
2167 ms
6767 ms
61 ms
1731 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Javaeye.com, 10% (7 requests) were made to Pos.baidu.com and 9% (6 requests) were made to Csdnim.qtmojo.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source T12.baidu.com.
Page size can be reduced by 399.0 kB (37%)
1.1 MB
689.7 kB
In fact, the total size of Javaeye.com main page is 1.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. 40% of websites need less resources to load. Javascripts take 502.5 kB which makes up the majority of the site volume.
Potential reduce by 54.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. This page needs HTML code to be minified as it can gain 11.2 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 54.9 kB or 81% of the original size.
Potential reduce by 6.7 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. Java Eye images are well optimized though.
Potential reduce by 309.1 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 309.1 kB or 62% of the original size.
Potential reduce by 28.2 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. Javaeye.com needs all CSS files to be minified and compressed as it can save up to 28.2 kB or 82% of the original size.
Number of requests can be reduced by 35 (51%)
68
33
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Java Eye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
www.iteye.com
3090 ms
new_homepage.css
2167 ms
application.js
6767 ms
AllyesDeliver.min.js
61 ms
getcmsad.ashx
1731 ms
tracking.js
9044 ms
ga.js
8 ms
logo.gif
254 ms
63371977078839471_%E5%89%AF%E6%9C%AC.jpg
684 ms
_BFF03EB6-A497-44D3-A6CF-2BF71E0B71AF_.jpg
17047 ms
icon_last_post.gif
513 ms
40406440-9eee-3cbe-a70d-f0e69dfedd0b.jpg
508 ms
eb3bcb04-f1f0-426b-abe7-209b0e8c4760.jpg
515 ms
a8ac9c16-10a7-37b5-9e94-9e1d771fcd48.jpg
517 ms
group-logo.gif
776 ms
af8ab93d-9559-3d4e-9cc8-5901c8bc5220.jpg
798 ms
group-logo.gif
799 ms
c9f66038-7478-3388-8086-d20c1f535495.jpg
800 ms
9b233690-61f3-3380-a50f-a9499b1157cc.png
1016 ms
87eaf24f-812a-3463-8e65-e3197d2ad8c2.png
1138 ms
2500388b-2dbf-3fb5-bee6-58cb9e751496.png
11347 ms
87ff2595-e925-3f95-b18e-c5e4244539f9-thumb.png
1175 ms
6ebe3551-cea7-3b44-be44-5d6100b36579-thumb.bmp
1178 ms
4a57dd27-6a9a-3ef9-854d-7d73b5d3a2fd-thumb.jpg
2467 ms
87a9c6ac-c0db-3aef-ad90-2c9cd6a1c700-thumb.jpg
1562 ms
user-logo-thumb.gif
2942 ms
biaoshi.gif
1566 ms
delay.min.js
30 ms
__utm.gif
14 ms
line_gray.gif
3058 ms
s
650 ms
gpt.js
7 ms
s
1851 ms
pubads_impl_81.js
6 ms
container.html
28 ms
ads
378 ms
expansion_embed.js
6 ms
ads
313 ms
s
647 ms
ads
282 ms
s
650 ms
c.js
893 ms
acom
2460 ms
dot_blue.gif
778 ms
s
3654 ms
acom
1752 ms
acom
1093 ms
s
1924 ms
adx.php
854 ms
u=2353534177,3171867597&fm=76
3392 ms
u=1856364587,2693382950&fm=76
20340 ms
bg.png
498 ms
acom
501 ms
adx.php
426 ms
u=2355213793,3180214524&fm=76
5329 ms
u=2049025532,2396797062&fm=76
1472 ms
acom
432 ms
logo_bg.gif
522 ms
shadow.png
510 ms
line_white.gif
510 ms
acom
481 ms
adx.php
432 ms
u=1771494726,2586260724&fm=76
6172 ms
u=1157930711,1419799990&fm=76
6154 ms
spinner.gif
421 ms
track
4905 ms
o.htm
868 ms
wh.js
698 ms
ac.js
1203 ms
javaeye.com SEO score
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Javaeye.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Javaeye.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.
javaeye.com
Open Graph description is not detected on the main page of Java Eye. 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: