55.9 sec in total
2.7 sec
52.7 sec
465 ms
Visit funet8.com now to see the best up-to-date Funet 8 content for China and also check out these interesting facts you probably never knew about funet8.com
你好, 欢迎来到好玩吧博客!在这里与您分享最精彩的互联网的好玩的事,在这里有好听的音乐、实用的软件、搞笑且有哲理的漫画、新奇的视频、最新最经典的电影介绍、神奇的网站和一些有用的技巧等
Visit funet8.comWe analyzed Funet8.com page load time and found that the first response time was 2.7 sec and then it took 53.2 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. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
funet8.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value10.0 s
0/100
25%
Value12.2 s
3/100
10%
Value7,890 ms
0/100
30%
Value0.05
99/100
15%
Value17.7 s
4/100
10%
2704 ms
2027 ms
6664 ms
5273 ms
15416 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Funet8.com, 25% (36 requests) were made to Asearch.alicdn.com and 12% (18 requests) were made to Images.funet8.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Img.qj.media8.cn.
Page size can be reduced by 457.5 kB (49%)
932.5 kB
475.0 kB
In fact, the total size of Funet8.com main page is 932.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 479.6 kB which makes up the majority of the site volume.
Potential reduce by 53.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 53.3 kB or 76% of the original size.
Potential reduce by 4.0 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. Funet 8 images are well optimized though.
Potential reduce by 281.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 281.7 kB or 59% of the original size.
Potential reduce by 118.5 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. Funet8.com needs all CSS files to be minified and compressed as it can save up to 118.5 kB or 81% of the original size.
Number of requests can be reduced by 67 (48%)
139
72
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funet 8. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
funet8.com
2704 ms
www.funet8.com
2027 ms
wp-emoji-release.min.js
6664 ms
style.css
5273 ms
jquery.js
15416 ms
ex
946 ms
c.js
1307 ms
cpc_i.js
8190 ms
stat.php
1959 ms
relatedItemsWidget
3935 ms
bootstrap.js
6306 ms
custom.js
5273 ms
wp-embed.min.js
4800 ms
pixel.png
3309 ms
logo.png
579 ms
js
4686 ms
tanxssp.js
381 ms
ex
1063 ms
acbeacon2.html
383 ms
spf
891 ms
TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png
160 ms
T13mMCFGVaXXbMsGbX.html
364 ms
TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png
22 ms
TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png
49 ms
TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png
49 ms
glyphicons-halflings-regular.woff
4187 ms
i.ashx
6846 ms
t.gif
4006 ms
tns.simba.taobao.com
11109 ms
magnifier-icon.png
858 ms
ping
15438 ms
app.gif
1146 ms
um.js
566 ms
img
2732 ms
um.json
18454 ms
getDeviceInfo
1266 ms
c1.ashx
1770 ms
tj.yule8.net
10334 ms
embed.js
1205 ms
stat.htm
287 ms
core.php
836 ms
css.css
1061 ms
flashobject.js
3125 ms
thumbnail.png
562 ms
share.js
5161 ms
1.jpg
2788 ms
gitlab.jpg
5656 ms
1.gif
5138 ms
1.gif
19524 ms
20160316102217_42977.jpg
2537 ms
mynameiscoder.jpg
2658 ms
linux-icojk.jpg
4797 ms
web-ico.jpg
4914 ms
30chengxuyuan.jpg
3365 ms
embed.default.css
82 ms
embed.compat.js
258 ms
z_stat.php
4799 ms
listRecentPosts.json
4061 ms
loop1.js
448 ms
97.jpg
20199 ms
k.png
869 ms
44.png
1003 ms
83.jpg
1333 ms
26.gif
20195 ms
98.jpg
3356 ms
logo.png
444 ms
TB2I2B4mXXXXXctXpXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
259 ms
T1eSpcFAhfXXcq1Onf-42-90.gif
236 ms
s_cap_1.gif
291 ms
tanxclick.js
41 ms
s_cap_5.gif
293 ms
TB2ffGalXXXXXarXpXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
236 ms
TB2Eh57ipXXXXc7XXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
236 ms
TB2fwDDkVXXXXacXXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
231 ms
TB2dtwakFXXXXXGXXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
234 ms
TB2lwOYkFXXXXbNXXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
229 ms
TB20Lr8lpXXXXXVXpXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
249 ms
TB2RWo7iFXXXXb2XXXXXXXXXXXX_!!110074383-0-saturn_solar.jpg_30x30.jpg
245 ms
TB2jGsilFXXXXcbXXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
249 ms
TB2scfRfpXXXXbXXpXXXXXXXXXX_!!13112147-0-saturn_solar.jpg_30x30.jpg
244 ms
TB1RSl2LVXXXXaGaXXXYXGcGpXX_M2.SS2_30x30.jpg
248 ms
TB2NlfzlpXXXXX6XXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
247 ms
TB2fJYXmXXXXXbKXpXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
256 ms
TB2BpmffpXXXXb.XXXXXXXXXXXX_!!57425032-0-saturn_solar.jpg_30x30.jpg
259 ms
TB2aVA8lFXXXXbnXXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
259 ms
TB2f9YJlpXXXXbmXpXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
266 ms
TB2na2xlVXXXXcvXXXXXXXXXXXX_!!0-saturn_solar.jpg_30x30.jpg
264 ms
TB2B.ZxlVXXXXabXXXXXXXXXXXX_!!2-saturn_solar.png_30x30.jpg
264 ms
TB2I2B4mXXXXXctXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
270 ms
TB2scfRfpXXXXbXXpXXXXXXXXXX_!!13112147-0-saturn_solar.jpg_110x90.jpg
286 ms
50
15849 ms
noavatar_default.png
109 ms
1
58 ms
88b36d6378e79fa5e98193e830.jpg
1517 ms
stat.htm
175 ms
core.php
713 ms
share_api.js
367 ms
share_view.js
741 ms
TB2ffGalXXXXXarXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
16 ms
s_blue_4.gif
57 ms
TB1RSl2LVXXXXaGaXXXYXGcGpXX_M2.SS2_110x90.jpg
26 ms
s_crown_1.gif
48 ms
tangram.js
3561 ms
api_base.js
802 ms
fx.htm
322 ms
view_base.js
882 ms
Wno.html
28 ms
z_stat.php
5816 ms
z_stat.php
1420 ms
TB2Eh57ipXXXXc7XXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
17 ms
T1_qLZXoNjXXb.cabb-23-18.png
304 ms
TB2NlfzlpXXXXX6XXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
29 ms
stat.htm
212 ms
core.php
334 ms
index
558 ms
logger.js
320 ms
g-117753.v-689226
907 ms
TB2fwDDkVXXXXacXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
14 ms
TB2fJYXmXXXXXbKXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
15 ms
share.css
536 ms
statIwt_www_new-min.js
459 ms
vasd_pv.js
26 ms
javascript
3696 ms
reportVv.js
55 ms
core-min.js
455 ms
irt
840 ms
TB2dtwakFXXXXXGXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
36 ms
s_blue_3.gif
76 ms
TB2BpmffpXXXXb.XXXXXXXXXXXX_!!57425032-0-saturn_solar.jpg_110x90.jpg
37 ms
stat.htm
276 ms
core.php
1168 ms
TB2lwOYkFXXXXbNXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
77 ms
s_blue_5.gif
91 ms
s_blue_2.gif
88 ms
TB2aVA8lFXXXXbnXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
67 ms
2715 ms
TB20Lr8lpXXXXXVXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
39 ms
TB2f9YJlpXXXXbmXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
35 ms
TB2RWo7iFXXXXb2XXXXXXXXXXXX_!!110074383-0-saturn_solar.jpg_110x90.jpg
19 ms
TB2na2xlVXXXXcvXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
26 ms
play
2914 ms
getDeviceInfo
2059 ms
TB2jGsilFXXXXcbXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
14 ms
TB2B.ZxlVXXXXabXXXXXXXXXXXX_!!2-saturn_solar.png_110x90.jpg
13 ms
blank.gif
89 ms
funet8.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
funet8.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
funet8.com SEO score
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funet8.com 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 Funet8.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.
funet8.com
Open Graph description is not detected on the main page of Funet 8. 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: