7.5 sec in total
1.5 sec
5.6 sec
518 ms
Welcome to whoisds.com homepage info - get ready to check Whois Ds best content for India right away, or after learning these important things about whoisds.com
At Whoisds you can get all type of domain data include all domain information on daily base in CSV file. 100% Free newly registered domains also available.
Visit whoisds.comWe analyzed Whoisds.com page load time and found that the first response time was 1.5 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
whoisds.com performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value9.8 s
0/100
25%
Value12.4 s
3/100
10%
Value4,440 ms
0/100
30%
Value0.257
48/100
15%
Value19.9 s
2/100
10%
1455 ms
33 ms
691 ms
536 ms
505 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 68% of them (50 requests) were addressed to the original Whoisds.com, 8% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Static-v.tawk.to. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Whoisds.com.
Page size can be reduced by 1.5 MB (67%)
2.3 MB
743.5 kB
In fact, the total size of Whoisds.com main page is 2.3 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 35.6 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 35.6 kB or 84% of the original size.
Potential reduce by 21.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. Whois Ds images are well optimized though.
Potential reduce by 809.4 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 809.4 kB or 73% of the original size.
Potential reduce by 666.9 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. Whoisds.com needs all CSS files to be minified and compressed as it can save up to 666.9 kB or 87% of the original size.
Number of requests can be reduced by 50 (82%)
61
11
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whois Ds. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
whoisds.com
1455 ms
css
33 ms
bootstrap.css
691 ms
font-awesome.css
536 ms
simple-line-icons.css
505 ms
owl.carousel.min.css
513 ms
owl.theme.default.min.css
663 ms
magnific-popup.css
683 ms
theme.css
794 ms
theme-elements.css
1040 ms
theme-blog.css
820 ms
theme-shop.css
1001 ms
theme-animate.css
1020 ms
settings.css
1027 ms
layers.css
1063 ms
navigation.css
1101 ms
component.css
1376 ms
default.css
1389 ms
custom.css
1344 ms
jquery.js
20 ms
modernizr.js
1292 ms
jquery.dataTables.css
1348 ms
jquery.dataTables.min.css
56 ms
dataTables.tableTools.css
1458 ms
jquery.dataTables.js
1807 ms
jquery.dataTables.min.js
60 ms
dataTables.tableTools.js
1682 ms
1.js
1610 ms
jquery.appear.js
1719 ms
jquery.easing.js
1718 ms
jquery-cookie.js
1642 ms
bootstrap.js
2047 ms
common.js
2047 ms
jquery.validation.js
2056 ms
jquery.stellar.js
2053 ms
jquery.easy-pie-chart.js
2051 ms
jquery.gmap.js
2102 ms
jquery.lazyload.js
2134 ms
jquery.isotope.js
2166 ms
owl.carousel.js
2367 ms
jquery.magnific-popup.js
2407 ms
vide.js
1915 ms
theme.js
1858 ms
jquery.themepunch.tools.min.js
2128 ms
jquery.themepunch.revolution.min.js
2048 ms
jquery.flipshow.js
1943 ms
view.home.js
2027 ms
theme.init.js
1965 ms
logo.png
1044 ms
whoisdsemail.jpg
1045 ms
whois-database-download-newly-registered-domains.jpg
2050 ms
logo-foot.png
1169 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
56 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
55 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
56 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
56 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
55 ms
fontawesome-webfont.woff
2024 ms
Simple-Line-Icons.woff
1715 ms
clhLqOv7MXn459PTh0gXYBayoCksK7A5ZWkzVNukUdQ.ttf
55 ms
analytics.js
122 ms
default
230 ms
collect
13 ms
icons.png
159 ms
emojione.min.css
139 ms
emojione.min.js
154 ms
1484807683931
383 ms
62.png
131 ms
ajax-loader.gif
131 ms
133 ms
33 ms
233 ms
v3
70 ms
whoisds.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
whoisds.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
whoisds.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoisds.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 Whoisds.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.
whoisds.com
Open Graph description is not detected on the main page of Whois Ds. 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: