Tools & Wizards About Us
intodns.com screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

intodns.com

intoDNS: checks DNS and mail servers health

Page Load Speed

1.6 sec in total

First Response

270 ms

Resources Loaded

1.3 sec

Page Rendered

73 ms

intodns.com screenshot

About Website

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

intoDNS checks the health and configuration of DNS and mail servers.

Visit intodns.com

Key Findings

We analyzed Intodns.com page load time and found that the first response time was 270 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

intodns.com performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

intodns.com

270 ms

intodns.com

498 ms

style.css

122 ms

jquery.js

363 ms

hint.js

361 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 80% of them (8 requests) were addressed to the original Intodns.com, 10% (1 request) were made to Google-analytics.com and 10% (1 request) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (498 ms) belongs to the original domain Intodns.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.0 kB (46%)

Content Size

15.4 kB

After Optimization

8.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Intodns.com main page is 15.4 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 5% of websites need less resources to load. Javascripts take 6.8 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 1.4 kB

  • Original 2.4 kB
  • After minification 2.3 kB
  • After compression 975 B

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 1.4 kB or 59% of the original size.

JavaScript Optimization

-14%

Potential reduce by 971 B

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.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 971 B or 14% of the original size.

CSS Optimization

-75%

Potential reduce by 4.7 kB

  • Original 6.2 kB
  • After minification 4.5 kB
  • After compression 1.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. Intodns.com needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (38%)

Requests Now

8

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intodns.com

intodns.com

270 ms

intodns.com

intodns.com

498 ms

style.css

style.css

122 ms

jquery.js

jquery.js

363 ms

hint.js

hint.js

361 ms

onload.js

onload.js

371 ms

urchin.js

urchin.js

19 ms

intodns_logo.gif

intodns_logo.gif

123 ms

report.gif

report.gif

122 ms

__utm.gif

__utm.gif

17 ms

Accessibility Review

intodns.com accessibility score

87

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

SEO Factors

intodns.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intodns.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Intodns.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

intodns.com

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