Access zli.me. 这里么 | 没错！就是黎叔这里

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

zli.me

1152 ms

zli.me

2447 ms

classic-themes.min.css

399 ms

dashicons.min.css

1387 ms

style.css

717 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 53% of them (36 requests) were addressed to the original Zli.me, 16% (11 requests) were made to Y.zli.me and 6% (4 requests) were made to Wyy.zli.me. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source W.zli.me.

Content Size

3.4 MB

After Optimization

3.1 MB

In fact, the total size of Zli.me main page is 3.4 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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 87.8 kB

Original 107.3 kB
After minification 101.5 kB
After compression 19.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 87.8 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 15.7 kB

Original 2.8 MB
After minification 2.8 MB

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. Zli images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 12.2 kB

Original 107.9 kB
After minification 107.4 kB
After compression 95.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 12.2 kB or 11% of the original size.

CSS Optimization

-66%

Potential reduce by 243.8 kB

Original 371.7 kB
After minification 366.6 kB
After compression 127.9 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. Zli.me needs all CSS files to be minified and compressed as it can save up to 243.8 kB or 66% of the original size.

Requests Now

After Optimization

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ZH
Language Claimed

ZH
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zli.me can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Zli.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

zli.me

Open Graph description is not detected on the main page of Zli. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

这里么 | 没错！就是黎叔这里

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

zli.me

zli.me

classic-themes.min.css

dashicons.min.css

style.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

zli.me

zli.me

classic-themes.min.css

dashicons.min.css

style.css

be.css

fonts.css

icons.css

font_2863485_yd7uwaxwe1n.css

jquery.min.js

jquery-migrate.min.js

jquery.lazyload.js

18637413.js

favorite-script.js

superfish.js

begin-script.js

ajax-content.js

qrious.js

owl.js

sticky.js

ias.js

infinite-post.js

begin-tab.js

fancybox.js

hm.js

ym.png

zl.png

s2.jpg

BeRsyj.jpg

64810f3adb0a298776365e01a0f96767

cert_45_1.png

police.gif

wmzz.png

kxwz.png

upyun.png

logo.png

gzh.jpg

captcha_images.php

captcha_images.php

shadow-top.png

iconfont.woff

font_2863485_yd7uwaxwe1n.woff

wbgb.jpg