Tools & Wizards About Us
dns.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

dns.com

帝恩思-DNS.COM：全球知名数字安全综合服务商-免费DNS解析-云解析-高防CDN-DNS劫持-SSL证书-网站劫持检测-宕机监控-云服务器ECS

Page Load Speed

7.8 sec in total

First Response

656 ms

Resources Loaded

6.4 sec

Page Rendered

718 ms

dns.com screenshot

About Website

Welcome to dns.com homepage info - get ready to check DNS best content for China right away, or after learning these important things about dns.com

帝恩思是 2012 年成立的新三板挂牌企业（证券代码 837018），致力成为全球知名数字安全综合服务商。帝恩思通过创新技术打造数字资产安全产品、应用安全监测和域名安全服务，保护在线业务免受网络威胁。优势包括数字资产安全服务、应用安全监测服务、域名安全服务，公司服务团队为众多企业提供数字安全解决方案。

Visit dns.com

Key Findings

We analyzed Dns.com page load time and found that the first response time was 656 ms and then it took 7.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

dns.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.468

19/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

dns.com

656 ms

www.dns.com

1336 ms

base.css

432 ms

common.css

872 ms

iconfont.css

655 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 94% of them (65 requests) were addressed to the original Dns.com, 3% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Dns.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 384.8 kB (16%)

Content Size

2.4 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dns.com main page is 2.4 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. 35% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 258.1 kB

  • Original 371.9 kB
  • After minification 348.0 kB
  • After compression 113.8 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 258.1 kB or 69% of the original size.

Image Optimization

-4%

Potential reduce by 69.1 kB

  • Original 1.7 MB
  • After minification 1.7 MB

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. DNS images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 38.7 kB

  • Original 241.0 kB
  • After minification 238.8 kB
  • After compression 202.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 38.7 kB or 16% of the original size.

CSS Optimization

-55%

Potential reduce by 18.9 kB

  • Original 34.4 kB
  • After minification 21.3 kB
  • After compression 15.5 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. Dns.com needs all CSS files to be minified and compressed as it can save up to 18.9 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (33%)

Requests Now

66

After Optimization

44

  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

dns.com

dns.com

656 ms

www.dns.com

www.dns.com

1336 ms

base.css

base.css

432 ms

common.css

common.css

872 ms

iconfont.css

iconfont.css

655 ms

animate.min.css

animate.min.css

863 ms

index_new.css

index_new.css

867 ms

swiper.min.css

swiper.min.css

883 ms

uaredirect.js

uaredirect.js

877 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

1031 ms

common.js

common.js

885 ms

popup.js

popup.js

884 ms

moment.min.js

moment.min.js

911 ms

Validform_v5.3.2_min.js

Validform_v5.3.2_min.js

899 ms

cookie.js

cookie.js

907 ms

iconfont.js

iconfont.js

1775 ms

jquery.SuperSlide.2.1.3.js

jquery.SuperSlide.2.1.3.js

1148 ms

wow.min.js

wow.min.js

1123 ms

jquery.particleground.js

jquery.particleground.js

1139 ms

index.js

index.js

1141 ms

swiper.min.js

swiper.min.js

1302 ms

js

js

47 ms

popup.css

popup.css

1346 ms

clipboard.min.js

clipboard.min.js

1370 ms

logo_172x32.png

logo_172x32.png

666 ms

head03.png

head03.png

2167 ms

svip01.png

svip01.png

833 ms

50668c44d2fafde7b3117a86226ea649.jpg

50668c44d2fafde7b3117a86226ea649.jpg

1323 ms

48d9c8da469813d3d98f8c51162dd119.jpg

48d9c8da469813d3d98f8c51162dd119.jpg

1566 ms

4836510d8a61acd09776d70c0010b38d.jpg

4836510d8a61acd09776d70c0010b38d.jpg

1790 ms

954cbf39cbe83e7e66687107c32ce45c.jpg

954cbf39cbe83e7e66687107c32ce45c.jpg

1582 ms

4cb4fd885d097a84c1e6cf20c7ecfb61.jpg

4cb4fd885d097a84c1e6cf20c7ecfb61.jpg

1560 ms

3d750fe1969f416966ebf8fb3ebe141e.jpg

3d750fe1969f416966ebf8fb3ebe141e.jpg

1812 ms

new20.png

new20.png

1787 ms

new12.png

new12.png

1793 ms

new13.png

new13.png

1815 ms

new14.png

new14.png

2014 ms

new15.png

new15.png

2019 ms

new21.png

new21.png

2020 ms

new16.png

new16.png

2035 ms

new08.png

new08.png

2045 ms

new19.png

new19.png

2237 ms

new07.png

new07.png

2250 ms

new18.png

new18.png

2254 ms

new06.png

new06.png

2259 ms

new17.png

new17.png

2203 ms

iconfont.woff

iconfont.woff

2263 ms

new05.png

new05.png

2287 ms

new10.jpg

new10.jpg

2383 ms

new11.png

new11.png

2377 ms

case1.png

case1.png

2372 ms

case2.png

case2.png

2236 ms

case3.png

case3.png

2249 ms

case4.png

case4.png

2259 ms

case5.png

case5.png

2279 ms

case6.png

case6.png

2282 ms

case7.png

case7.png

2132 ms

case8.png

case8.png

2101 ms

new09.jpg

new09.jpg

2264 ms

sprite.png

sprite.png

2290 ms

gzh01.png

gzh01.png

2133 ms

hm.js

hm.js

1138 ms

beian.png

beian.png

1834 ms

banner_c.png

banner_c.png

1637 ms

wechat_dns.jpg

wechat_dns.jpg

1418 ms

topscoll.png

topscoll.png

1589 ms

hm.gif

hm.gif

348 ms

push.js

push.js

1165 ms

logo_172x32_1.png

logo_172x32_1.png

601 ms

Accessibility Review

dns.com accessibility score

72

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dns.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

dns.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dns.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that 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

dns.com

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