DOODLE.COM Easy scheduling | Doodle


doodle.com website information.

doodle.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

No name server records were found.

and probably website doodle.com is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.

According to Alexa traffic rank the highest website doodle.com position was 1743 (in the world). The lowest Alexa rank position was 1882. Now website doodle.com ranked in Alexa database as number 1880 (in the world).

Website doodle.com Desktop speed measurement score (90/100) is better than the results of 88.96% of other sites and shows that the page is performing great on desktop computers.

doodle.com Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of doodle.com (52/100) is better than the results of 37.6% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Apr-26-2024 1,880-11
Apr-25-2024 1,8690
Apr-24-2024 1,8690
Apr-23-2024 1,869-1
Apr-22-2024 1,868-15
Apr-21-2024 1,8534
Apr-20-2024 1,8570

Advertisement

doodle.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



doodle.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: DOODLE.COM
Registry Domain ID: 23630_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.corehub.net
Registrar URL: http://corehub.net
Updated Date: 2020-12-09T08:52:34Z
Creation Date: 1995-12-06T05:00:00Z
Registry Expiry Date: 2021-12-05T05:00:00Z
Registrar: Corehub, S.R.L.
Registrar IANA ID: 15
Registrar Abuse Contact Email: abuse@corehub.net
Registrar Abuse Contact Phone: +34935275235
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: JONAH.NS.CLOUDFLARE.COM
Name Server: MIRA.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-04-24T20:27:40Z

doodle.com server information

Servers Location

IP Address
Country
Region
City

doodle.com desktop page speed rank

Last tested: 2016-06-12


Desktop Speed Good
90/100

doodle.com Desktop Speed Test Quick Summary


priority - 6 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 9 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://doodle.com/builtstatic/1465286543/libs/js/jQuery/jquery-2.1.4.js
http://doodle.com/np/config?locale=en_US
http://doodle.com/np/nls/en_US/l10nScript
http://doodle.com/np/templates/script?groups[]=com…roups[]=stingrayShared
http://adserver.adtech.de/addyn/3.0/1284/3583575/0…366;misc=1465709214865
http://adserver.adtech.de/addyn/3.0/1284/3583577/0…366;misc=1465709214891
http://adserver.adtech.de/addyn/3.0/1284/3583576/0…366;misc=1465709214892
http://adserver.adtech.de/addyn/3.0/1284/3583574/0…366;misc=1465709214893
http://doodle.com/builtstatic/1465286543/libs/js/requirejs/requirejs.min.js

Optimize CSS Delivery of the following:

http://doodle.com/builtstatic/1465286543/doodle/css/landing/home.css

priority - 3 Leverage 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://doodle.wemfbox.ch/blank.gif (expiration not specified)
http://scripts.kissmetrics.com/95d80792dff37c16388…abeff76f2a821bb5b.2.js (60 seconds)
http://static.hotjar.com/c/hotjar-142490.js?sv=5 (60 seconds)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-CFKQ (16.2 minutes)
http://beacon.errorception.com/56bafccd1f5a7d1c09000c69.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

doodle.com Desktop Resources

Total Resources30
Number of Hosts14
Static Resources18
JavaScript Resources19
CSS Resources1

doodle.com Desktop Resource Breakdown

doodle.com mobile page speed rank

Last tested: 2018-02-07


Mobile Speed Bad
52/100

doodle.com Mobile Speed Test Quick Summary


priority - 72 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://cdn2.doodle.com/dist/vendor.1be78d34412cc5dd0a1a.js
https://doodle.com/np/config?locale=en_US
https://doodle.com/np/nls/en_US/l10nScript
https://cdn2.doodle.com/dist/home.388af675e18076819db8.js

Optimize CSS Delivery of the following:

https://cdn2.doodle.com/dist/vendor-styles.46a4367…44ecddff040509eef2.css
https://cdn2.doodle.com/dist/home.ce95a29e8409562bd647c5899b3707c6.css
https://fonts.googleapis.com/css?family=Fira+Sans:…700italic|Caveat+Brush

priority - 20 Leverage 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:

https://cdn2.doodle.com/dist/home.388af675e18076819db8.js (expiration not specified)
https://cdn2.doodle.com/dist/home.ce95a29e8409562bd647c5899b3707c6.css (expiration not specified)
https://cdn2.doodle.com/dist/i/07b16de211727247b81a91a03653bfea.png (expiration not specified)
https://cdn2.doodle.com/dist/i/5b1a607d9580eb51c6dcb895767a789b.png (expiration not specified)
https://cdn2.doodle.com/dist/i/e77f3b7823f4d4b7c8412751779cab98.png (expiration not specified)
https://cdn2.doodle.com/dist/i/f4184b4f88c2a2c2937915536a8e5911.png (expiration not specified)
https://cdn2.doodle.com/dist/i/fe9ecc393c7cff86f4d3f664f50169f5.png (expiration not specified)
https://cdn2.doodle.com/dist/vendor-styles.46a4367…44ecddff040509eef2.css (expiration not specified)
https://cdn2.doodle.com/dist/vendor.1be78d34412cc5dd0a1a.js (expiration not specified)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://cdn.syndication.twimg.com/tweets.json?call…codes=true&tz=GMT-0800 (60 seconds)
https://static.hotjar.com/c/hotjar-142490.js?sv=5 (60 seconds)
https://syndication.twitter.com/settings (10 minutes)
https://www.google-analytics.com/gtm/js?id=GTM-W4V…d=742419155.1518045766 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-CFKQ (15 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 8 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 74.6KiB (71% reduction).

Compressing and resizing https://cdn2.doodle.com/dist/i/fe9ecc393c7cff86f4d3f664f50169f5.png could save 18.8KiB (95% reduction).
Compressing and resizing https://cdn2.doodle.com/dist/i/e77f3b7823f4d4b7c8412751779cab98.png could save 16KiB (94% reduction).
Compressing and resizing https://cdn2.doodle.com/dist/i/f4184b4f88c2a2c2937915536a8e5911.png could save 14.8KiB (94% reduction).
Compressing and resizing https://cdn2.doodle.com/dist/i/07b16de211727247b81a91a03653bfea.png could save 13.5KiB (94% reduction).
Compressing https://pbs.twimg.com/card_img/958434943222386688/…mat=png&name=144x144_2 could save 1.4KiB (17% reduction).
Compressing https://pbs.twimg.com/profile_images/923621515286913024/_db-YyUT_bigger.jpg could save 1KiB (34% reduction).
Compressing https://pbs.twimg.com/profile_images/798117355838640128/sJq52tZo_bigger.jpg could save 1KiB (44% reduction).
Compressing https://pbs.twimg.com/profile_images/919564350117089282/jr2rkDbz_bigger.jpg could save 1KiB (35% reduction).
Compressing https://pbs.twimg.com/profile_images/827522995564474368/CB3yjKJB_bigger.jpg could save 1,008B (34% reduction).
Compressing https://pbs.twimg.com/profile_images/931246000991223809/KVUv6SMM_bigger.jpg could save 994B (58% reduction).
Compressing https://pbs.twimg.com/profile_images/818935840516800512/aIFgdGkm_bigger.jpg could save 968B (37% reduction).
Compressing https://pbs.twimg.com/profile_images/889466874672668672/aUtB6Adq_bigger.jpg could save 924B (36% reduction).
Compressing https://pbs.twimg.com/profile_images/776150205439832064/iiBrbS1n_bigger.jpg could save 908B (31% reduction).
Compressing https://pbs.twimg.com/profile_images/887826037295505408/4O530oM4_bigger.jpg could save 879B (27% reduction).
Compressing https://pbs.twimg.com/profile_images/4415530210721…0/YNbTftG__bigger.jpeg could save 775B (38% reduction).
Compressing https://pbs.twimg.com/profile_images/692793957747548160/8fwDMkIg_bigger.jpg could save 769B (28% reduction).

doodle.com Mobile Resources

Total Resources82
Number of Hosts19
Static Resources57
JavaScript Resources27
CSS Resources5

doodle.com Mobile Resource Breakdown

doodle.com mobile page usability

Last tested: 2018-02-07


Mobile Usability Good
99/100

doodle.com Mobile Usability Test Quick Summary


priority - 1 Size 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.

The tap target <a href="https://t.co/gW1b26D7vh" class="link customisable">http://doodle.com</a> is close to 1 other tap targets.
The tap target <a href="https://twitte…43909476995072" class="u-linkBlend u-…long-permalink">1:08 AM - Jun 22, 2016</a> is close to 1 other tap targets.
The tap target <a href="https://twitte…43909476995072" class="Tweet-action--…ion--heartEdge">45</a> is close to 1 other tap targets.
The tap target <a href="https://suppor…icles/20175256" class="Icon Icon--inf…ScribingTarget">Twitter Ads info and privacy</a> is close to 1 other tap targets.
The tap target <button type="button" class="d-button d-twe…on slick-arrow"></button> and 1 others are close to other tap targets.

doodle.com similar domains

Similar domains:
www.doodle.com
www.doodle.net
www.doodle.org
www.doodle.info
www.doodle.biz
www.doodle.us
www.doodle.mobi
www.oodle.com
www.doodle.com
www.xoodle.com
www.dxoodle.com
www.xdoodle.com
www.soodle.com
www.dsoodle.com
www.sdoodle.com
www.eoodle.com
www.deoodle.com
www.edoodle.com
www.roodle.com
www.droodle.com
www.rdoodle.com
www.foodle.com
www.dfoodle.com
www.fdoodle.com
www.coodle.com
www.dcoodle.com
www.cdoodle.com
www.dodle.com
www.diodle.com
www.doiodle.com
www.dioodle.com
www.dkodle.com
www.dokodle.com
www.dkoodle.com
www.dlodle.com
www.dolodle.com
www.dloodle.com
www.dpodle.com
www.dopodle.com
www.dpoodle.com
www.doidle.com
www.dooidle.com
www.dokdle.com
www.dookdle.com
www.doldle.com
www.dooldle.com
www.dopdle.com
www.doopdle.com
www.doole.com
www.dooxle.com
www.doodxle.com
www.dooxdle.com
www.doosle.com
www.doodsle.com
www.doosdle.com
www.dooele.com
www.doodele.com
www.dooedle.com
www.doorle.com
www.doodrle.com
www.doordle.com
www.doofle.com
www.doodfle.com
www.doofdle.com
www.doocle.com
www.doodcle.com
www.doocdle.com
www.doode.com
www.doodpe.com
www.doodlpe.com
www.doodple.com
www.doodoe.com
www.doodloe.com
www.doodole.com
www.doodke.com
www.doodlke.com
www.doodkle.com
www.doodl.com
www.doodlw.com
www.doodlew.com
www.doodlwe.com
www.doodls.com
www.doodles.com
www.doodlse.com
www.doodld.com
www.doodled.com
www.doodlde.com
www.doodlr.com
www.doodler.com
www.doodlre.com
www.doodle.con

doodle.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


doodle.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.