29.7 sec in total
1.1 sec
28.2 sec
441 ms
Click here to check amazing Windme content. Otherwise, check out these important facts you probably never knew about windme.org
这是杨年浩的个人博客,纯技术讨论,偶尔吐槽
Visit windme.orgWe analyzed Windme.org page load time and found that the first response time was 1.1 sec and then it took 28.7 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
windme.org performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value10.0 s
0/100
25%
Value11.8 s
4/100
10%
Value90 ms
99/100
30%
Value0.273
45/100
15%
Value9.4 s
31/100
10%
1060 ms
1667 ms
1257 ms
3116 ms
1390 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 36% of them (19 requests) were addressed to the original Windme.org, 28% (15 requests) were made to Mat1.gtimg.com and 15% (8 requests) were made to App.qlogo.cn. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source App.qlogo.cn.
Page size can be reduced by 178.8 kB (54%)
331.2 kB
152.4 kB
In fact, the total size of Windme.org main page is 331.2 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. 20% of websites need less resources to load. Javascripts take 180.5 kB which makes up the majority of the site volume.
Potential reduce by 38.2 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 38.2 kB or 77% of the original size.
Potential reduce by 6.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. Windme images are well optimized though.
Potential reduce by 117.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 117.8 kB or 65% of the original size.
Potential reduce by 16.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. Windme.org needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 76% of the original size.
Number of requests can be reduced by 28 (60%)
47
19
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Windme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
windme.org
1060 ms
main.css
1667 ms
common_tpl.js
1257 ms
jquery-1.7.1.js
3116 ms
swfobject.js
1390 ms
pagenavi-css.css
1393 ms
qfcode.js
611 ms
index.php
1366 ms
stats
1177 ms
3763610.js
1054 ms
step_ol_bg.png
769 ms
wrapper.gif
529 ms
logo.gif
2055 ms
topnav.jpg
884 ms
author.gif
1705 ms
date.gif
431 ms
comment.gif
458 ms
05641426553142.png
8193 ms
feedme.gif
2792 ms
rss.png
1026 ms
windme.org
534 ms
show.php
908 ms
li.gif
1228 ms
icon_0.gif
3838 ms
go.asp
20084 ms
bg_cal_today.gif
903 ms
index.php
1960 ms
show.css
503 ms
0.css
505 ms
jquery.js
747 ms
50
15931 ms
160
1988 ms
160
2043 ms
160
2045 ms
50
20275 ms
50
15921 ms
50
15918 ms
50
15992 ms
50
16369 ms
50
16369 ms
50
16369 ms
bgst.gif
275 ms
tit.gif
273 ms
bgs0.png
274 ms
vip_icon_orange.gif
537 ms
bgs.gif
536 ms
listen.png
537 ms
tips.gif
534 ms
bgs1.png
535 ms
sbg.png
541 ms
space.gif
794 ms
bgs2.png
792 ms
head_50.jpg
792 ms
windme.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not have valid values
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
windme.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
windme.org SEO score
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 Windme.org 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 Windme.org 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.
windme.org
Open Graph description is not detected on the main page of Windme. 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: