dig.do Website Information
Daily Unique Visits: 1,104
Daily Page Views: 2,208
Income Per Day: $7
Estimated Value: $1,680
dig.do is registered under .DO top-level domain. Please check other sites in .DO zone.
No name server records were found.
and is probably hosted by AS-COLOCROSSING - ColoCrossing, US. See the full list of other websites hosted by AS-COLOCROSSING - ColoCrossing, US.
The highest website dig.do position in Alexa rank database was 25772 and the lowest rank position was 990863. Current position of dig.do in Alexa rank database is 649471.
Desktop speed score of dig.do (92/100) is better than the results of 90.97% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of dig.do (88/100) is better than the results of 28.85% of other sites and means that the page is mobile-friendly.
Mobile speed score of dig.do (85/100) is better than the results of 90.58% of other sites and shows that the landing page performance on mobile devices is excellent.
Advertisement
dig.do Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
dig.do whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
dig.do server information
Servers Location
dig.do desktop page speed rank
Last tested: 2017-04-26
dig.do Desktop Speed Test Quick Summary
priority - 5Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://dig.do/images_/site-audience-growth.png (expiration not specified)
http://dig.do/images_/top-sites.png (expiration not specified)
http://dig.do/images_/website-analysis.png (expiration not specified)
http://dig.do/logos_/dig.do.png (expiration not specified)
http://connect.facebook.net/pt_BR/all.js (20 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 2Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 2.8KiB (22% reduction).
dig.do Desktop Resource Breakdown
| Total Resources | 34 |
| Number of Hosts | 13 |
| Static Resources | 21 |
| JavaScript Resources | 15 |
| CSS Resources | 1 |
dig.do mobile page speed rank
Last tested: 2017-04-26
dig.do Mobile Speed Test Quick Summary
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
priority - 8Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://dig.do/images_/site-audience-growth.png (expiration not specified)
http://dig.do/images_/top-sites.png (expiration not specified)
http://dig.do/images_/website-analysis.png (expiration not specified)
http://dig.do/logos_/dig.do.png (expiration not specified)
http://connect.facebook.net/pt_BR/all.js (20 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 2.8KiB (22% reduction).
dig.do Mobile Resource Breakdown
| Total Resources | 37 |
| Number of Hosts | 14 |
| Static Resources | 21 |
| JavaScript Resources | 15 |
| CSS Resources | 1 |
dig.do mobile page usability
Last tested: 2017-04-26
dig.do Mobile Usability Test Quick Summary
priority - 8Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 756 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:
<iframe id="aswift_0" name="aswift_0"> falls outside the viewport.The element
<img src="/images_/top-sites.png"> falls outside the viewport.The element
<iframe src="https://web.fa…how_faces=true" name="f15688beb" class=""> falls outside the viewport.priority - 4Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<a href="http://dig.do/">dig.do - home</a> and 7 others are close to other tap targets.dig.do HTML validation
Warnings
The “type” attribute for the “style” element is not needed and should be omitted.
"...=yes" /> <style type="text/css"> a { ..."
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
"...opsites/"><img src="/images_/top-sites.png" border=0 alt="Top sites"></a><b..."
Element name “g:plusone” cannot be represented as XML 1.0.
"...: right"> <g:plusone size="medium" annotation="inline" width="250"></g:pl..."
The “type” attribute is unnecessary for JavaScript resources.
"...riate --> <script type="text/javascript"> (fu..."
Consider adding a “lang” attribute to the “html” start tag to declare the language of this document.
"...TYPE html> <meta http-equiv="content-type" content="text/html; charset=utf-8"/> <tit..."
Errors
The “clear” attribute on the “br” element is obsolete. Use CSS instead.
".../a> <br> <br clear=all> <div ..." Line: 148 Column: 1 - 14
"... </div> <br clear=all> <br> ..."
CSS: “xwidth”: Property “xwidth” doesn't exist.
"...<hr> <p> <div style=" float: left; xwidth: 50%; "> Dig.d..."
Element “g:plusone” not allowed as child of element “p” in this context. (Suppressing further errors from this subtree.)
"...: right"> <g:plusone size="medium" annotation="inline" width="250"></g:pl..."
dig.do similar domains
www.dig.net
www.dig.org
www.dig.info
www.dig.biz
www.dig.us
www.dig.mobi
www.ig.do
www.dig.do
www.xig.do
www.dxig.do
www.xdig.do
www.sig.do
www.dsig.do
www.sdig.do
www.eig.do
www.deig.do
www.edig.do
www.rig.do
www.drig.do
www.rdig.do
www.fig.do
www.dfig.do
www.fdig.do
www.cig.do
www.dcig.do
www.cdig.do
www.dg.do
www.dug.do
www.diug.do
www.duig.do
www.djg.do
www.dijg.do
www.djig.do
www.dkg.do
www.dikg.do
www.dkig.do
www.dog.do
www.diog.do
www.doig.do
www.di.do
www.dif.do
www.digf.do
www.difg.do
www.div.do
www.digv.do
www.divg.do
www.dit.do
www.digt.do
www.ditg.do
www.dib.do
www.digb.do
www.dibg.do
www.diy.do
www.digy.do
www.diyg.do
www.dih.do
www.digh.do
www.dihg.do
dig.do Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
dig.do TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.