Tools & Wizards About Us
dyebhw.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dyebhw.com

德阳耳鼻喉专科医院[官方网]_德阳耳鼻喉医院_医保定点_德阳医院

Page Load Speed

66.8 sec in total

First Response

16 sec

Resources Loaded

50.6 sec

Page Rendered

213 ms

dyebhw.com screenshot

About Website

Visit dyebhw.com now to see the best up-to-date Dyebhw content and also check out these interesting facts you probably never knew about dyebhw.com

德阳博爱耳鼻喉专科医院是德阳医保定点医院，耳鼻喉诊疗专业医院，专业治疗鼻炎、鼻窦炎、鼻息肉、鼻出血、慢性咽喉炎、鼾症、中耳炎等。TEL:0838-2203298

Visit dyebhw.com

Key Findings

We analyzed Dyebhw.com page load time and found that the first response time was 16 sec and then it took 50.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 33 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

dyebhw.com performance score

0

Network Requests Diagram

dyebhw.com

16017 ms

zong_main.css

1065 ms

zong_global.css

4785 ms

zong_index2.css

1681 ms

jQuery1.9.1.js

20090 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 83% of them (49 requests) were addressed to the original Dyebhw.com, 7% (4 requests) were made to Dkt.zoosnet.net and 7% (4 requests) were made to Lxbjs.baidu.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Dyebhw.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.0 kB (84%)

Content Size

115.7 kB

After Optimization

18.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dyebhw.com main page is 115.7 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 72.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 63.2 kB

  • Original 72.5 kB
  • After minification 43.6 kB
  • After compression 9.2 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 28.8 kB, which is 40% 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 63.2 kB or 87% of the original size.

Image Optimization

-75%

Potential reduce by 5.7 kB

  • Original 7.6 kB
  • After minification 1.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, Dyebhw needs image optimization as it can save up to 5.7 kB or 75% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 11.0 kB

  • Original 14.8 kB
  • After minification 9.0 kB
  • After compression 3.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 11.0 kB or 74% of the original size.

CSS Optimization

-82%

Potential reduce by 17.0 kB

  • Original 20.8 kB
  • After minification 19.6 kB
  • After compression 3.8 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. Dyebhw.com needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (46%)

Requests Now

24

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dyebhw.com

dyebhw.com

16017 ms

zong_main.css

zong_main.css

1065 ms

zong_global.css

zong_global.css

4785 ms

zong_index2.css

zong_index2.css

1681 ms

jQuery1.9.1.js

jQuery1.9.1.js

20090 ms

zong_comment.min.js

zong_comment.min.js

5836 ms

zong_ma.js

zong_ma.js

2861 ms

appcall-uncompressed.js

appcall-uncompressed.js

493 ms

LsJS.aspx

LsJS.aspx

1945 ms

swt28.js

swt28.js

983 ms

swt_1.js

swt_1.js

1658 ms

swt.js

swt.js

997 ms

top_bg.png

top_bg.png

9705 ms

logo.png

logo.png

4574 ms

88afbb672984239013b0d73b92ec87f2.jpg

88afbb672984239013b0d73b92ec87f2.jpg

16067 ms

83cf5d05d95ae1bd4bddeb4c01128c54.jpg

83cf5d05d95ae1bd4bddeb4c01128c54.jpg

8598 ms

66808256187011d412eb971d294cf6e9.jpg

66808256187011d412eb971d294cf6e9.jpg

19996 ms

73bba06a8438aaca4b61c0c1eec2d436.jpg

73bba06a8438aaca4b61c0c1eec2d436.jpg

19997 ms

idx_doc_5.jpg

idx_doc_5.jpg

19998 ms

idx_doc_2.jpg

idx_doc_2.jpg

19998 ms

idx_doc_3.jpg

idx_doc_3.jpg

19999 ms

idx_doc_9.jpg

idx_doc_9.jpg

19999 ms

idx_doc_4.jpg

idx_doc_4.jpg

19998 ms

idx_doc_7.jpg

idx_doc_7.jpg

19999 ms

idx_doc_btn1.png

idx_doc_btn1.png

19999 ms

idx_doc_btn2.png

idx_doc_btn2.png

19998 ms

idx_doc_big2.jpg

idx_doc_big2.jpg

19998 ms

idx_doc_big3.jpg

idx_doc_big3.jpg

19998 ms

idx_doc_big4.jpg

idx_doc_big4.jpg

19998 ms

idx_doc_big5.jpg

idx_doc_big5.jpg

19998 ms

idx_doc_big7.jpg

idx_doc_big7.jpg

19997 ms

idx_doc_big9.jpg

idx_doc_big9.jpg

19998 ms

botton_ico1.png

botton_ico1.png

19998 ms

botton_pic.png

botton_pic.png

19998 ms

icon_home.png

icon_home.png

19965 ms

sprite.png

sprite.png

19965 ms

png_idx_small.png

png_idx_small.png

19965 ms

png_idx_tit.png

png_idx_tit.png

19965 ms

idx_m4_btn.png

idx_m4_btn.png

19964 ms

idx_m1_list.png

idx_m1_list.png

19965 ms

png_idx_m3.png

png_idx_m3.png

19965 ms

idx_m3_tel.png

idx_m3_tel.png

19966 ms

idx_m3_telico.png

idx_m3_telico.png

19965 ms

idx_m5_ico.png

idx_m5_ico.png

19965 ms

idx_m7.png

idx_m7.png

19966 ms

ft_bg.png

ft_bg.png

19966 ms

ft_logo.png

ft_logo.png

19965 ms

button_bg.png

button_bg.png

19913 ms

JS3.aspx

JS3.aspx

448 ms

JS_Float.aspx

JS_Float.aspx

256 ms

hm.js

hm.js

4424 ms

newsid0.aspx

newsid0.aspx

240 ms

botton_tel_tit.png

botton_tel_tit.png

19811 ms

hm.gif

hm.gif

313 ms

lxb.js

lxb.js

1682 ms

log.gif

log.gif

1200 ms

_l.js

_l.js

960 ms

log.gif

log.gif

1469 ms

botton_tel_btn.png

botton_tel_btn.png

12875 ms

SEO Factors

dyebhw.com SEO score

0

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

Social Sharing Optimization

dyebhw.com

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