williams.edu website information.
williams.edu domain name is registered by .EDU top-level domain registry. See the other sites registred in .EDU domain zone.
Following name servers are specified for williams.edu domain:
- lenox.williams.edu
- lee.williams.edu
- emergency.williams.edu
and probably website williams.edu 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 williams.edu position was 4793 (in the world). The lowest Alexa rank position was 5203. Now website williams.edu ranked in Alexa database as number 4816 (in the world).
Website williams.edu Desktop speed measurement score (60/100) is better than the results of 35.69% of other sites shows that the page desktop performance can be improved.
williams.edu Mobile usability score (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of williams.edu (22/100) is better than the results of 5.33% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
Date | Rank | Change |
---|---|---|
Nov-14-2024 | 4,816 | 30 |
Nov-13-2024 | 4,846 | 0 |
Nov-12-2024 | 4,846 | 0 |
Nov-11-2024 | 4,846 | 0 |
Nov-10-2024 | 4,846 | -17 |
Nov-09-2024 | 4,829 | 13 |
Nov-08-2024 | 4,842 | 10 |
Advertisement
williams.edu 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.
williams.edu 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.
This Registry database contains ONLY .EDU domains.
The data in the EDUCAUSE Whois database is provided
by EDUCAUSE for information purposes in order to
assist in the process of obtaining information about
or related to .edu domain registration records.
The EDUCAUSE Whois database is authoritative for the
.EDU domain.
A Web interface for the .EDU EDUCAUSE Whois Server is
available at: http://whois.educause.edu
By submitting a Whois query, you agree that this information
will not be used to allow, enable, or otherwise support
the transmission of unsolicited commercial advertising or
solicitations via e-mail. The use of electronic processes to
harvest information from this server is generally prohibited
except as reasonably necessary to register or modify .edu
domain names.
-------------------------------------------------------------
Domain Name: WILLIAMS.EDU
Registrant:
Williams College
Main Street
Williamstown, MA 01267
USA
Administrative Contact:
Ashley Frost
Williams College
Center for Computing Jesup Hall
Williamstown, MA 01267
USA
+1.4135973069
afrost@williams.edu
Technical Contact:
Ashley Frost
Williams College
Center for Computing Jesup Hall
Williamstown, MA 01267
USA
+1.4135973069
afrost@williams.edu
Name Servers:
EMERGENCY-DO.WILLIAMS.EDU
LEE.WILLIAMS.EDU
LENOX.WILLIAMS.EDU
Domain record activated: 29-Sep-1986
Domain record last updated: 02-Jul-2024
Domain expires: 31-Jul-2027
williams.edu server information
williams.edu desktop page speed rank
Last tested: 2016-09-03
williams.edu Desktop Speed Test Quick Summary
priority - 27 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 268KiB (67% reduction).
Compressing http://www.williams.edu/wp-content/plugins/wms-nav…idget.min.js?ver=1.0.8 could save 35.2KiB (64% reduction).
Compressing http://www.williams.edu/wp-includes/js/wp-emoji-release.min.js?ver=4.4.4 could save 25.8KiB (77% reduction).
Compressing http://www.williams.edu/wp-content/plugins/wms-mee…oncat.min.js?ver=2.0.0 could save 18.6KiB (75% reduction).
Compressing http://www.williams.edu/wp-includes/js/jquery/ui/sortable.min.js?ver=1.11.4 could save 17.9KiB (73% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/js/main.js?ver=1.73 could save 17.4KiB (67% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/js/quicklinks.js?ver=1.0 could save 16.7KiB (70% reduction).
Compressing http://www.williams.edu/wp-includes/js/jquery/ui/d…able.min.js?ver=1.11.4 could save 13.6KiB (73% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/…ybox.pack.js?ver=2.0.6 could save 13KiB (62% reduction).
Compressing http://www.williams.edu/wp-content/plugins/wms-mee…otope.min.js?ver=2.0.0 could save 10.7KiB (68% reduction).
Compressing http://www.williams.edu/wp-content/plugins/wms-mee…ctmasonry.js?ver=2.0.0 could save 7KiB (70% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/js/purl.js?ver=1.0 could save 6.1KiB (70% reduction).
Compressing http://www.williams.edu/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4 could save 4.2KiB (62% reduction).
Compressing http://www.williams.edu/wp-includes/js/jquery/ui/d…able.min.js?ver=1.11.4 could save 4.2KiB (68% reduction).
Compressing http://www.williams.edu/wp-includes/js/jquery/jque…grate.min.js?ver=1.2.1 could save 4KiB (57% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat-…age/js/main.js?ver=2.3 could save 3.2KiB (59% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/…box-media.js?ver=1.0.0 could save 2.9KiB (61% reduction).
Compressing http://www.williams.edu/wp-includes/js/jquery/ui/core.min.js?ver=1.11.4 could save 2.1KiB (54% reduction).
Compressing http://www.williams.edu/wp-includes/js/jquery/ui/mouse.min.js?ver=1.11.4 could save 2.1KiB (67% reduction).
Compressing http://www.williams.edu/wp-includes/js/jquery/jque…keys.min.js?ver=0.0.2m could save 862B (49% reduction).
Compressing http://www.williams.edu/wp-includes/js/wp-embed.min.js?ver=4.4.4 could save 653B (47% reduction).
Compressing http://www.williams.edu/wp-content/plugins/wms-mee…idget.min.js?ver=2.0.0 could save 525B (50% reduction).
priority - 17 Reduce server response time
In our test, your server responded in 1.9 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 12 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 119.2KiB (20% reduction).
Compressing http://www.williams.edu/files/Grid-Muse-Poet.jpg could save 23.2KiB (23% reduction).
Compressing http://www.williams.edu/files/Grid-Eyeball.jpg could save 18.4KiB (11% reduction).
Compressing http://www.williams.edu/files/DirectorsCup.crystal.jpg could save 16.2KiB (40% reduction).
Compressing http://www.williams.edu/files/WaxWorks.crop_.jpg could save 15KiB (24% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/img/williams.png could save 8.1KiB (52% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/img/icon_sprite.png could save 6.3KiB (12% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/img/williams_sm.png could save 3.2KiB (69% reduction).
Compressing http://www.williams.edu/files/TIFButtonUpdate.png could save 2.6KiB (52% reduction).
Compressing http://www.williams.edu/wp-content/themes/meerkat/img/w.png could save 523B (51% reduction).
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 8 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://www.williams.edu/wp-includes/js/jquery/jque…grate.min.js?ver=1.2.1
Optimize CSS Delivery of the following:
http://www.williams.edu/wp-content/themes/meerkat-homepage/style.css
http://www.williams.edu/wp-content/plugins/wms-mee…s/widget.css?ver=2.0.0
http://www.williams.edu/wp-content/plugins/wms-mee…crollbar.css?ver=2.0.0
http://www.williams.edu/wp-content/plugins/wms-nav…s/widget.css?ver=1.0.8
http://www.williams.edu/wp-includes/css/dashicons.min.css?ver=4.4.4
http://www.williams.edu/wp-content/plugins/wms-wid…css/loop.css?ver=4.4.4
http://www.williams.edu/files/themes/meerkat-homep…style.css?v=1472934277
priority - 3 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 32.3KiB (42% reduction).
Minifying http://www.williams.edu/wp-content/themes/meerkat/js/main.js?ver=1.73 could save 9KiB (35% reduction).
Minifying http://www.williams.edu/wp-content/plugins/wms-mee…ctmasonry.js?ver=2.0.0 could save 5.2KiB (52% reduction).
Minifying http://www.williams.edu/wp-content/themes/meerkat/js/purl.js?ver=1.0 could save 3.9KiB (46% reduction).
Minifying http://www.williams.edu/wp-content/themes/meerkat/…box-media.js?ver=1.0.0 could save 2.6KiB (54% reduction).
Minifying http://www.williams.edu/wp-content/themes/meerkat-…age/js/main.js?ver=2.3 could save 1.4KiB (26% reduction).
priority - 1 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://www.google.com/jsapi?autoload=%7B%22module…22%3A%22en%22%7D%5D%7D (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
priority - 1 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 4.8KiB (37% reduction).
Minifying http://www.williams.edu/wp-content/themes/meerkat-homepage/style.css could save 861B (27% reduction) after compression.
williams.edu Desktop Resources
Total Resources | 58 |
Number of Hosts | 7 |
Static Resources | 28 |
JavaScript Resources | 28 |
CSS Resources | 10 |
williams.edu Desktop Resource Breakdown
williams.edu mobile page speed rank
Last tested: 2019-12-10
williams.edu Mobile Speed Test Quick Summary
priority - 259 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 2.5MiB (83% reduction).
Compressing https://magazine.williams.edu/wp-content/blogs.dir…ener-Homepage-crop.jpg could save 957.4KiB (90% reduction).
Compressing https://magazine.williams.edu/wp-content/blogs.dir…ty-Images-Homepage.jpg could save 223KiB (48% reduction).
priority - 38 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://v1.addthisedge.com/live/boost/ra-512bca886…_ate.track.config_resp (59 seconds)
https://cdn.printfriendly.com/printfriendly.js (5 minutes)
https://s7.addthis.com/js/300/addthis_widget.js?ver=1.0 (10 minutes)
https://use.typekit.net/jwl0jgy.js?ver=5.2.3 (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-KWHWG4B (15 minutes)
https://www.google.com/cse/static/style/look/v3/default.css (50 minutes)
https://ds-4047.kxcdn.com/api/v3/domain_settings/a…&client_version=client (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://www.williams.edu/wp-content/lib/assets/js/…ht-config.js?ver=1.5.3 (4 hours)
https://www.williams.edu/wp-content/lib/assets/js/…light.min.js?ver=1.5.0 (4 hours)
https://www.williams.edu/wp-content/lib/assets/js/…uery.cookie.js?ver=1.0 (4 hours)
https://www.williams.edu/wp-content/lib/assets/js/…cycle2.min.js?ver=2.15 (4 hours)
https://www.williams.edu/wp-content/lib/assets/js/…ect_swipe.js?ver=2.1.3 (4 hours)
https://www.williams.edu/wp-content/lib/assets/js/….filter.min.js?ver=1.0 (4 hours)
https://www.williams.edu/wp-content/lib/assets/js/…r.pager.min.js?ver=1.0 (4 hours)
https://www.williams.edu/wp-content/lib/assets/js/…esorter.min.js?ver=1.0 (4 hours)
https://www.williams.edu/wp-content/lib/assets/js/vendor/purl.js?ver=1.0 (4 hours)
https://www.williams.edu/wp-content/plugins/cloudf…are-purge.js?ver=1.0.0 (4 hours)
https://www.williams.edu/wp-content/plugins/wms-me…oncat.min.js?ver=2.6.0 (4 hours)
https://www.williams.edu/wp-content/plugins/wms-me…js/widget.js?ver=2.6.0 (4 hours)
https://www.williams.edu/wp-content/plugins/wms-na…typeahead.js?ver=1.0.9 (4 hours)
https://www.williams.edu/wp-content/plugins/wms-na…js/widget.js?ver=1.0.9 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…/app.js?ver=1575985543 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…s_gallery.js?ver=5.2.3 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…lib/browser.js?ver=1.0 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…b/directory.js?ver=2.2 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…s/lib/facet.js?ver=1.0 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…agmanager.js?ver=1.0.0 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…ache.min.js?ver=1.0.13 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…main.js?ver=1573160984 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…do_tables.js?ver=1.0.0 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…avigation.js?ver=1.1.1 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…/uisearch.js?ver=1.0.0 (4 hours)
https://www.williams.edu/wp-content/themes/meerkat…us-fix.js?ver=20151112 (4 hours)
https://www.williams.edu/wp-includes/js/imagesloaded.min.js?ver=3.2.0 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/jqu…grate.min.js?ver=1.4.1 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/jqu…color.min.js?ver=2.1.1 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/jqu…keys.min.js?ver=0.0.2m (4 hours)
https://www.williams.edu/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp (4 hours)
https://www.williams.edu/wp-includes/js/jquery/jqu…onry.min.js?ver=3.1.2b (4 hours)
https://www.williams.edu/wp-includes/js/jquery/ui/core.min.js?ver=1.11.4 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/ui/…able.min.js?ver=1.11.4 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/ui/…able.min.js?ver=1.11.4 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/ui/mouse.min.js?ver=1.11.4 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/ui/…tion.min.js?ver=1.11.4 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/ui/…able.min.js?ver=1.11.4 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/ui/tooltip.min.js?ver=1.11.4 (4 hours)
https://www.williams.edu/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4 (4 hours)
https://www.williams.edu/wp-includes/js/masonry.min.js?ver=3.3.2 (4 hours)
https://www.williams.edu/wp-includes/js/wp-embed.min.js?ver=5.2.3 (4 hours)
https://www.williams.edu/wp-includes/js/wp-emoji-release.min.js?ver=5.2.3 (4 hours)
https://z.moatads.com/addthismoatframe568911941483/moatframe.js (8 hours)
priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 7 blocking script resources and 10 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://www.williams.edu/wp-includes/js/jquery/jqu…grate.min.js?ver=1.4.1
https://www.williams.edu/wp-includes/js/imagesloaded.min.js?ver=3.2.0
https://www.williams.edu/wp-includes/js/masonry.min.js?ver=3.3.2
https://www.williams.edu/wp-includes/js/jquery/jqu…onry.min.js?ver=3.1.2b
https://www.williams.edu/wp-content/themes/meerkat…ache.min.js?ver=1.0.13
https://use.typekit.net/jwl0jgy.js?ver=5.2.3
Optimize CSS Delivery of the following:
https://www.williams.edu/wp-content/plugins/wms-me…ss/style.css?ver=2.6.0
https://www.williams.edu/wp-content/plugins/wms-na…s/widget.css?ver=1.0.9
https://www.williams.edu/wp-includes/css/dist/bloc…tyle.min.css?ver=5.2.3
https://www.williams.edu/wp-includes/css/dashicons.min.css?ver=5.2.3
https://www.williams.edu/wp-content/lib/assets/js/…ager.min.css?ver=5.2.3
https://www.williams.edu/wp-content/lib/assets/js/…lter.min.css?ver=5.2.3
https://www.williams.edu/wp-content/lib/assets/fon…lack-tie.css?ver=3.4.1
https://www.williams.edu/wp-content/themes/meerkat…yle.css?ver=1573160984
https://www.williams.edu/wp-content/plugins/wms-wi…css/loop.css?ver=5.2.3
priority - 0 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 3.7KiB (32% reduction).
Minifying https://www.google.com/cse/static/style/look/v3/default.css could save 509B (19% reduction) after compression.
priority - 0 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 1.7KiB (16% reduction).
Minifying https://www.williams.edu/wp-content/lib/assets/js/…r.pager.min.js?ver=1.0 could save 172B (17% reduction) after compression.
Minifying https://www.williams.edu/wp-content/lib/assets/js/…uery.cookie.js?ver=1.0 could save 151B (27% reduction) after compression.
Minifying https://www.williams.edu/wp-includes/js/jquery/jqu…onry.min.js?ver=3.1.2b could save 119B (17% reduction) after compression.
Minifying https://www.williams.edu/wp-includes/js/jquery/ui/mouse.min.js?ver=1.11.4 could save 115B (12% reduction) after compression.
williams.edu Mobile Resources
Total Resources | 97 |
Number of Hosts | 18 |
Static Resources | 76 |
JavaScript Resources | 57 |
CSS Resources | 12 |
williams.edu Mobile Resource Breakdown
williams.edu mobile page usability
Last tested: 2019-12-10
williams.edu Mobile Usability Test Quick Summary
priority - 3 Size 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 446 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:
<span>Academics</span>
falls outside the viewport.The element
<span>Admission & Aid</span>
falls outside the viewport.The element
<span>Give to Williams</span>
falls outside the viewport.The element
<span>Varsity Sports</span>
falls outside the viewport.The element
<span>Arts at Williams</span>
falls outside the viewport.The element
<span>Environment & Sustainability</span>
falls outside the viewport.priority - 0 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.
<a id="slide-text-2" href="https://magazi…on-management/" class="hometrack slid…toggle slide-2">In Context We’…r Jeremy Cone.</a>
is close to 1 other tap targets.<a href="https://www.williams.edu" class="wordmark">Go to Williams College Home</a>
is close to 1 other tap targets.<a href="tel:413.597.3131">Williams Colle…(413) 597-3131</a>
is close to 1 other tap targets.<a href="#page">Back to top</a>
is close to 2 other tap targets.williams.edu similar domains
www.williams.net
www.williams.org
www.williams.info
www.williams.biz
www.williams.us
www.williams.mobi
www.illiams.edu
www.williams.edu
www.qilliams.edu
www.wqilliams.edu
www.qwilliams.edu
www.ailliams.edu
www.wailliams.edu
www.awilliams.edu
www.silliams.edu
www.wsilliams.edu
www.swilliams.edu
www.eilliams.edu
www.weilliams.edu
www.ewilliams.edu
www.wlliams.edu
www.wulliams.edu
www.wiulliams.edu
www.wuilliams.edu
www.wjlliams.edu
www.wijlliams.edu
www.wjilliams.edu
www.wklliams.edu
www.wiklliams.edu
www.wkilliams.edu
www.wolliams.edu
www.wiolliams.edu
www.woilliams.edu
www.wiliams.edu
www.wipliams.edu
www.wilpliams.edu
www.wiplliams.edu
www.wioliams.edu
www.wiloliams.edu
www.wikliams.edu
www.wilkliams.edu
www.wilpiams.edu
www.willpiams.edu
www.wiloiams.edu
www.willoiams.edu
www.wilkiams.edu
www.willkiams.edu
www.willams.edu
www.willuams.edu
www.williuams.edu
www.willuiams.edu
www.willjams.edu
www.willijams.edu
www.willjiams.edu
www.willkams.edu
www.willikams.edu
www.willoams.edu
www.willioams.edu
www.willims.edu
www.williqms.edu
www.williaqms.edu
www.williqams.edu
www.williwms.edu
www.williawms.edu
www.williwams.edu
www.willisms.edu
www.williasms.edu
www.willisams.edu
www.willizms.edu
www.williazms.edu
www.willizams.edu
www.willias.edu
www.willians.edu
www.williamns.edu
www.willianms.edu
www.williajs.edu
www.williamjs.edu
www.williajms.edu
www.williaks.edu
www.williamks.edu
www.williakms.edu
www.william.edu
www.williamw.edu
www.williamsw.edu
www.williamws.edu
www.williame.edu
www.williamse.edu
www.williames.edu
www.williamd.edu
www.williamsd.edu
www.williamds.edu
www.williamz.edu
www.williamsz.edu
www.williamzs.edu
www.williamx.edu
www.williamsx.edu
www.williamxs.edu
www.williama.edu
www.williamsa.edu
www.williamas.edu
williams.edu 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.
williams.edu 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.