100.1 sec in total
16.6 sec
82.7 sec
737 ms
Click here to check amazing Whyzzx content. Otherwise, check out these important facts you probably never knew about whyzzx.com
武汉叶子整形美容医院集成医疗美容和生活美容两大主题,下辖微创美容、整形美容、激光美容、生活美容、口腔美容五大中心,美丽热线:4000-844-448
Visit whyzzx.comWe analyzed Whyzzx.com page load time and found that the first response time was 16.6 sec and then it took 83.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 90 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
whyzzx.com performance score
name
value
score
weighting
Value1.7 s
93/100
10%
Value1.9 s
98/100
25%
Value20.0 s
0/100
10%
Value130 ms
96/100
30%
Value0.316
37/100
15%
Value4.1 s
87/100
10%
16643 ms
4607 ms
2402 ms
713 ms
17555 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 85% of them (108 requests) were addressed to the original Whyzzx.com, 3% (4 requests) were made to Hm.baidu.com and 2% (2 requests) were made to Static.mediav.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Whyzzx.com.
Page size can be reduced by 158.4 kB (74%)
212.6 kB
54.3 kB
In fact, the total size of Whyzzx.com main page is 212.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. HTML takes 139.6 kB which makes up the majority of the site volume.
Potential reduce by 116.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. 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 116.5 kB or 83% of the original size.
Potential reduce by 5.5 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, Whyzzx needs image optimization as it can save up to 5.5 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 25.0 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 25.0 kB or 71% of the original size.
Potential reduce by 11.3 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. Whyzzx.com needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 78% of the original size.
Number of requests can be reduced by 24 (69%)
35
11
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whyzzx. 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 as a result speed up the page load time.
www.whyzzx.com
16643 ms
index.css
4607 ms
style.css
2402 ms
uaredirect.js
713 ms
jquery-1.9.1.min.js
17555 ms
huandeng.js
3919 ms
qiehuan.js
2906 ms
jquery.flexslider-min.js
6280 ms
index.js
3398 ms
tt.js
6433 ms
logo.jpg
13075 ms
hzjg_tb.jpg
13802 ms
telephone.jpg
14273 ms
nav_ppzx.jpg
6204 ms
nav_zjtd.jpg
19644 ms
nav_zxmx.jpg
6733 ms
nav_yzxxf.jpg
19644 ms
nav_bbzx.jpg
19645 ms
nav_pfmr.jpg
19645 ms
nav_zsmx.jpg
15412 ms
nav_jczt.jpg
19645 ms
xnav_zhx.jpg
16851 ms
xnav_meifu.jpg
19646 ms
xnav_wuch.jpg
19646 ms
xnav_kouq.jpg
19647 ms
liuy.jpg
19648 ms
donglingshu.jpg
19651 ms
meiyanshu.jpg
19653 ms
yzxxf.jpg
19654 ms
ybhxf.jpg
19654 ms
meibishu.jpg
19655 ms
fengxiong.jpg
19655 ms
rongzhi.jpg
19657 ms
star.jpg
19657 ms
bahen.jpg
19654 ms
tuomao.jpg
19656 ms
shoulianzhen.jpg
19657 ms
ind_c1_right_tel.jpg
19656 ms
meiyanshu.jpg
19659 ms
anli1.jpg
19659 ms
wangyurong.jpg
19661 ms
ind_xm_btn01.jpg
19661 ms
ind_xm_btn02.jpg
19662 ms
yzxxf.jpg
19663 ms
hm.js
1469 ms
anli2.jpg
19641 ms
h.js
1705 ms
hm.gif
405 ms
21.gif
804 ms
hm.gif
377 ms
stat.php
1172 ms
swt.js
19698 ms
yefei.jpg
20440 ms
longbi.jpg
19913 ms
anli5.jpg
19572 ms
fengxiong.jpg
19844 ms
rongzhi.jpg
20371 ms
tisheng.jpg
20229 ms
vface.jpg
19789 ms
simi.jpg
19999 ms
ybhxf.jpg
19998 ms
anli6.jpg
19998 ms
zhangweihua.jpg
19999 ms
tuomao.jpg
20001 ms
meifu.jpg
20001 ms
chuzhou.jpg
20001 ms
quban.jpg
20002 ms
bahen.jpg
20020 ms
boniaosuan.jpg
20019 ms
anli4.jpg
20023 ms
botox.jpg
20023 ms
anli3.gif
20023 ms
yvoire.jpg
20023 ms
shoulianzhen.jpg
20027 ms
meibaizhen.jpg
20046 ms
chuzhouzhen.jpg
20046 ms
6bc7392e2eb1b0a6ae33027b12894157.jpg
20044 ms
50328d025458dc89bd4a882be3342893.jpg
20044 ms
fb219e8a05db36e5bceac67146938d1c.jpg
20045 ms
666aaa1840dbdcfda94ca2e797ce87f6.jpg
20044 ms
0f61079509ea6e82af2b070cdbcc1d5c.jpg
20042 ms
7d777e2d61cb781453d737e05acbfc61.jpg
20041 ms
aa831cfca8962758296f876045a2d9cb.jpg
20040 ms
2b9c682da0d62a322554f36e72969990.jpg
20039 ms
1e81a1e51946f079d4979652d27f31c8.jpg
20038 ms
08a57a5d97793a9dff9ae556cf73d29b.jpg
20036 ms
e91d1d10897a9672e6345182d6c43553.jpg
20032 ms
stat.htm
817 ms
core.php
1031 ms
57958f45875d585aa01ac5fb7baba203.jpg
19974 ms
9.gif
893 ms
mvl.js
1370 ms
app.gif
4210 ms
mba.js
221 ms
mv.js
311 ms
t
1434 ms
b
1353 ms
t
1365 ms
00003.jpg
19997 ms
foot_logo.jpg
19997 ms
ckmap.htm
593 ms
m
549 ms
dibutu.png
20040 ms
foot_weixin.jpg
19999 ms
nav_tb.jpg
15320 ms
diandian.gif
15067 ms
1.jpg
20000 ms
7.jpg
20025 ms
8.jpg
20025 ms
3.jpg
20024 ms
4.jpg
20024 ms
5.jpg
20023 ms
6.jpg
20021 ms
xnav_bj.jpg
20017 ms
ind_newatb.jpg
19997 ms
ind_xmnav_bj.jpg
19996 ms
ind_xmnav_tb.jpg
19992 ms
ind_xmnav_xz3.jpg
19991 ms
ind_xm_dbbj.jpg
19991 ms
ind_xm_xian.jpg
19991 ms
ind_xmnav_xz4.jpg
19984 ms
foot_tb_zxmr.jpg
19966 ms
foot_tb_zsmr.jpg
19965 ms
foot_tb_pfmr.jpg
19964 ms
foot_tb_kqmr.jpg
19964 ms
prev.png
19963 ms
next.png
19964 ms
whyzzx.com accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
whyzzx.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
whyzzx.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
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whyzzx.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 Whyzzx.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
whyzzx.com
Open Graph description is not detected on the main page of Whyzzx. 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: