26.6 sec in total
1.1 sec
25 sec
513 ms
Welcome to woko.cc homepage info - get ready to check WOKO best content for China right away, or after learning these important things about woko.cc
WOKO!艺考论坛,中国第一艺术高考、艺术考研交流社区,为艺考生提供权威艺考资讯、艺考咨询、艺考资料等服务,致力于做最好的艺考网站。
Visit woko.ccWe analyzed Woko.cc page load time and found that the first response time was 1.1 sec and then it took 25.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
woko.cc performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value2.5 s
90/100
25%
Value5.6 s
54/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value2.2 s
99/100
10%
1138 ms
446 ms
829 ms
573 ms
565 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 64% of them (53 requests) were addressed to the original Woko.cc, 5% (4 requests) were made to Cnbfa.com and 5% (4 requests) were made to Tcss.qq.com. The less responsive or slowest element that took the longest time to load (10.9 sec) relates to the external source Cnzz.mmstat.com.
Page size can be reduced by 437.9 kB (38%)
1.2 MB
716.5 kB
In fact, the total size of Woko.cc main page is 1.2 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 633.5 kB which makes up the majority of the site volume.
Potential reduce by 80.0 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 80.0 kB or 80% of the original size.
Potential reduce by 60.5 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. WOKO images are well optimized though.
Potential reduce by 240.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 240.8 kB or 69% of the original size.
Potential reduce by 56.6 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. Woko.cc needs all CSS files to be minified and compressed as it can save up to 56.6 kB or 77% of the original size.
Number of requests can be reduced by 37 (46%)
80
43
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WOKO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.woko.cc
1138 ms
push.js
446 ms
style_1_common.css
829 ms
style_1_forum_index.css
573 ms
style.css
565 ms
common.js
1380 ms
forum.js
842 ms
logging.js
633 ms
style.css
826 ms
ping.js
1239 ms
discuz_tips.js
733 ms
2.gif
655 ms
kakarun.gif
1020 ms
logo.gif
3022 ms
bgimg.jpg
1624 ms
logo.png
831 ms
qq_login.gif
373 ms
sina_login_btn.png
742 ms
qqgroup.png
369 ms
ad3.jpg
2104 ms
111222h2x6rc76r66o6vvl.jpg
2746 ms
124507optjtyllvpyxyw6x.jpg
1329 ms
105103suxfvrf4exfoh7xr.jpg
2775 ms
103928dgr9yu96ajzy9pkj.jpg
2747 ms
173651yvglmlaedegebpzu.jpg
2445 ms
collapsed_no.gif
3043 ms
forum.gif
3051 ms
collapsed_yes.gif
3290 ms
logo_88_31.gif
3294 ms
ad2.jpg
4226 ms
qq.png
3389 ms
weixin.png
3562 ms
site_qq.jpg
3438 ms
5.gif
652 ms
1.gif
820 ms
logo.png
957 ms
px.png
3575 ms
pn.png
3578 ms
nv.png
3668 ms
qmenu.png
3758 ms
nv_a.png
3938 ms
button1.png
3962 ms
button2.png
4055 ms
followbutton.php
3335 ms
common_extra.js
4087 ms
jquery-1.8.3.min.js
4600 ms
button3.png
3599 ms
search.png
3499 ms
arrwd.gif
3133 ms
pt_item.png
2918 ms
followButton.css
491 ms
34_avatar_small.jpg
2531 ms
chart.png
2543 ms
00_avatar_small.jpg
2308 ms
titlebg.png
2284 ms
66_avatar_small.jpg
2406 ms
79_avatar_small.jpg
2119 ms
24_avatar_small.jpg
2159 ms
26_avatar_small.jpg
2271 ms
95_avatar_small.jpg
2027 ms
39_avatar_small.jpg
2109 ms
04_avatar_small.jpg
2131 ms
03_avatar_small.jpg
2137 ms
bg_flbtn.png
17 ms
followButton.js
33 ms
suda.js
32 ms
sso.js
31 ms
b.gif
929 ms
z_stat.php
1955 ms
stat.htm
164 ms
core.php
681 ms
9.gif
2095 ms
toss_12.gif
228 ms
ODc3ODg3OA==.js
560 ms
stat.php
856 ms
ping_hotclick.js
515 ms
stat.htm
165 ms
core.php
450 ms
pic1.gif
458 ms
9.gif
10882 ms
scrolltop.png
266 ms
app.gif
766 ms
app.gif
1996 ms
woko.cc 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
woko.cc best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
woko.cc SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use legible font sizes
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Woko.cc can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Woko.cc 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.
woko.cc
Open Graph description is not detected on the main page of WOKO. 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: