YELLOWFEVER.CO.NZ Yellow Fever Ngā Wana Kōwhai · Supporters of the Wellington Phoenix

yellowfever.co.nz Website Information

Daily Unique Visits: 7,221

Daily Page Views: 36,105

Income Per Day: $90

Estimated Value: $54,000

This website is located in United States and is using following IP address 192.241.205.104. See the complete list of popular websites hosted in United States.

yellowfever.co.nz is registered under .NZ top-level domain. Please check other sites in .NZ zone.

Website yellowfever.co.nz is using the following name servers:

  • ns2.iwantmyname.net
  • ns4.iwantmyname.net
  • ns3.iwantmyname.net
  • ns1.iwantmyname.net

and is probably hosted by CLOUDFLARENET - Cloudflare, Inc., US. See the full list of other websites hosted by CLOUDFLARENET - Cloudflare, Inc., US.

The highest website yellowfever.co.nz position in Alexa rank database was 15818 and the lowest rank position was 998975. Current position of yellowfever.co.nz in Alexa rank database is 188683.

Desktop speed score of yellowfever.co.nz (63/100) is better than the results of 39.87% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of yellowfever.co.nz (79/100) is better than the results of 25.07% of other sites and means that the page is not mobile-friendly.

Mobile speed score of yellowfever.co.nz (57/100) is better than the results of 48.04% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

yellowfever.co.nz Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


yellowfever.co.nz whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


% 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-07-02T02:57:42+12:00
domain_name: yellowfever.co.nz
query_status: 200 Active
domain_dateregistered: 2007-03-20T17:41:50+12:00
domain_datelastmodified: 2022-04-24T18:17:29+12:00
domain_datecreated: 2007-03-20T17:41:50+12:00
domain_delegaterequested: yes
domain_signed: no
%
registrar_name: iwantmyname
registrar_address1: PO Box 11671
registrar_city: Wellington
registrar_postalcode: 6142
registrar_country: NZ (NEW ZEALAND)
registrar_phone: +64 6 8880031
registrar_fax: +64 6 8880031
registrar_email: help@support.iwantmyname.com
%
ns_name_01: ns2.digitalocean.com
ns_name_02: ns3.digitalocean.com
ns_name_03: ns1.digitalocean.com
%
% Additional information may be available at https://www.dnc.org.nz/whois/search?domain_name=yellowfever.co.nz
%

yellowfever.co.nz server information

Servers Location

yellowfever.co.nz desktop page speed rank

Last tested: 2019-02-06


Desktop Speed Bad
63/100

yellowfever.co.nz Desktop Speed Test Quick Summary


priority - 44Optimize images

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

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

Compressing http://cdn3.yellowfever.co.nz/uploads/banner/image…ark2019_300x600_01.jpg could save 132.5KiB (75% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/footer-…cedbd086ee6edeaca5.jpg could save 89.8KiB (70% reduction).
Compressing http://cdn1.yellowfever.co.nz/uploads/news_item/im…aper_files_folders.jpg could save 49.5KiB (86% reduction).
Compressing and resizing http://www.yellowfever.co.nz/assets/layout/yellowf…d96fa85b67e384c780.png could save 40KiB (72% reduction).
Compressing http://cdn3.yellowfever.co.nz/uploads/news_item/im…n_thumb_DSC02332-1.jpg could save 24.9KiB (81% reduction).
Compressing and resizing http://www.yellowfever.co.nz/assets/layout/phoenix…581fd95c59b8f97298.png could save 19.7KiB (73% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/theme-b…294eece0607606b951.png could save 18.6KiB (99% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/nav-bac…2bb540bd302122196b.png could save 16KiB (99% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…b77cd242f504788cbe.png could save 14.9KiB (85% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/theme-b…94ad811dc96fee52db.jpg could save 10.7KiB (97% reduction).
Compressing http://cdn2.yellowfever.co.nz/uploads/news_item/im…ligibilitycriteria.jpg could save 7.3KiB (63% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/news/…14eb9a161296eeae7b.jpg could save 1.9KiB (14% reduction).
Compressing http://cdn0.yellowfever.co.nz/uploads/news_item/im…de-awake-at-night1.jpg could save 1.5KiB (32% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/block-h…00dcc5767b6439f05b.jpg could save 1.4KiB (16% reduction).
Compressing http://cdn3.yellowfever.co.nz/uploads/news_item/im…es-1974780_960_720.jpg could save 1.4KiB (23% reduction).
Compressing http://cdn2.yellowfever.co.nz/uploads/news_item/im…in_thumb_C538PB-2T.jpg could save 1.3KiB (14% reduction).
Compressing http://cdn3.yellowfever.co.nz/uploads/news_item/im…_1_1_1_1_1_1_1_1_1.jpg could save 921B (15% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…38ba58ae2c2523eed6.png could save 252B (16% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…e1d03c49b6bc15edbc.png could save 244B (17% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/inputfi…7dff253e9359045bfd.jpg could save 221B (34% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…511f650bbfa9383e54.png could save 212B (14% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…0e268d1eff99eafd78.png could save 179B (12% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…bab014ed257276ea11.png could save 171B (12% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…c5fcda3572a8f9b672.png could save 158B (11% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…53d91a0f92544d9895.png could save 141B (11% reduction).

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

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

Remove render-blocking JavaScript:

http://www.yellowfever.co.nz/assets/application-dd…ac9f293585e22243893.js

Optimize CSS Delivery of the following:

http://www.yellowfever.co.nz/assets/yellow/applica…cfa93ffe8bb8474258.css

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

Minifying http://www.yellowfever.co.nz/assets/application-dd…ac9f293585e22243893.js could save 68.6KiB (37% reduction) after compression.

priority - 2Leverage 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://www.yellowfever.co.nz/assets/stag-bold-webf…6bad286f39852a4335.ttf (expiration not specified)
http://www.yellowfever.co.nz/assets/texgyreadvento…c0743024857bc2d17c.ttf (expiration not specified)
http://www.google-analytics.com/ga.js (2 hours)
https://js-agent.newrelic.com/nr-1118.min.js (2 hours)

yellowfever.co.nz Desktop Resource Breakdown

Total Resources49
Number of Hosts10
Static Resources44
JavaScript Resources4
CSS Resources1

yellowfever.co.nz mobile page speed rank

Last tested: 2019-02-06


Mobile Speed Bad
57/100

yellowfever.co.nz Mobile Speed Test Quick Summary


priority - 39Optimize images

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

Optimize the following images to reduce their size by 385.6KiB (69% reduction).

Compressing http://cdn2.yellowfever.co.nz/uploads/banner/image…ark2019_300x600_01.jpg could save 132.5KiB (75% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/footer-…cedbd086ee6edeaca5.jpg could save 89.8KiB (70% reduction).
Compressing http://cdn3.yellowfever.co.nz/uploads/news_item/im…aper_files_folders.jpg could save 49.5KiB (86% reduction).
Compressing http://cdn0.yellowfever.co.nz/uploads/news_item/im…n_thumb_DSC02332-1.jpg could save 24.9KiB (81% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/theme-b…294eece0607606b951.png could save 18.6KiB (99% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/nav-bac…2bb540bd302122196b.png could save 16KiB (99% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…b77cd242f504788cbe.png could save 14.9KiB (85% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/phoenix…581fd95c59b8f97298.png could save 11.5KiB (43% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/theme-b…94ad811dc96fee52db.jpg could save 10.7KiB (97% reduction).
Compressing http://cdn1.yellowfever.co.nz/uploads/news_item/im…ligibilitycriteria.jpg could save 7.3KiB (63% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/news/…14eb9a161296eeae7b.jpg could save 1.9KiB (14% reduction).
Compressing http://cdn0.yellowfever.co.nz/uploads/news_item/im…de-awake-at-night1.jpg could save 1.5KiB (32% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/block-h…00dcc5767b6439f05b.jpg could save 1.4KiB (16% reduction).
Compressing http://cdn2.yellowfever.co.nz/uploads/news_item/im…es-1974780_960_720.jpg could save 1.4KiB (23% reduction).
Compressing http://cdn0.yellowfever.co.nz/uploads/news_item/im…in_thumb_C538PB-2T.jpg could save 1.3KiB (14% reduction).
Compressing http://cdn1.yellowfever.co.nz/uploads/news_item/im…_1_1_1_1_1_1_1_1_1.jpg could save 921B (15% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…38ba58ae2c2523eed6.png could save 252B (16% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…e1d03c49b6bc15edbc.png could save 244B (17% reduction).
Compressing http://www.yellowfever.co.nz/assets/layout/inputfi…7dff253e9359045bfd.jpg could save 221B (34% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…511f650bbfa9383e54.png could save 212B (14% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…0e268d1eff99eafd78.png could save 179B (12% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…bab014ed257276ea11.png could save 171B (12% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…c5fcda3572a8f9b672.png could save 158B (11% reduction).
Compressing http://www.yellowfever.co.nz/assets/sections/table…53d91a0f92544d9895.png could save 141B (11% reduction).

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

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

Remove render-blocking JavaScript:

http://www.yellowfever.co.nz/assets/application-dd…ac9f293585e22243893.js

Optimize CSS Delivery of the following:

http://www.yellowfever.co.nz/assets/yellow/applica…cfa93ffe8bb8474258.css

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

Minifying http://www.yellowfever.co.nz/assets/application-dd…ac9f293585e22243893.js could save 68.6KiB (37% reduction) after compression.

priority - 3Leverage 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://www.yellowfever.co.nz/assets/stag-bold-webf…6bad286f39852a4335.ttf (expiration not specified)
http://www.yellowfever.co.nz/assets/texgyreadvento…c0743024857bc2d17c.ttf (expiration not specified)
http://www.google-analytics.com/ga.js (2 hours)
https://js-agent.newrelic.com/nr-1118.min.js (2 hours)

yellowfever.co.nz Mobile Resource Breakdown

Total Resources49
Number of Hosts10
Static Resources44
JavaScript Resources4
CSS Resources1

yellowfever.co.nz mobile page usability

Last tested: 2019-02-06


Mobile Usability Medium
79/100

yellowfever.co.nz Mobile Usability Test Quick Summary


priority - 11Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Register and 1 others render only 4 pixels tall (11 CSS pixels).

renders only 5 pixels tall (14 CSS pixels).

Kit: renders only 4 pixels tall (11 CSS pixels).

Contact us and 2 others render only 4 pixels tall (11 CSS pixels).

Home renders only 7 pixels tall (18 CSS pixels).

Podcasts and 7 others render only 7 pixels tall (18 CSS pixels).

Wednesday, 6 February, 2019 and 9 others render only 5 pixels tall (12 CSS pixels).

A collaborativ…ng the league. and 9 others render only 5 pixels tall (14 CSS pixels).

Read More and 9 others render only 5 pixels tall (14 CSS pixels).

VIEW MORE NEWS renders only 5 pixels tall (12 CSS pixels).
Phoenix City - Windswept renders only 5 pixels tall (14 CSS pixels).

Pts and 7 others render only 5 pixels tall (14 CSS pixels).

Wellington Phoenix and 9 others render only 5 pixels tall (14 CSS pixels).

-16 and 69 others render only 5 pixels tall (14 CSS pixels).

40 and 9 others render only 5 pixels tall (14 CSS pixels).

Powered by renders only 4 pixels tall (11 CSS pixels).

Privacy Policy and 1 others render only 5 pixels tall (14 CSS pixels).
- © Cop…Yellow Fever - and 1 others render only 5 pixels tall (14 CSS pixels).
Supporters of…ington Phoenix renders only 5 pixels tall (14 CSS pixels).

The following text fragments have a small line height. Increase the line height to make them more legible.

Pacific Games…ympics for men has a line height of only 108% of the font size.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 3Size 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 1,070 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <ul>Home New…op About</ul> falls outside the viewport.
The element <input id="q" type="text" name="q" class="form-control"> falls outside the viewport.
The element <button id="search_submit" type="submit">Go</button> falls outside the viewport.
The element <div class="col-ad"></div> falls outside the viewport.
The element <h2>Podcast</h2> falls outside the viewport.
The element <div class="content">Phoenix City -…Play</div> falls outside the viewport.
The element <h2>Table</h2> falls outside the viewport.
The element <div class="content">P W…Powered by</div> falls outside the viewport.

priority - 0Size 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="http://www.yel…er.co.nz/login">Login</a> is close to 1 other tap targets.

The tap target <a href="mailto:info@yellowfever.co.nz">Contact us</a> is close to 1 other tap targets.

The tap target <a href="http://www.yel…ver.co.nz/news">News</a> and 5 others are close to other tap targets.

The tap target <button id="search_submit" type="submit">Go</button> is close to 1 other tap targets.
The tap target <a href="/terms">Terms of Use</a> is close to 1 other tap targets.

yellowfever.co.nz HTML validation

Errors

Heading cannot be a child of another heading.

Line: 271 Column: 52 - 55
"... Christmas<h5> ..."

Element “div” not allowed as child of element “h5” in this context. (Suppressing further errors from this subtree.)

Line: 272 Column: 9 - 35
"...> <div class="audio-wrapper"> <..."

End tag “div” seen, but there were open elements.

Line: 277 Column: 5 - 10
"...iv> </div> </d..."

Unclosed element “h5”.

Line: 271 Column: 52 - 55
"... Christmas<h5> ..."

End tag for “body” seen, but there were unclosed elements.

Line: 461 Column: 1 - 7
"... </body> </htm..."

Unclosed element “div”.

Line: 80 Column: 3 - 20
"...</div> <div id="content"> <..."

Warnings

Empty heading.

Line: 271 Column: 52 - 55
"... Christmas<h5> ..."

This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.

Line: 2 Column: 16 - 6
"...TYPE html> <html> <head..."

yellowfever.co.nz similar domains

Similar domains:
www.yellowfever.com
www.yellowfever.net
www.yellowfever.org
www.yellowfever.info
www.yellowfever.biz
www.yellowfever.us
www.yellowfever.mobi
www.ellowfever.co.nz
www.yellowfever.co.nz
www.tellowfever.co.nz
www.ytellowfever.co.nz
www.tyellowfever.co.nz
www.gellowfever.co.nz
www.ygellowfever.co.nz
www.gyellowfever.co.nz
www.hellowfever.co.nz
www.yhellowfever.co.nz
www.hyellowfever.co.nz
www.uellowfever.co.nz
www.yuellowfever.co.nz
www.uyellowfever.co.nz
www.yllowfever.co.nz
www.ywllowfever.co.nz
www.yewllowfever.co.nz
www.ywellowfever.co.nz
www.ysllowfever.co.nz
www.yesllowfever.co.nz
www.ysellowfever.co.nz
www.ydllowfever.co.nz
www.yedllowfever.co.nz
www.ydellowfever.co.nz
www.yrllowfever.co.nz
www.yerllowfever.co.nz
www.yrellowfever.co.nz
www.yelowfever.co.nz
www.yeplowfever.co.nz
www.yelplowfever.co.nz
www.yepllowfever.co.nz
www.yeolowfever.co.nz
www.yelolowfever.co.nz
www.yeollowfever.co.nz
www.yeklowfever.co.nz
www.yelklowfever.co.nz
www.yekllowfever.co.nz
www.yelpowfever.co.nz
www.yellpowfever.co.nz
www.yeloowfever.co.nz
www.yelloowfever.co.nz
www.yelkowfever.co.nz
www.yellkowfever.co.nz
www.yellwfever.co.nz
www.yelliwfever.co.nz
www.yelloiwfever.co.nz
www.yelliowfever.co.nz
www.yellkwfever.co.nz
www.yellokwfever.co.nz
www.yelllwfever.co.nz
www.yellolwfever.co.nz
www.yelllowfever.co.nz
www.yellpwfever.co.nz
www.yellopwfever.co.nz
www.yellofever.co.nz
www.yelloqfever.co.nz
www.yellowqfever.co.nz
www.yelloqwfever.co.nz
www.yelloafever.co.nz
www.yellowafever.co.nz
www.yelloawfever.co.nz
www.yellosfever.co.nz
www.yellowsfever.co.nz
www.yelloswfever.co.nz
www.yelloefever.co.nz
www.yellowefever.co.nz
www.yelloewfever.co.nz
www.yellowever.co.nz
www.yellowcever.co.nz
www.yellowfcever.co.nz
www.yellowcfever.co.nz
www.yellowdever.co.nz
www.yellowfdever.co.nz
www.yellowdfever.co.nz
www.yellowrever.co.nz
www.yellowfrever.co.nz
www.yellowrfever.co.nz
www.yellowtever.co.nz
www.yellowftever.co.nz
www.yellowtfever.co.nz
www.yellowgever.co.nz
www.yellowfgever.co.nz
www.yellowgfever.co.nz
www.yellowvever.co.nz
www.yellowfvever.co.nz
www.yellowvfever.co.nz
www.yellowfver.co.nz
www.yellowfwver.co.nz
www.yellowfewver.co.nz
www.yellowfwever.co.nz
www.yellowfsver.co.nz
www.yellowfesver.co.nz
www.yellowfsever.co.nz
www.yellowfdver.co.nz
www.yellowfedver.co.nz
www.yellowfrver.co.nz
www.yellowferver.co.nz
www.yellowfeer.co.nz
www.yellowfecer.co.nz
www.yellowfevcer.co.nz
www.yellowfecver.co.nz
www.yellowfefer.co.nz
www.yellowfevfer.co.nz
www.yellowfefver.co.nz
www.yellowfeger.co.nz
www.yellowfevger.co.nz
www.yellowfegver.co.nz
www.yellowfeber.co.nz
www.yellowfevber.co.nz
www.yellowfebver.co.nz
www.yellowfevr.co.nz
www.yellowfevwr.co.nz
www.yellowfevewr.co.nz
www.yellowfevwer.co.nz
www.yellowfevsr.co.nz
www.yellowfevesr.co.nz
www.yellowfevser.co.nz
www.yellowfevdr.co.nz
www.yellowfevedr.co.nz
www.yellowfevder.co.nz
www.yellowfevrr.co.nz
www.yellowfeverr.co.nz
www.yellowfevrer.co.nz
www.yellowfeve.co.nz
www.yellowfevee.co.nz
www.yellowfevere.co.nz
www.yellowfeveer.co.nz
www.yellowfeved.co.nz
www.yellowfeverd.co.nz
www.yellowfevef.co.nz
www.yellowfeverf.co.nz
www.yellowfevefr.co.nz
www.yellowfevet.co.nz
www.yellowfevert.co.nz
www.yellowfevetr.co.nz

yellowfever.co.nz Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


yellowfever.co.nz TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.