Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

lzw.me

志文工作室 - 每天知道多一点

Page Load Speed

20.6 sec in total

First Response

1.2 sec

Resources Loaded

19 sec

Page Rendered

343 ms

About Website

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.me

Key Findings

We 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.

Performance Metrics

lzw.me performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value44.5 s

0/100

25%

SI (Speed Index)

Value20.6 s

0/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.199

62/100

15%

TTI (Time to Interactive)

Value37.7 s

0/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 162.6 kB (16%)

Content Size

1.0 MB

After Optimization

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.

HTML Optimization

-81%

Potential reduce by 63.4 kB

  • Original 77.8 kB
  • After minification 73.4 kB
  • After compression 14.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.

Image Optimization

-5%

Potential reduce by 27.7 kB

  • Original 540.8 kB
  • After minification 513.1 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.

JavaScript Optimization

-7%

Potential reduce by 23.9 kB

  • Original 340.9 kB
  • After minification 337.0 kB
  • After compression 316.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.

CSS Optimization

-59%

Potential reduce by 47.6 kB

  • Original 81.3 kB
  • After minification 79.5 kB
  • After compression 33.7 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.

Requests Breakdown

Number of requests can be reduced by 57 (75%)

Requests Now

76

After Optimization

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.

Accessibility Review

lzw.me accessibility score

67

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

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

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lzw.me best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lzw.me SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: