5.3 sec in total
746 ms
4 sec
524 ms
Welcome to zglzy.cc homepage info - get ready to check Zglzy best content right away, or after learning these important things about zglzy.cc
绿之源
Visit zglzy.ccWe analyzed Zglzy.cc page load time and found that the first response time was 746 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
zglzy.cc performance score
name
value
score
weighting
Value1.4 s
98/100
10%
Value4.4 s
40/100
25%
Value11.9 s
4/100
10%
Value10 ms
100/100
30%
Value1.248
1/100
15%
Value1.4 s
100/100
10%
746 ms
218 ms
431 ms
433 ms
650 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that all of those requests were addressed to Zglzy.cc and no external sources were called. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Zglzy.cc.
Page size can be reduced by 48.9 kB (1%)
5.3 MB
5.3 MB
In fact, the total size of Zglzy.cc main page is 5.3 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. 65% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 12.1 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. This page needs HTML code to be minified as it can gain 2.7 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 12.1 kB or 78% of the original size.
Potential reduce by 36.9 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. Zglzy images are well optimized though.
We found no issues to fix!
41
41
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zglzy. According to our analytics all requests are already optimized.
zglzy.cc
746 ms
scroll.css
218 ms
style.css
431 ms
phone.css
433 ms
jquery-1.12.4.min.js
650 ms
jquery.flexslider-min.js
438 ms
toscroll.js
435 ms
headbj.png
218 ms
ff6783540763843fbae61736255ee562.png
217 ms
menu.png
221 ms
12f6dc67e3b260ffce1679f4b3d77dbc.jpg
1719 ms
318e4e08531f25a6602ed38e32553afd.jpg
1079 ms
1545978463102415.png
1088 ms
1545982301564706.png
645 ms
1545202961135834.png
433 ms
1545203001296962.png
2381 ms
1545203018117291.png
649 ms
1545203097201044.png
861 ms
1545203121121310.png
865 ms
1545203147819798.png
1076 ms
1545203232248078.png
1296 ms
1545203240363274.png
1935 ms
cf55a4e793d7b12c0a37183b3b348e0a.jpg
1295 ms
dd99372d4d949d13484b0653c9ad790c.jpg
1522 ms
37fae352704056da0ac3a194c131bdc1.jpg
1513 ms
5aa8339c4353faed8300c13a6cb55331.jpg
1513 ms
d97b77bed2dc54ce796f56dc522e2b13.jpg
1729 ms
240d9dab770512059d2c010cf608ea3d.jpg
2590 ms
69a6c7d00166438bd57ef47acb7165fa.jpg
1739 ms
d9fed76c604106edb1294aba58bf4c74.jpg
1933 ms
foot.png
1945 ms
foot1.png
1958 ms
wx.png
2148 ms
foot2.png
2148 ms
foot3.png
2160 ms
631ddd99ac24d92a78bef05882d761b0.jpg
2163 ms
386a358519c06989902f2ddb81655866.jpg
2352 ms
8d844473ce9e9da1fe1be7bbc3afa192.jpg
2352 ms
top.png
2364 ms
foot4.png
2381 ms
footbj.png
2566 ms
bannerli.png
2537 ms
bannerli1.png
2549 ms
zglzy.cc accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
zglzy.cc 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
zglzy.cc 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
Tap targets are not sized appropriately
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zglzy.cc 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 Zglzy.cc 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.
zglzy.cc
Open Graph description is not detected on the main page of Zglzy. 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: