JMWESTON.COM J.M. WESTON


jmweston.com website information.

jmweston.com website servers are located in Ireland and are responding from following IP address 54.76.103.85. Check the full list of most visited websites located in Ireland.

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

Following name servers are specified for jmweston.com domain:

  • ns1.internet-fr.net
  • ns2.internet-fr.net

According to Alexa traffic rank the highest website jmweston.com position was 24918 (in the world). The lowest Alexa rank position was 999184. Now website jmweston.com ranked in Alexa database as number 190346 (in the world).

Website jmweston.com Desktop speed measurement score (57/100) is better than the results of 29.1% of other sites shows that the page desktop performance can be improved.

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

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

Weekly Rank Report

DateRankChange
Jan-29-2020 190,346N/A
Jan-28-2020 N/AN/A
Jan-27-2020 N/AN/A
Jan-26-2020 N/AN/A
Jan-25-2020 N/AN/A
Jan-24-2020 220,103N/A
Jan-23-2020 N/AN/A

Advertisement

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


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


jmweston.com server information

Servers Location

jmweston.com desktop page speed rank

Last tested: 2020-01-19


Desktop Speed Bad
57/100

jmweston.com Desktop Speed Test Quick Summary


priority - 41 Optimize images

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

Optimize the following images to reduce their size by 396.9KiB (47% reduction).

Compressing https://cdn.jmweston.com/skin/frontend/base/default/images/kickers1.jpg could save 116.3KiB (70% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/default/images/kickers5.jpg could save 113KiB (50% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/default/images/kickers4.jpg could save 106KiB (56% reduction).
Compressing https://cdn.jmweston.com/media/catalog/category/sousmenuOS.jpg could save 21.4KiB (22% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/default/images/kickers6.jpg could save 19.3KiB (21% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/default/images/kickers3.jpg could save 8.9KiB (21% reduction).
Compressing https://cdn.jmweston.com/media/catalog/category/Visuel-Histoire-FR_1.jpg could save 5.5KiB (19% reduction).
Compressing and resizing https://cdn.jmweston.com/skin/frontend/base/defaul…ages/pic_instagram.png could save 1.9KiB (80% reduction).
Compressing and resizing https://cdn.jmweston.com/skin/frontend/base/defaul…ages/pic_recherche.png could save 1.7KiB (73% reduction).
Compressing and resizing https://cdn.jmweston.com/skin/frontend/base/default/images/pic_youtube.png could save 1.5KiB (76% reduction).
Compressing and resizing https://cdn.jmweston.com/skin/frontend/base/default/images/pic_facebook.png could save 1.1KiB (78% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/defaul…ages/pic_pinterest.png could save 114B (28% reduction).

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

Your page has 30 blocking script resources and 13 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://cdn.jmweston.com/js/lib/jquery-2.2.0.js
https://cdn.jmweston.com/js/prototype/prototype.js
https://cdn.jmweston.com/js/lib/ccard.js
https://cdn.jmweston.com/js/prototype/validation.js
https://cdn.jmweston.com/js/scriptaculous/builder.js
https://cdn.jmweston.com/js/scriptaculous/effects.js
https://cdn.jmweston.com/js/scriptaculous/dragdrop.js
https://cdn.jmweston.com/js/scriptaculous/controls.js
https://cdn.jmweston.com/js/scriptaculous/slider.js
https://cdn.jmweston.com/js/varien/js.js
https://cdn.jmweston.com/js/varien/form.js
https://cdn.jmweston.com/js/varien/menu.js
https://cdn.jmweston.com/js/mage/translate.js
https://cdn.jmweston.com/js/mage/cookies.js
https://cdn.jmweston.com/js/lib/jQuerynoConflict.js
https://cdn.jmweston.com/js/lib/jquery.mousewheel.js
https://cdn.jmweston.com/js/lib/jquery.jscrollpane.min.js
https://cdn.jmweston.com/js/lib/jquery.cycle.js
https://cdn.jmweston.com/js/lib/ddaccordion.js
https://cdn.jmweston.com/js/lib/jquery.qtip.min.js
https://cdn.jmweston.com/js/lib/jquery.jplayer.min.js
https://cdn.jmweston.com/js/lib/animations.js
https://cdn.jmweston.com/js/modernizr.js
https://cdn.jmweston.com/js/weston.js
https://cdn.jmweston.com/js/jquery.panzoom.js
https://cdn.jmweston.com/skin/frontend/base/defaul…in/jquery-ui-1-10-4.js
https://cdn.jmweston.com/skin/frontend/base/defaul…ajaxlogin/ajaxlogin.js
https://cstatic.weborama.fr/js/advertiserv2/adperf_conversion.js
https://bs.serving-sys.com/Serving/ActivityServer.…rnd=342879.11537103355
https://bs.serving-sys.com/Serving/ActivityServer.…&rnd=94937.10426613688

Optimize CSS Delivery of the following:

https://cdn.jmweston.com/skin/frontend/base/default/css/stylesportrait.css
https://cdn.jmweston.com/skin/frontend/base/default/css/widgets.css
https://cdn.jmweston.com/skin/frontend/base/defaul…jquery.jscrollpane.css
https://cdn.jmweston.com/skin/frontend/base/defaul…i-1.9.1.custom.min.css
https://cdn.jmweston.com/skin/frontend/base/default/css/jquery.qtip.min.css
https://cdn.jmweston.com/skin/frontend/base/default/css/jplayer.css
https://cdn.jmweston.com/skin/frontend/base/default/css/parallax.css
https://cdn.jmweston.com/skin/frontend/base/default/css/normalize.css
https://cdn.jmweston.com/skin/frontend/base/default/css/weston.css
https://cdn.jmweston.com/skin/frontend/base/defaul…/jmw-8b74b2.weston.css
https://fonts.googleapis.com/css?family=Marcellus|Montserrat
https://cdn.jmweston.com/skin/frontend/base/default/css/style-fix.css
https://cdn.jmweston.com/skin/frontend/base/defaul…jaxlogin/ajaxlogin.css

priority - 13 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 123.7KiB (37% reduction).

Minifying https://cdn.jmweston.com/js/lib/jquery-2.2.0.js could save 38.6KiB (50% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/defaul…in/jquery-ui-1-10-4.js could save 37.2KiB (36% reduction) after compression.
Minifying https://cdn.jmweston.com/js/weston.js could save 12.2KiB (31% reduction) after compression.
Minifying https://cdn.jmweston.com/js/jquery.panzoom.js could save 5.7KiB (52% reduction) after compression.
Minifying https://cdn.jmweston.com/js/prototype/prototype.js could save 5.6KiB (16% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/jquery.cycle.js could save 5.5KiB (41% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/controls.js could save 2.8KiB (33% reduction) after compression.
Minifying https://cdn.jmweston.com/js/prototype/validation.js could save 2.2KiB (27% reduction) after compression.
Minifying https://cdn.jmweston.com/js/varien/js.js could save 2.1KiB (35% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/ddaccordion.js could save 2KiB (45% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/effects.js could save 1.8KiB (21% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/dragdrop.js could save 1.7KiB (23% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/defaul…ajaxlogin/ajaxlogin.js could save 1.4KiB (42% reduction) after compression.
Minifying https://cdn.jmweston.com/js/varien/form.js could save 987B (31% reduction) after compression.
Minifying https://cdn.jmweston.com/js/varien/menu.js could save 720B (50% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/slider.js could save 670B (25% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/builder.js could save 582B (32% reduction) after compression.
Minifying https://cdn.jmweston.com/js/mage/cookies.js could save 556B (52% reduction) after compression.
Minifying https://cdn.jmweston.com/js/mage/translate.js could save 489B (66% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/jquery.mousewheel.js could save 404B (43% reduction) after compression.
Minifying https://cstatic.weborama.fr/js/advertiserv2/adperf_conversion.js could save 221B (15% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/ccard.js could save 213B (49% reduction) after compression.
Minifying https://www.jmweston.com/debugClasses.js could save 118B (25% reduction) after compression.

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:

https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-MBH2NVP (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/182468…7636?v=2.9.15&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2 Reduce server response time

In our test, your server responded in 0.45 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 - 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 13.5KiB (24% reduction).

Minifying https://cdn.jmweston.com/skin/frontend/base/default/css/stylesportrait.css could save 6.3KiB (20% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/default/css/normalize.css could save 1.7KiB (65% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/default/css/weston.css could save 1.7KiB (20% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/default/css/jplayer.css could save 1.2KiB (39% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/defaul…i-1.9.1.custom.min.css could save 890B (16% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/default/css/widgets.css could save 606B (50% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/default/css/print.css could save 470B (63% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/defaul…jaxlogin/ajaxlogin.css could save 334B (22% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/defaul…jquery.jscrollpane.css could save 195B (29% reduction) after compression.
Minifying https://www.jmweston.com/skin/frontend/base/defaul…r/popup_newsletter.css could save 108B (17% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/default/css/style-fix.css could save 105B (19% reduction) after compression.

priority - 1 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 4.9KiB (30% reduction).

Minifying https://www.jmweston.com/ could save 4.9KiB (30% reduction) after compression.

jmweston.com Desktop Resources

Total Resources112
Number of Hosts26
Static Resources80
JavaScript Resources46
CSS Resources17

jmweston.com Desktop Resource Breakdown

jmweston.com mobile page speed rank

Last tested: 2020-01-19


Mobile Speed Bad
50/100

jmweston.com Mobile Speed Test Quick Summary


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

Your page has 1 blocking script 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://maps.googleapis.com/maps/api/js?key=AIzaSy…false&libraries=places

priority - 39 Optimize images

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

Optimize the following images to reduce their size by 382.1KiB (48% reduction).

Compressing https://www.jmweston.com/media/catalog/category/les-boutiques1807.jpg could save 129.2KiB (49% reduction).
Compressing https://www.jmweston.com/media/catalog/category/femmes1807.jpg could save 81.9KiB (49% reduction).
Compressing https://www.jmweston.com/media/catalog/category/chaussures1807.jpg could save 64KiB (46% reduction).
Compressing https://www.jmweston.com/media/catalog/category/weston-vintage1807.jpg could save 57.9KiB (50% reduction).
Compressing https://www.jmweston.com/media/catalog/category/soldes-20201807.jpg could save 45.6KiB (43% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/mobile…bg_gradient_retina.png could save 935B (85% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/mobile…es/i_menu_retina_1.png could save 894B (84% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/mobile…tom/bg_logo_retina.png could save 806B (16% reduction).
Compressing https://cdn.jmweston.com/skin/frontend/base/mobile…/bg_divider_retina.png could save 780B (76% reduction).

priority - 13 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 126.8KiB (36% reduction).

Minifying https://cdn.jmweston.com/js/lib/jquery-2.2.0.js could save 38.6KiB (50% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/defaul…in/jquery-ui-1-10-4.js could save 37.2KiB (36% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/mobile/js/weston_mobile.js could save 12.2KiB (31% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/jquery.storelocator.js could save 6KiB (43% reduction) after compression.
Minifying https://cdn.jmweston.com/js/prototype/prototype.js could save 5.6KiB (16% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/jquery.cycle.js could save 5.5KiB (41% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/controls.js could save 2.8KiB (33% reduction) after compression.
Minifying https://cdn.jmweston.com/js/prototype/validation.js could save 2.2KiB (27% reduction) after compression.
Minifying https://cdn.jmweston.com/js/varien/js.js could save 2.1KiB (35% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/mobile/js/iphone.js could save 2.1KiB (26% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/ddaccordion.js could save 2KiB (45% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/effects.js could save 1.8KiB (21% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/mobile/js/dnd.js could save 1.7KiB (38% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/dragdrop.js could save 1.7KiB (23% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/defaul…ajaxlogin/ajaxlogin.js could save 1.4KiB (42% reduction) after compression.
Minifying https://cdn.jmweston.com/js/varien/form.js could save 987B (31% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/slider.js could save 670B (25% reduction) after compression.
Minifying https://cdn.jmweston.com/js/scriptaculous/builder.js could save 582B (32% reduction) after compression.
Minifying https://cdn.jmweston.com/js/mage/cookies.js could save 556B (52% reduction) after compression.
Minifying https://cdn.jmweston.com/js/mage/translate.js could save 489B (66% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/jquery.mousewheel.js could save 404B (43% reduction) after compression.
Minifying https://cdn.jmweston.com/js/lib/ccard.js could save 213B (49% reduction) after compression.
Minifying https://www.jmweston.com/debugClasses.js could save 118B (25% reduction) after compression.

priority - 10 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://jmweston.com/
https://www.jmweston.com/
https://www.jmweston.com/mobile_fr/

priority - 5 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.googletagmanager.com/gtm.js?id=GTM-MBH2NVP (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/182468…7636?v=2.9.15&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://maps.googleapis.com/maps/api/js?key=AIzaSy…false&libraries=places (30 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 1 Reduce server response time

In our test, your server responded in 0.27 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 - 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 6.8KiB (20% reduction).

Minifying https://cdn.jmweston.com/skin/frontend/base/mobile/css/iphone.css could save 3.9KiB (17% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/mobile/css/weston_mobile.css could save 1.7KiB (20% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/mobile/css/widgets.css could save 795B (44% reduction) after compression.
Minifying https://cdn.jmweston.com/skin/frontend/base/defaul…jaxlogin/ajaxlogin.css could save 334B (22% reduction) after compression.
Minifying https://www.jmweston.com/skin/frontend/base/defaul…r/popup_newsletter.css could save 108B (17% reduction) after compression.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.8KiB (21% reduction).

Minifying https://www.jmweston.com/mobile_fr/ could save 1.8KiB (21% reduction) after compression.

jmweston.com Mobile Resources

Total Resources86
Number of Hosts19
Static Resources65
JavaScript Resources40
CSS Resources7

jmweston.com Mobile Resource Breakdown

jmweston.com mobile page usability

Last tested: 2020-01-19


Mobile Usability Good
99/100

jmweston.com Mobile Usability Test Quick Summary


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.

The tap target <a href="https://www.jm…fr/information">Plus d’infos</a> is close to 2 other tap targets.

jmweston.com Mobile Resources

Total Resources86
Number of Hosts19
Static Resources65
JavaScript Resources40
CSS Resources7

jmweston.com Mobile Resource Breakdown

jmweston.com similar domains

Similar domains:
www.jmweston.com
www.jmweston.net
www.jmweston.org
www.jmweston.info
www.jmweston.biz
www.jmweston.us
www.jmweston.mobi
www.mweston.com
www.jmweston.com
www.nmweston.com
www.jnmweston.com
www.njmweston.com
www.hmweston.com
www.jhmweston.com
www.hjmweston.com
www.umweston.com
www.jumweston.com
www.ujmweston.com
www.imweston.com
www.jimweston.com
www.ijmweston.com
www.kmweston.com
www.jkmweston.com
www.kjmweston.com
www.mmweston.com
www.jmmweston.com
www.mjmweston.com
www.jweston.com
www.jnweston.com
www.jmnweston.com
www.jjweston.com
www.jmjweston.com
www.jjmweston.com
www.jkweston.com
www.jmkweston.com
www.jmeston.com
www.jmqeston.com
www.jmwqeston.com
www.jmqweston.com
www.jmaeston.com
www.jmwaeston.com
www.jmaweston.com
www.jmseston.com
www.jmwseston.com
www.jmsweston.com
www.jmeeston.com
www.jmweeston.com
www.jmeweston.com
www.jmwston.com
www.jmwwston.com
www.jmwewston.com
www.jmwweston.com
www.jmwsston.com
www.jmwesston.com
www.jmwdston.com
www.jmwedston.com
www.jmwdeston.com
www.jmwrston.com
www.jmwerston.com
www.jmwreston.com
www.jmweton.com
www.jmwewton.com
www.jmweswton.com
www.jmweeton.com
www.jmweseton.com
www.jmwedton.com
www.jmwesdton.com
www.jmwezton.com
www.jmweszton.com
www.jmwezston.com
www.jmwexton.com
www.jmwesxton.com
www.jmwexston.com
www.jmweaton.com
www.jmwesaton.com
www.jmweaston.com
www.jmweson.com
www.jmwesron.com
www.jmwestron.com
www.jmwesrton.com
www.jmwesfon.com
www.jmwestfon.com
www.jmwesfton.com
www.jmwesgon.com
www.jmwestgon.com
www.jmwesgton.com
www.jmwesyon.com
www.jmwestyon.com
www.jmwesyton.com
www.jmwestn.com
www.jmwestin.com
www.jmwestoin.com
www.jmwestion.com
www.jmwestkn.com
www.jmwestokn.com
www.jmwestkon.com
www.jmwestln.com
www.jmwestoln.com
www.jmwestlon.com
www.jmwestpn.com
www.jmwestopn.com
www.jmwestpon.com
www.jmwesto.com
www.jmwestob.com
www.jmwestonb.com
www.jmwestobn.com
www.jmwestoh.com
www.jmwestonh.com
www.jmwestohn.com
www.jmwestoj.com
www.jmwestonj.com
www.jmwestojn.com
www.jmwestom.com
www.jmwestonm.com
www.jmwestomn.com
www.jmweston.con

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


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