18.1 sec in total
1 sec
16.8 sec
263 ms
Visit edzbe.com now to see the best up-to-date Edzbe content and also check out these interesting facts you probably never knew about edzbe.com
耳朵的主人,是一个小众音乐电台,以合集的模式提供歌特厄运、朋克流行、后摇、重金属等小众音乐供用户试听下载,每月更新合集两期,旨在分享我所喜欢及我所爱,庆幸我还有耳朵,还可以是耳朵的主人。
Visit edzbe.comWe analyzed Edzbe.com page load time and found that the first response time was 1 sec and then it took 17.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
edzbe.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value8.0 s
3/100
25%
Value7.8 s
23/100
10%
Value90 ms
98/100
30%
Value0
100/100
15%
Value6.3 s
61/100
10%
1025 ms
201 ms
398 ms
403 ms
411 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 69% of them (37 requests) were addressed to the original Edzbe.com, 6% (3 requests) were made to Static.duoshuo.com and 6% (3 requests) were made to 2.gravatar.com. The less responsive or slowest element that took the longest time to load (9.1 sec) relates to the external source Lib.sinaapp.com.
Page size can be reduced by 482.6 kB (19%)
2.6 MB
2.1 MB
In fact, the total size of Edzbe.com main page is 2.6 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.2 MB which makes up the majority of the site volume.
Potential reduce by 28.5 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 5.4 kB, which is 15% 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 28.5 kB or 79% of the original size.
Potential reduce by 234.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. Obviously, Edzbe needs image optimization as it can save up to 234.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 139.3 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 139.3 kB or 65% of the original size.
Potential reduce by 79.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. Edzbe.com needs all CSS files to be minified and compressed as it can save up to 79.9 kB or 82% of the original size.
Number of requests can be reduced by 24 (46%)
52
28
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edzbe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.edzbe.com
1025 ms
style.css
201 ms
wpfp.css
398 ms
wp-easyarchives.css
403 ms
jquery.fancybox-1.3.4.css
411 ms
css3_light_blue.css
432 ms
embed.js
576 ms
jquery.min.js
9054 ms
wpfp.js
440 ms
style.css
9042 ms
ccoooo.js
9039 ms
zzsc.js
9040 ms
jquery-1.8.3.min.js
9052 ms
embed.default.css
8461 ms
embed.compat.js
155 ms
bg.jpg
596 ms
56 ms
e0888ab1f7697c265025a860b0ba9aa6
136 ms
c7b16884b068cea25e55f7ee6707ec7f
312 ms
bd519862fc92759a8d5178727baaf90c
239 ms
232cdefbb4739ed3271f07e1fdffde3f
268 ms
logo.png
420 ms
a1.jpg
3711 ms
a2.jpg
4542 ms
a3.jpg
3105 ms
a4.jpg
3690 ms
a5.jpg
2728 ms
ico.png
795 ms
vol60.jpg
2788 ms
loading.gif
3181 ms
ico_16.png
2990 ms
ico_14.png
3194 ms
161740f5xlu557wl3u7nnn.jpg
4066 ms
2015.jpg
5222 ms
5424320978248.jpg_640x452.jpg
4559 ms
psbe.jpg
5722 ms
p1664159196.jpg
4696 ms
sina.png
4298 ms
qzone.png
4531 ms
ad-1.jpg
4839 ms
ad-2.jpg
5269 ms
hy_83x30.png
4773 ms
fa2cea514f1507877a33940d14ff6536
624 ms
a3177fab46cec1779e895cd1aa337fa3
162 ms
backgrounds.png
4956 ms
footerlogo.png
5158 ms
weixin.png
5259 ms
stat.php
1187 ms
counts.json
925 ms
stat.htm
166 ms
core.php
963 ms
9.gif
1559 ms
shares.png
3208 ms
app.gif
1349 ms
edzbe.com 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.
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.
edzbe.com 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
Browser errors were logged to the console
edzbe.com 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edzbe.com 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 Edzbe.com 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.
edzbe.com
Open Graph description is not detected on the main page of Edzbe. 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: