Tools & Wizards About Us
broken.dns.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

broken.dns.com

DNS.COM-免费DNS_智能DNS_高防DNS_DNS解析，免费智能DNS解析服务商，国内最大的高防DNS解析服务商

Page Load Speed

12.2 sec in total

First Response

3 sec

Resources Loaded

9 sec

Page Rendered

195 ms

broken.dns.com screenshot

About Website

Visit broken.dns.com now to see the best up-to-date Broken DNS content for China and also check out these interesting facts you probably never knew about broken.dns.com

DNS.COM是国内最大的高防DNS解析服务商，采用自主研发的DNS解析系统，无论在解析技术及抗攻击能力均处于国内领先水平。并提供高质量的电信、联通、教育网、双线及三线智能DNS免费解析，以及支持搜索引擎优化解析。网站、域名健康状态检查监控功能，提供准确实时的宕机检测告警及宕机自动切换。

Visit broken.dns.com

Key Findings

We analyzed Broken.dns.com page load time and found that the first response time was 3 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

broken.dns.com performance score

0

Network Requests Diagram

broken.dns.com

3003 ms

www.dns.com

2304 ms

index.css

247 ms

core.css

487 ms

jquery.min.js

1201 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Broken.dns.com, 96% (50 requests) were made to Dns.com and 2% (1 request) were made to Mp.weixin.qq.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Broken.dns.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.5 kB (14%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Broken.dns.com main page is 1.2 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. 20% of websites need less resources to load. Images take 966.4 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.0 kB

  • Original 14.5 kB
  • After minification 13.9 kB
  • After compression 4.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 10.0 kB or 69% of the original size.

Image Optimization

-2%

Potential reduce by 17.7 kB

  • Original 966.4 kB
  • After minification 948.7 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. Broken DNS images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 82.9 kB

  • Original 122.0 kB
  • After minification 115.1 kB
  • After compression 39.2 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 82.9 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 47.9 kB

  • Original 59.8 kB
  • After minification 55.5 kB
  • After compression 11.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. Broken.dns.com needs all CSS files to be minified and compressed as it can save up to 47.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (10%)

Requests Now

50

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

broken.dns.com

broken.dns.com

3003 ms

www.dns.com

www.dns.com

2304 ms

index.css

index.css

247 ms

core.css

core.css

487 ms

jquery.min.js

jquery.min.js

1201 ms

jquery.easing.compatibility.js

jquery.easing.compatibility.js

726 ms

banner.js

banner.js

725 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

728 ms

home.js

home.js

729 ms

animateBackground-plugin.js

animateBackground-plugin.js

726 ms

showqrcode

showqrcode

1385 ms

dns_logo_2015.png

dns_logo_2015.png

476 ms

goTop.png

goTop.png

477 ms

mouse.gif

mouse.gif

478 ms

index_word1.png

index_word1.png

479 ms

index_word2.png

index_word2.png

484 ms

index_word3.png

index_word3.png

742 ms

index_word4.png

index_word4.png

741 ms

index_word5.png

index_word5.png

742 ms

index_word6.png

index_word6.png

742 ms

index_word7.png

index_word7.png

743 ms

dns_footer_logo_2015.png

dns_footer_logo_2015.png

950 ms

20150717125805_54253.jpg

20150717125805_54253.jpg

1198 ms

20150608064040_13656.jpg

20150608064040_13656.jpg

1220 ms

pagination.png

pagination.png

242 ms

trait_icon1.png

trait_icon1.png

246 ms

trait_icon2.png

trait_icon2.png

245 ms

trait_icon3.png

trait_icon3.png

458 ms

trait_icon4.png

trait_icon4.png

482 ms

actionBox01.jpg

actionBox01.jpg

1951 ms

actionBox01_gray.jpg

actionBox01_gray.jpg

1439 ms

actionBox02.jpg

actionBox02.jpg

1652 ms

actionBox02_gray.jpg

actionBox02_gray.jpg

1445 ms

function_icon1.png

function_icon1.png

1436 ms

function_icon2.png

function_icon2.png

1460 ms

function_icon3.png

function_icon3.png

1675 ms

function_icon4.png

function_icon4.png

1677 ms

function_icon5.png

function_icon5.png

1684 ms

function_icon6.png

function_icon6.png

1702 ms

function_icon7.png

function_icon7.png

1890 ms

function_icon8.png

function_icon8.png

1915 ms

function_icon9.png

function_icon9.png

1917 ms

function_icon10.png

function_icon10.png

1923 ms

actionBox04.jpg

actionBox04.jpg

2429 ms

partners_thunderbolt.png

partners_thunderbolt.png

2129 ms

partners_anquanbao.png

partners_anquanbao.png

2154 ms

partners_cndns.png

partners_cndns.png

2153 ms

partners_22.png

partners_22.png

2161 ms

partners_wy.png

partners_wy.png

2186 ms

partners_qingsong.png

partners_qingsong.png

2367 ms

partners_maff.png

partners_maff.png

2392 ms

partners_ming.png

partners_ming.png

2393 ms

SEO Factors

broken.dns.com SEO score

0

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 Broken.dns.com 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 Broken.dns.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

broken.dns.com

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