48.5 sec in total
7.9 sec
40.1 sec
459 ms
Visit wzl.im now to see the best up-to-date WZL content and also check out these interesting facts you probably never knew about wzl.im
WZL的自留地,记录那年的故事,讲述生活的点点滴滴...
Visit wzl.imWe analyzed Wzl.im page load time and found that the first response time was 7.9 sec and then it took 40.6 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.
wzl.im performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value6.2 s
11/100
25%
Value6.0 s
47/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value2.4 s
98/100
10%
7898 ms
2177 ms
3879 ms
10568 ms
286 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 51% of them (35 requests) were addressed to the original Wzl.im, 9% (6 requests) were made to Cpro.baidustatic.com and 4% (3 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (19.7 sec) belongs to the original domain Wzl.im.
Page size can be reduced by 388.5 kB (49%)
798.0 kB
409.6 kB
In fact, the total size of Wzl.im main page is 798.0 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. 30% of websites need less resources to load. Javascripts take 374.7 kB which makes up the majority of the site volume.
Potential reduce by 35.6 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 35.6 kB or 75% of the original size.
Potential reduce by 27.6 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. WZL images are well optimized though.
Potential reduce by 239.6 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 239.6 kB or 64% of the original size.
Potential reduce by 85.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. Wzl.im needs all CSS files to be minified and compressed as it can save up to 85.6 kB or 81% of the original size.
Number of requests can be reduced by 26 (39%)
66
40
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WZL. 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 4 to 1 for CSS and as a result speed up the page load time.
wzl.im
7898 ms
reset.css
2177 ms
style.css
3879 ms
jquery.js
10568 ms
embed.js
286 ms
highslide.css
4064 ms
highslide-with-html.packed.js
4592 ms
c.js
10348 ms
bg.png
3110 ms
stat.php
1525 ms
stats
7212 ms
wp-embed.min.js
369 ms
Newer.js
6137 ms
lazyload.js
7655 ms
wp-emoji-release.min.js
6265 ms
100 ms
headbg.png
5401 ms
icon_search.png
757 ms
info.png
6481 ms
thumbg.png
12079 ms
10.jpg
2160 ms
sep.png
7979 ms
5.jpg
7477 ms
timthumb.php
9603 ms
2.jpg
11627 ms
timthumb.php
19657 ms
3.jpg
9693 ms
timthumb.php
16111 ms
pagenavbgcun.jpg
11206 ms
pagenavbg.jpg
10052 ms
li.png
10416 ms
73f1441dd101f9faa7b6853ea9ed9ee8
339 ms
embed.default.css
89 ms
embed.compat.js
220 ms
counts.json
2862 ms
zczm
1028 ms
tags.png
9735 ms
footerbg.png
10514 ms
ctop.png
10113 ms
cdown.png
10179 ms
h.js
1392 ms
zczm
3235 ms
stat.htm
594 ms
core.php
1985 ms
hm.gif
394 ms
9.gif
4152 ms
loading.gif
7723 ms
controls.png
7827 ms
adx.php
790 ms
u=3718621298,3658177392&fm=76
3636 ms
u=664732858,3890334781&fm=76
4239 ms
u=1536918444,2064392575&fm=76
2151 ms
bg.png
513 ms
reduce_bd-logo1_oper.png
513 ms
u=877754082,4004118855&fm=76
14339 ms
app.gif
6128 ms
closefeedback.min.js
469 ms
rounded-white.png
766 ms
o.htm
1501 ms
zoomout.cur
7068 ms
loader.white.gif
783 ms
reduce_promotion_oper.png
506 ms
bd_logo.png
520 ms
bg_rb.png
523 ms
hm.gif
715 ms
wh.js
759 ms
ac.js
511 ms
fp.htm
687 ms
fp.htm
384 ms
wzl.im accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
wzl.im 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
Browser errors were logged to the console
Page has valid source maps
wzl.im 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 uses legible font sizes
EN
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wzl.im can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Wzl.im 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.
wzl.im
Open Graph description is not detected on the main page of WZL. 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: