20.6 sec in total
1.2 sec
19 sec
343 ms
Welcome to lzw.me homepage info - get ready to check Lzw best content for China right away, or after learning these important things about lzw.me
一个关 于web 前端、网站建设和计算机基础技术学习的个人网站
Visit lzw.meWe analyzed Lzw.me page load time and found that the first response time was 1.2 sec and then it took 19.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
lzw.me performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value44.5 s
0/100
25%
Value20.6 s
0/100
10%
Value520 ms
56/100
30%
Value0.199
62/100
15%
Value37.7 s
0/100
10%
1231 ms
459 ms
462 ms
531 ms
537 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 84% of them (70 requests) were addressed to the original Lzw.me, 7% (6 requests) were made to Lib.baomitu.com and 2% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (17 sec) belongs to the original domain Lzw.me.
Page size can be reduced by 162.6 kB (16%)
1.0 MB
878.1 kB
In fact, the total size of Lzw.me main page is 1.0 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. 60% of websites need less resources to load. Images take 540.8 kB which makes up the majority of the site volume.
Potential reduce by 63.4 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 63.4 kB or 81% of the original size.
Potential reduce by 27.7 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. Lzw images are well optimized though.
Potential reduce by 23.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 47.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. Lzw.me needs all CSS files to be minified and compressed as it can save up to 47.6 kB or 59% of the original size.
Number of requests can be reduced by 57 (75%)
76
19
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lzw. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
lzw.me
1231 ms
style.min.css
459 ms
animate.min.css
462 ms
font-awesome.min.css
531 ms
bootstrap.min.css
537 ms
superfish.min.css
465 ms
style.css
470 ms
kratos.diy.css
468 ms
shCore.js
476 ms
shBrushAS3.js
680 ms
shBrushArduino.js
681 ms
shBrushBash.js
685 ms
shBrushColdFusion.js
696 ms
shBrushClojure.js
698 ms
shBrushCpp.js
715 ms
shBrushCSharp.js
907 ms
shBrushCss.js
910 ms
shBrushDelphi.js
915 ms
shBrushDiff.js
929 ms
shBrushErlang.js
929 ms
shBrushFSharp.js
953 ms
shBrushGo.js
1136 ms
shBrushGroovy.js
1142 ms
shBrushHaskell.js
1143 ms
shBrushJava.js
1164 ms
shBrushJavaFX.js
1163 ms
shBrushJScript.js
1192 ms
shBrushLatex.js
1363 ms
shBrushMatlabKey.js
1369 ms
shBrushObjC.js
1375 ms
shBrushPerl.js
1397 ms
shBrushPhp.js
1396 ms
shBrushPlain.js
1430 ms
shBrushPowerShell.js
1592 ms
shBrushPython.js
1597 ms
shBrushR.js
1605 ms
shBrushRuby.js
1628 ms
shBrushScala.js
1630 ms
jquery.min.js
538 ms
bootstrap.min.js
539 ms
shBrushSql.js
1455 ms
shBrushSwift.js
1373 ms
shBrushVb.js
1374 ms
shBrushXml.js
1380 ms
jquery.lightbox-0.5.css
1405 ms
shBrushYaml.js
1400 ms
jquery.easing.min.js
1533 ms
jquery.qrcode.min.js
1382 ms
modernizr.min.js
1409 ms
jquery.waypoints.min.js
1405 ms
jquery.stellar.min.js
1424 ms
hoverIntent.min.js
1421 ms
superfish.js
1524 ms
kratos.js
1695 ms
kratos.diy.js
2075 ms
scoop-help.png
13254 ms
60s-preview.jpg
5073 ms
m3u8-dl-tool.png
10763 ms
chatgpt-1.png
16997 ms
websocket-mock.png
4052 ms
thumb.php
2073 ms
thumb.php
1208 ms
thumb.php
3802 ms
thumb.php
1372 ms
thumb.php
2401 ms
t01177801b8373c4870-300x188.jpg
725 ms
xcx_tool.jpg
5912 ms
lzwme-qrcode_430.jpg
4718 ms
apple-touch-icon.png
1080 ms
hm.js
1050 ms
adsbygoogle.js
255 ms
default.cur
824 ms
hand.cur
2015 ms
pointer.cur
1075 ms
glyphicons-halflings-regular.woff
27 ms
fontawesome-webfont.woff
6 ms
Din.otf
2152 ms
shCore.css
1198 ms
shThemeMidnight.css
1428 ms
show_ads_impl.js
237 ms
zrt_lookup.html
115 ms
ads
221 ms
hm.gif
306 ms
lzw.me 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
lzw.me 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
lzw.me 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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lzw.me 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 Lzw.me 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.
lzw.me
Open Graph description is not detected on the main page of Lzw. 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: