fieldays.co.nz website information.
fieldays.co.nz domain name is registered by .NZ top-level domain registry. See the other sites registred in .NZ domain zone.
Following name servers are specified for fieldays.co.nz domain:
- kara.ns.cloudflare.com
- rob.ns.cloudflare.com
and probably website fieldays.co.nz is hosted by WIKIMEDIA - Wikimedia Foundation Inc., US web hosting company. Check the complete list of other most popular websites hosted by WIKIMEDIA - Wikimedia Foundation Inc., US hosting company.
According to Alexa traffic rank the highest website fieldays.co.nz position was 112460 (in the world). The lowest Alexa rank position was 998372. Now website fieldays.co.nz ranked in Alexa database as number 499181 (in the world).
Website fieldays.co.nz Desktop speed measurement score (54/100) is better than the results of 28.19% of other sites shows that the page desktop performance can be improved.
fieldays.co.nz 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 fieldays.co.nz (53/100) is better than the results of 39.51% 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-18-2024 | 499,181 | -14,288 |
| Nov-17-2024 | 484,893 | -187 |
| Nov-16-2024 | 484,706 | -12,245 |
| Nov-15-2024 | 472,461 | 3,659 |
| Nov-14-2024 | 476,120 | -6,782 |
| Nov-13-2024 | 469,338 | 0 |
| Nov-12-2024 | 469,338 | 0 |
Advertisement
fieldays.co.nz 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.
fieldays.co.nz 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.
% Terms of Use
%
% By submitting a WHOIS query you are entering into an agreement with Domain
% Name Commission Ltd on the following terms and conditions, and subject to
% all relevant .nz Policies and procedures as found at https://dnc.org.nz/.
%
% It is prohibited to:
% - Send high volume WHOIS queries with the effect of downloading part of or
% all of the .nz Register or collecting register data or records;
% - Access the .nz Register in bulk through the WHOIS service (ie. where a
% user is able to access WHOIS data other than by sending individual queries
% to the database);
% - Use WHOIS data to allow, enable, or otherwise support mass unsolicited
% commercial advertising, or mass solicitations to registrants or to
% undertake market research via direct mail, electronic mail, SMS, telephone
% or any other medium;
% - Use WHOIS data in contravention of any applicable data and privacy laws,
% including the Unsolicited Electronic Messages Act 2007;
% - Store or compile WHOIS data to build up a secondary register of
% information;
% - Publish historical or non-current versions of WHOIS data; and
% - Publish any WHOIS data in bulk.
%
% Copyright Domain Name Commission Limited (a company wholly-owned by Internet
% New Zealand Incorporated) which may enforce its rights against any person or
% entity that undertakes any prohibited activity without its written
% permission.
%
% The WHOIS service is provided by NZRS Limited.
%
version: 8.7
query_datetime: 2022-01-03T13:11:58+13:00
domain_name: fieldays.co.nz
query_status: 200 Active
domain_dateregistered: 1997-03-26T00:00:00+12:00
domain_datelastmodified: 2021-11-01T09:01:08+13:00
domain_datecreated: 1997-03-26T00:00:00+12:00
domain_delegaterequested: yes
domain_signed: no
%
registrar_name: Enlighten Domains
registrar_address1: PO Box 14167
registrar_city: HAMILTON
registrar_postalcode: 3252
registrar_country: NZ (NEW ZEALAND)
registrar_phone: +64 7 8536060
registrar_fax: +64 7 8553975
registrar_email: admin@enlightendomains.co.nz
%
ns_name_01: kara.ns.cloudflare.com
ns_name_02: rob.ns.cloudflare.com
%
% Additional information may be available at https://www.dnc.org.nz/whois/search?domain_name=fieldays.co.nz
%
fieldays.co.nz server information
fieldays.co.nz desktop page speed rank
Last tested: 2019-09-04
fieldays.co.nz Desktop Speed Test Quick Summary
priority - 69 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 670.3KiB (54% reduction).
Compressing and resizing https://www.fieldays.co.nz/wp-content/themes/field…s/NZ-Fieldays-logo.jpg could save 51.8KiB (93% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2018/01/id1596pic6.jpg could save 42.5KiB (32% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2018/05/App.png could save 41KiB (23% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2018/05/map-1.png could save 36.3KiB (24% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2019…-App-Explorer-Band.png could save 4.8KiB (14% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2018/05/get_tickets_green.png could save 732B (20% reduction).
Compressing https://yt3.ggpht.com/-c-XTv1oqCr0/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 465B (32% reduction).
priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 9 blocking script resources and 17 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.fieldays.co.nz/wp-includes/js/jquery/j…grate.min.js?ver=1.4.1
https://www.fieldays.co.nz/wp-content/plugins/fd-v…/hoverbox.js?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…/carousel.js?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…countdown.js?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…textblock.js?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…s/youtube.js?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/caro…ousel-min.js?ver=1.3.3
https://www.fieldays.co.nz/wp-content/plugins/caro…script-min.js?ver=1.11
Optimize CSS Delivery of the following:
https://www.fieldays.co.nz/wp-content/plugins/fd-v…css/icon.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…carousel.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…ountdown.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…extblock.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…tisement.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…/youtube.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…ss/image.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/fd-v…s/button.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/caro…css/style.css?ver=1.11
https://www.fieldays.co.nz/wp-content/plugins/caro…eme.style.css?ver=1.11
https://www.fieldays.co.nz/wp-content/plugins/caro…ansitions.css?ver=1.11
https://www.fieldays.co.nz/wp-content/plugins/caro…css/style.css?ver=1.11
https://www.fieldays.co.nz/wp-content/plugins/caro…ngle-post.css?ver=1.11
https://www.fieldays.co.nz/wp-includes/css/dist/bl…tyle.min.css?ver=5.2.2
https://www.fieldays.co.nz/wp-content/plugins/js_c…oser.min.css?ver=6.0.5
https://www.fieldays.co.nz/wp-content/themes/field…es/main-1c34c68252.css
priority - 9 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.
https://fieldays.co.nz/
https://www.fieldays.co.nz/
priority - 4 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/recaptcha/api2/webworker.js?hl=en&v=v1565591531251 (5 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-579DHDH (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/578755…58818?v=2.9.4&r=stable (20 minutes)
https://connect.facebook.net/signals/plugins/inferredEvents.js?v=2.9.4 (20 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 1 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 7.9KiB (55% reduction).
Compressing https://www.fieldays.co.nz/wp-content/plugins/caro…s/arrow-left-white.svg could save 1.5KiB (67% reduction).
Compressing https://www.fieldays.co.nz/wp-content/plugins/caro…/arrow-right-white.svg could save 1.5KiB (67% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…ages/vodafone-logo.svg could save 1.4KiB (52% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…t/images/instagram.svg could save 905B (54% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…ist/images/twitter.svg could save 339B (44% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…dist/images/radquo.svg could save 174B (38% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…/arrow-right-white.svg could save 166B (38% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…s/arrow-left-white.svg could save 164B (37% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…ist/images/youtube.svg could save 156B (33% reduction).
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 1KiB (30% reduction).
Minifying https://www.fieldays.co.nz/wp-content/plugins/fd-v…/youtube.css?ver=5.2.2 could save 323B (58% reduction) after compression.
Minifying https://www.fieldays.co.nz/wp-content/plugins/caro…css/style.css?ver=1.11 could save 227B (23% reduction) after compression.
Minifying https://www.fieldays.co.nz/wp-content/plugins/fd-v…hoverbox.css?ver=5.2.2 could save 118B (16% 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 727B (58% reduction).
Minifying https://www.fieldays.co.nz/wp-content/plugins/fd-v…/hoverbox.js?ver=5.2.2 could save 225B (79% reduction) after compression.
Minifying https://www.fieldays.co.nz/wp-content/plugins/fd-v…s/youtube.js?ver=5.2.2 could save 213B (78% reduction) after compression.
fieldays.co.nz Desktop Resources
| Total Resources | 95 |
| Number of Hosts | 15 |
| Static Resources | 77 |
| JavaScript Resources | 33 |
| CSS Resources | 20 |
fieldays.co.nz Desktop Resource Breakdown
fieldays.co.nz mobile page speed rank
Last tested: 2019-10-29
fieldays.co.nz Mobile Speed Test Quick Summary
priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 9 blocking script resources and 17 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.fieldays.co.nz/wp-includes/js/jquery/j…grate.min.js?ver=1.4.1
https://www.fieldays.co.nz/wp-content/plugins/fd-v…/hoverbox.js?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…/carousel.js?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…countdown.js?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…textblock.js?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…s/youtube.js?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/caro…ousel-min.js?ver=1.3.3
https://www.fieldays.co.nz/wp-content/plugins/caro…script-min.js?ver=1.11
Optimize CSS Delivery of the following:
https://www.fieldays.co.nz/wp-content/plugins/fd-v…css/icon.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…carousel.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…ountdown.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…extblock.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…tisement.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…/youtube.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…ss/image.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/fd-v…s/button.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/caro…css/style.css?ver=1.11
https://www.fieldays.co.nz/wp-content/plugins/caro…eme.style.css?ver=1.11
https://www.fieldays.co.nz/wp-content/plugins/caro…ansitions.css?ver=1.11
https://www.fieldays.co.nz/wp-content/plugins/caro…css/style.css?ver=1.11
https://www.fieldays.co.nz/wp-content/plugins/caro…ngle-post.css?ver=1.11
https://www.fieldays.co.nz/wp-includes/css/dist/bl…tyle.min.css?ver=5.2.4
https://www.fieldays.co.nz/wp-content/plugins/js_c…oser.min.css?ver=6.0.5
https://www.fieldays.co.nz/wp-content/themes/field…es/main-1c34c68252.css
priority - 34 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.
https://fieldays.co.nz/
https://www.fieldays.co.nz/
priority - 16 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 158.3KiB (29% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2018/05/App.png could save 41KiB (23% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2018/05/map-1.png could save 36.3KiB (24% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…s/NZ-Fieldays-logo.jpg could save 32.6KiB (58% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2019…-App-Explorer-Band.png could save 4.8KiB (14% reduction).
Compressing https://www.fieldays.co.nz/wp-content/uploads/2018/05/get_tickets_green.png could save 732B (20% reduction).
Compressing https://yt3.ggpht.com/-c-XTv1oqCr0/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 465B (32% reduction).
priority - 6 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/recaptcha/api2/webworker.js…bZx3NV5xhaMoMLrZV3TkN4 (5 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-579DHDH (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/578755…58818?v=2.9.5&r=stable (20 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 1 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 6.3KiB (55% reduction).
Compressing https://www.fieldays.co.nz/wp-content/plugins/caro…/arrow-right-white.svg could save 1.5KiB (67% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…ages/vodafone-logo.svg could save 1.4KiB (52% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…t/images/instagram.svg could save 905B (54% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…ist/images/twitter.svg could save 339B (44% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…dist/images/radquo.svg could save 174B (38% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…/arrow-right-white.svg could save 166B (38% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…s/arrow-left-white.svg could save 164B (37% reduction).
Compressing https://www.fieldays.co.nz/wp-content/themes/field…ist/images/youtube.svg could save 156B (33% reduction).
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 1KiB (30% reduction).
Minifying https://www.fieldays.co.nz/wp-content/plugins/fd-v…/youtube.css?ver=5.2.4 could save 323B (58% reduction) after compression.
Minifying https://www.fieldays.co.nz/wp-content/plugins/caro…css/style.css?ver=1.11 could save 227B (23% reduction) after compression.
Minifying https://www.fieldays.co.nz/wp-content/plugins/fd-v…hoverbox.css?ver=5.2.4 could save 118B (16% 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 727B (58% reduction).
Minifying https://www.fieldays.co.nz/wp-content/plugins/fd-v…/hoverbox.js?ver=5.2.4 could save 225B (79% reduction) after compression.
Minifying https://www.fieldays.co.nz/wp-content/plugins/fd-v…s/youtube.js?ver=5.2.4 could save 213B (78% reduction) after compression.
fieldays.co.nz Mobile Resources
| Total Resources | 95 |
| Number of Hosts | 16 |
| Static Resources | 76 |
| JavaScript Resources | 32 |
| CSS Resources | 20 |
fieldays.co.nz Mobile Resource Breakdown
fieldays.co.nz mobile page usability
Last tested: 2019-10-29
fieldays.co.nz 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.
<button type="button" class="navbar-toggler collapsed">Menu</button> is close to 1 other tap targets.The tap target
<button id="mc-embedded-subscribe" type="submit" name="submit" class="btn btn-primary"></button> is close to 1 other tap targets.The tap target
<a href="https://fielda…rivacy-policy/">Privacy Policy</a> and 3 others are close to other tap targets.fieldays.co.nz similar domains
www.fieldays.net
www.fieldays.org
www.fieldays.info
www.fieldays.biz
www.fieldays.us
www.fieldays.mobi
www.ieldays.co.nz
www.fieldays.co.nz
www.cieldays.co.nz
www.fcieldays.co.nz
www.cfieldays.co.nz
www.dieldays.co.nz
www.fdieldays.co.nz
www.dfieldays.co.nz
www.rieldays.co.nz
www.frieldays.co.nz
www.rfieldays.co.nz
www.tieldays.co.nz
www.ftieldays.co.nz
www.tfieldays.co.nz
www.gieldays.co.nz
www.fgieldays.co.nz
www.gfieldays.co.nz
www.vieldays.co.nz
www.fvieldays.co.nz
www.vfieldays.co.nz
www.feldays.co.nz
www.fueldays.co.nz
www.fiueldays.co.nz
www.fuieldays.co.nz
www.fjeldays.co.nz
www.fijeldays.co.nz
www.fjieldays.co.nz
www.fkeldays.co.nz
www.fikeldays.co.nz
www.fkieldays.co.nz
www.foeldays.co.nz
www.fioeldays.co.nz
www.foieldays.co.nz
www.fildays.co.nz
www.fiwldays.co.nz
www.fiewldays.co.nz
www.fiweldays.co.nz
www.fisldays.co.nz
www.fiesldays.co.nz
www.fiseldays.co.nz
www.fidldays.co.nz
www.fiedldays.co.nz
www.fideldays.co.nz
www.firldays.co.nz
www.fierldays.co.nz
www.fireldays.co.nz
www.fiedays.co.nz
www.fiepdays.co.nz
www.fielpdays.co.nz
www.fiepldays.co.nz
www.fieodays.co.nz
www.fielodays.co.nz
www.fieoldays.co.nz
www.fiekdays.co.nz
www.fielkdays.co.nz
www.fiekldays.co.nz
www.fielays.co.nz
www.fielxays.co.nz
www.fieldxays.co.nz
www.fielxdays.co.nz
www.fielsays.co.nz
www.fieldsays.co.nz
www.fielsdays.co.nz
www.fieleays.co.nz
www.fieldeays.co.nz
www.fieledays.co.nz
www.fielrays.co.nz
www.fieldrays.co.nz
www.fielrdays.co.nz
www.fielfays.co.nz
www.fieldfays.co.nz
www.fielfdays.co.nz
www.fielcays.co.nz
www.fieldcays.co.nz
www.fielcdays.co.nz
www.fieldys.co.nz
www.fieldqys.co.nz
www.fieldaqys.co.nz
www.fieldqays.co.nz
www.fieldwys.co.nz
www.fieldawys.co.nz
www.fieldways.co.nz
www.fieldsys.co.nz
www.fieldasys.co.nz
www.fieldzys.co.nz
www.fieldazys.co.nz
www.fieldzays.co.nz
www.fieldas.co.nz
www.fieldats.co.nz
www.fieldayts.co.nz
www.fieldatys.co.nz
www.fieldags.co.nz
www.fieldaygs.co.nz
www.fieldagys.co.nz
www.fieldahs.co.nz
www.fieldayhs.co.nz
www.fieldahys.co.nz
www.fieldaus.co.nz
www.fieldayus.co.nz
www.fieldauys.co.nz
www.fielday.co.nz
www.fieldayw.co.nz
www.fieldaysw.co.nz
www.fieldayws.co.nz
www.fieldaye.co.nz
www.fieldayse.co.nz
www.fieldayes.co.nz
www.fieldayd.co.nz
www.fieldaysd.co.nz
www.fieldayds.co.nz
www.fieldayz.co.nz
www.fieldaysz.co.nz
www.fieldayzs.co.nz
www.fieldayx.co.nz
www.fieldaysx.co.nz
www.fieldayxs.co.nz
www.fieldaya.co.nz
www.fieldaysa.co.nz
www.fieldayas.co.nz
fieldays.co.nz 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.
fieldays.co.nz 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.