60.7 sec in total
11.6 sec
48.5 sec
546 ms
Visit 680.com now to see the best up-to-date 680 content for China and also check out these interesting facts you probably never knew about 680.com
时间财富网原名威客中国威客网,是威客行业领先的威客网。网站汇聚数百万设计师,设计公司,网站软件开发人员及兼职从业人员为公司及大众提供设计、文案、开发、营销等全方位的创意服务。
Visit 680.comWe analyzed 680.com page load time and found that the first response time was 11.6 sec and then it took 49 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 26 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
680.com performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value13.2 s
0/100
25%
Value9.3 s
12/100
10%
Value80 ms
99/100
30%
Value0.426
22/100
15%
Value7.9 s
44/100
10%
11639 ms
3931 ms
2311 ms
15388 ms
6271 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 24% of them (30 requests) were addressed to the original 680.com, 19% (24 requests) were made to Wk.p.680.com and 10% (12 requests) were made to Js.680.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Sp2.680.com.
Page size can be reduced by 398.4 kB (16%)
2.5 MB
2.1 MB
In fact, the total size of 680.com main page is 2.5 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. 25% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 126.3 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 126.3 kB or 83% of the original size.
Potential reduce by 169.9 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. 680 images are well optimized though.
Potential reduce by 74.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 74.1 kB or 67% 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. 680.com needs all CSS files to be minified and compressed as it can save up to 28.2 kB or 80% of the original size.
Number of requests can be reduced by 15 (16%)
95
80
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 680. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.680.com
11639 ms
index3.0.css
3931 ms
tip-yellow.css
2311 ms
jquery.js
15388 ms
hd.js
6271 ms
in3.0.js
2768 ms
jquery.floatDiv.js
5561 ms
jquery.poshytip.min.js
3222 ms
aq_auth.js
11765 ms
bottom1.2.js
469 ms
tongji.js
465 ms
logo1.jpg
3460 ms
dkhs.jpg
18669 ms
bass.gif
4467 ms
20160407115229820831.png
14151 ms
tui_285_80.jpg
3069 ms
2016030122335487120_2703078.jpg
3205 ms
2014011621244825412_2789721.jpg
1765 ms
2015011921450839325_1313612.jpg
3032 ms
2015092814430840404_2629680.jpg
2396 ms
2015042618271727501_3005669.jpg
20071 ms
zx_dian.jpg
15376 ms
bottom_1200.png
3377 ms
ad_389121_710_272.jpg
12697 ms
ad_387284_710_272.jpg
15840 ms
ad_389168_710_272.jpg
20064 ms
ad_389244_710_272.jpg
20064 ms
ad_388958_710_272.jpg
20065 ms
vk_8549764_710_272.jpg
20065 ms
vk_2714781_710_272.jpg
20066 ms
vk_1313612_710_272.jpg
20066 ms
ad_387376_710_272.jpg
20067 ms
add2.jpg
20067 ms
tag-255.jpg
20067 ms
ad_384447_285_80.jpg
20067 ms
ad_382203_285_80.jpg
20068 ms
vk_39177_295_90.jpg
20068 ms
vk_8457743_295_90.jpg
20068 ms
vk_9381822_295_90.jpg
20069 ms
vk_longbo_280_80.jpg
20069 ms
vk_8434118_280_80.jpg
20069 ms
vk_2789721_280_80.jpg
20069 ms
vk_1066842_280_80.jpg
20070 ms
vk_3265537_280_80.jpg
20069 ms
vk_8504286_280_80.jpg
20070 ms
2013122710231829687_2682132.jpg
6427 ms
328863.png
4823 ms
361204.png
5347 ms
379671.png
9620 ms
374144.png
13483 ms
370749.png
20067 ms
364950.png
9479 ms
349170.png
10377 ms
8796257_280_150.jpg
11148 ms
icon11_03.png
2994 ms
vikecn_icon.png
6486 ms
xlx.gif
5059 ms
minbao.png
2704 ms
xm_icon.png
3631 ms
ad3.jpg
12713 ms
vikecn_icon_quan.png
10110 ms
20160407114338926619.png
3017 ms
20160407095630699543.jpg
7396 ms
201604071624028750.png
11453 ms
bottom_1000.png
2956 ms
680_sy_btn.png
18510 ms
zz.jpg
1279 ms
ebs.png
2982 ms
weixin.jpg
13406 ms
phone.jpg
4864 ms
png-zhiding.png
1860 ms
png-tisheng.png
4782 ms
zuan2.gif
3936 ms
zuan3.gif
3952 ms
cap1.gif
3951 ms
zuan4.gif
5328 ms
cap5.gif
4370 ms
cap3.gif
4399 ms
logo.jpg
20057 ms
680-top-bg.png
4455 ms
faxq.png
3344 ms
ss.jpg
1901 ms
244090.jpg
6374 ms
114057.jpg
4943 ms
155172.jpg
4265 ms
273444.jpg
4724 ms
243025.jpg
4906 ms
ad15.jpg
5178 ms
aa_06.jpg
5813 ms
aa_07.jpg
6596 ms
aa_03.jpg
6802 ms
png-jiaji.png
6273 ms
ad103.jpg
11016 ms
ad1.jpg
10638 ms
ad4.jpg
14535 ms
ad105.jpg
12043 ms
22344951_1618826.jpg
2613 ms
22016012316583026988_8549764.jpg
3301 ms
22016010903225500651_1229516.jpg
6256 ms
2016030321073475151_8202269.jpg
5570 ms
2016020119053413975_39177.jpg
2714 ms
2016030911592622024_9611922.jpg
4047 ms
2016030416583092357_9392395.jpg
2849 ms
2016011016075103041_2316382.png
20046 ms
2015121418115444571_9381802.jpg
4926 ms
2016031415535728135_9609461.png
12179 ms
2015122112032214654_1066842.jpg
7474 ms
2016021412553721852_9594206.png
7635 ms
2015062610553424825_384114.png
20044 ms
2015061217572834739_2033275.jpg
4594 ms
2015051814151394165_1767876.jpg
2782 ms
2015101910534807895_9328870.jpg
3444 ms
shangbiao.png
19746 ms
ib.png
8809 ms
c.php
4039 ms
stat.htm
255 ms
core.php
797 ms
cklog3.1.asp
5141 ms
1115 ms
sprite.png
5187 ms
tip-yellow_arrows.gif
5586 ms
9.gif
983 ms
hy_83x30.png
4826 ms
app.gif
839 ms
680.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
680.com 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
Issues were logged in the Issues panel in Chrome Devtools
680.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 680.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 680.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
680.com
Open Graph description is not detected on the main page of 680. 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: