tower.co.nz website information.
tower.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 tower.co.nz domain:
- ns.domainnetwork.se
- ns2.domainnetwork.se
- ns3.domainnetwork.com
and probably website tower.co.nz is hosted by NIH-NET - National Institutes of Health, US web hosting company. Check the complete list of other most popular websites hosted by NIH-NET - National Institutes of Health, US hosting company.
According to Alexa traffic rank the highest website tower.co.nz position was 39116 (in the world). The lowest Alexa rank position was 999806. Now website tower.co.nz ranked in Alexa database as number 574990 (in the world).
Website tower.co.nz Desktop speed measurement score (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.
tower.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 tower.co.nz (60/100) is better than the results of 54.7% 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 |
|---|---|---|
| Sep-25-2024 | N/A | N/A |
| Sep-24-2024 | 574,990 | 17,197 |
| Sep-23-2024 | 592,187 | -11,760 |
| Sep-22-2024 | 580,427 | 1,605 |
| Sep-21-2024 | 582,032 | -15,028 |
| Sep-20-2024 | 567,004 | 22,470 |
| Sep-19-2024 | 589,474 | 7,828 |
Advertisement
tower.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.
tower.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: 2021-11-25T00:39:48+13:00
domain_name: tower.co.nz
query_status: 200 Active
domain_dateregistered: 2000-09-26T15:26:35+12:00
domain_datelastmodified: 2021-11-20T01:38:02+13:00
domain_datecreated: 1997-04-04T00:00:00+12:00
domain_delegaterequested: yes
domain_signed: no
%
registrar_name: CSC Corporate Domains, Inc
registrar_address1: 251 Little Falls Drive,
registrar_city: Wilmington
registrar_province: Delaware
registrar_postalcode: 19808
registrar_country: US (UNITED STATES)
registrar_phone: +1 302 6365400
registrar_fax: +1 302 636 54500
registrar_email: tldsupport@cscglobal.com
%
ns_name_01: ns.domainnetwork.se
ns_name_02: ns2.domainnetwork.se
ns_name_03: ns3.domainnetwork.com
%
% Additional information may be available at https://www.dnc.org.nz/whois/search?domain_name=tower.co.nz
%
tower.co.nz server information
tower.co.nz desktop page speed rank
Last tested: 2015-09-07
tower.co.nz Desktop Speed Test Quick Summary
priority - 6 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 61KiB (5% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/50%20percent…/Video-Confidence.ashx could save 8.2KiB (8% reduction).
Losslessly compressing https://d1hsywbuwp5s57.cloudfront.net/touchpointcx…idein/feedback-btn.png could save 5.2KiB (56% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/50%20percent…mages/SmartDriver.ashx could save 4.4KiB (8% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Homepage%20i…ackage%20discount.ashx could save 2.7KiB (10% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Hero%20Images/Homepage2.ashx could save 1.9KiB (2% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Homepage%20i…ravel%20insurance.ashx could save 1.9KiB (3% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Homepage%20i…tents%20insurance.ashx could save 1.8KiB (5% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Homepage%20i…House%20insurance.ashx could save 1.8KiB (3% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Homepage%20i…Other%20insurance.ashx could save 1.8KiB (3% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Homepage%20i…d/Car%20insurance.ashx could save 1.8KiB (4% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Promotions/Free-fuel-campaign.ashx could save 913B (1% reduction).
Losslessly compressing http://www.tower.co.nz/~/media/Images/Hero%20Images/Homepage1.ashx could save 814B (1% reduction).
priority - 4 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
http://www.tower.co.nz/layouts/system/VisitorIdentification.js
Optimize CSS Delivery of the following:
http://www.tower.co.nz/bundles/Tower/CustomStyles?…HkJ2tChzTu9m2Wp6zzsAo1
http://www.tower.co.nz/bundles/Tower/JQueryStyles?…Dxk3ApJ8x-rvy7J8nXbrs1
priority - 3 Reduce server response time
In our test, your server responded in 0.38 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 - 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://d1hsywbuwp5s57.cloudfront.net/touchpointcx…idein/feedback-btn.png (60 seconds)
https://d1hsywbuwp5s57.cloudfront.net/touchpointcx…0902a5344e5bb2171.1.js (60 seconds)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-5DHJJ2 (16.2 minutes)
http://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 10.7KiB (70% reduction).
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 3.7KiB (2% reduction).
Minifying https://d1hsywbuwp5s57.cloudfront.net/touchpointcx…0902a5344e5bb2171.1.js could save 1.3KiB (9% reduction).
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.4KiB (14% reduction).
tower.co.nz Desktop Resources
| Total Resources | 45 |
| Number of Hosts | 12 |
| Static Resources | 29 |
| JavaScript Resources | 11 |
| CSS Resources | 4 |
tower.co.nz Desktop Resource Breakdown
tower.co.nz mobile page speed rank
Last tested: 2019-06-21
tower.co.nz Mobile Speed Test Quick Summary
priority - 26 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://www.tower.co.nz/
https://www.tower.co.nz/
priority - 24 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://www.tower.co.nz/bundles/Common/TopLibs?v=Q…t7oUOJAggG80vl1X-EGBM1
https://www.tower.co.nz/layouts/system/VisitorIdentification.js
Optimize CSS Delivery of the following:
https://www.tower.co.nz/bundles/Tower/CustomStyles…tFuCjoWWfzQHDk-sbrP3s1
https://www.tower.co.nz/bundles/Common/JQueryStyle…NINr2_a_75Jt1IXhbZ9Hk1
priority - 11 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://d3f5l8ze0o4j2m.cloudfront.net/m87/k33spt.js (expiration not specified)
https://js.adsrvr.org/up_loader.1.1.0.js (expiration not specified)
https://static.hotjar.com/c/hotjar-1298719.js?sv=5 (60 seconds)
https://www.google-analytics.com/gtm/js?id=GTM-P3W…d=373536705.1561089994 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-5DHJJ2 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/128388…9227?v=2.8.51&r=stable (20 minutes)
https://connect.facebook.net/signals/config/411182…8946?v=2.8.51&r=stable (20 minutes)
https://connect.facebook.net/signals/plugins/inferredEvents.js?v=2.8.51 (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://www.googletagservices.com/activeview/js/cu…dar.js?cache=r20110914 (50 minutes)
https://a.tribalfusion.com/pixel/tags/car/755553/pixel.js (60 minutes)
https://rules.quantcount.com/rules-p-BebMKfvnpgehQ.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.inspectlet.com/inspectlet.js (4 hours)
priority - 7 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 64KiB (28% reduction).
Compressing https://www.tower.co.nz/~/media/Images/Hero%20Imag…erheating-700x430.ashx could save 7.1KiB (17% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/pr…nce_296x296.ashx?mw=70 could save 4.7KiB (38% reduction).
Compressing https://www.tower.co.nz/~/media/Images/Hero%20Imag…ro-mobile-940x769.ashx could save 4.7KiB (44% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/pr…vel_296x296.ashx?mw=70 could save 4.4KiB (33% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/pr…car_296x296.ashx?mw=70 could save 3.9KiB (34% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/navigation_tower_logo.ashx could save 3.2KiB (33% reduction).
Compressing https://d3f5l8ze0o4j2m.cloudfront.net/m87/close.png could save 3.1KiB (23% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/pr…use_296x296.ashx?mw=70 could save 2.9KiB (42% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/pr…nts_296x296.ashx?mw=70 could save 2.2KiB (33% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Homepage…ed_140x140.ashx?mw=150 could save 1.7KiB (33% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/pr…ess_296x296.ashx?mw=70 could save 1.6KiB (32% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Homepage…on_140x140.ashx?mw=150 could save 1.6KiB (36% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Homepage…on_140x140.ashx?mw=150 could save 1.5KiB (35% reduction).
Compressing https://www.tower.co.nz/~/media/Images/custom-logo…92E8CA8BE40805AE8DAEE6 could save 1.5KiB (28% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Homepage…on_140x140.ashx?mw=150 could save 1.5KiB (31% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Homepage…icon_280x90.ashx?mw=40 could save 1.3KiB (17% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/na…travel_icon_60x60.ashx could save 542B (27% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/na…urance_icon_60x60.ashx could save 524B (30% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/na…ntents_icon_60x60.ashx could save 423B (32% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/na…_house_icon_60x60.ashx could save 322B (33% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/na…own_car_icon60x60.ashx could save 260B (31% reduction).
Compressing https://www.tower.co.nz/~/media/Images/bu/Icons/na…siness-icon_60x60.ashx could save 146B (30% reduction).
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 11KiB (71% reduction).
Compressing https://rules.quantcount.com/rules-p-BebMKfvnpgehQ.js could save 2.5KiB (69% reduction).
Compressing https://widget-mediator.zopim.com/s/W/xdds/1hj8cu2IJ9p8roeW/p/1561089994020 could save 1.1KiB (63% reduction).
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.3KiB (15% reduction).
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.3KiB (31% reduction).
Minifying https://a.tribalfusion.com/pixel/tags/car/755553/pixel.js could save 321B (17% reduction) after compression.
Minifying https://www.tower.co.nz/Scripts/Tower/wffm.js could save 213B (28% reduction) after compression.
Minifying https://www.tower.co.nz/layouts/system/VisitorIdentification.js could save 102B (16% reduction) after compression.
tower.co.nz Mobile Resources
| Total Resources | 101 |
| Number of Hosts | 31 |
| Static Resources | 52 |
| JavaScript Resources | 42 |
| CSS Resources | 3 |
tower.co.nz Mobile Resource Breakdown
tower.co.nz mobile page usability
Last tested: 2019-06-21
tower.co.nz Mobile Usability Test Quick Summary
priority - 1 Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<button class="owl-dot active"></button> and 3 others are close to other tap targets.The tap target
<a href="/promo/terms-a…irpoints-terms">Ts&Cs apply</a> is close to 1 other tap targets.The tap target
<a href="/airpoints" class="">Start earning…oints Dollars™</a> is close to 1 other tap targets.The tap target
<a href="/travel-insurance">Travel insurance</a> and 1 others are close to other tap targets.The tap target
<a href="/terms-and-conditions">Terms & conditions</a> and 3 others are close to other tap targets.tower.co.nz similar domains
www.tower.net
www.tower.org
www.tower.info
www.tower.biz
www.tower.us
www.tower.mobi
www.ower.co.nz
www.tower.co.nz
www.rower.co.nz
www.trower.co.nz
www.rtower.co.nz
www.fower.co.nz
www.tfower.co.nz
www.ftower.co.nz
www.gower.co.nz
www.tgower.co.nz
www.gtower.co.nz
www.yower.co.nz
www.tyower.co.nz
www.ytower.co.nz
www.twer.co.nz
www.tiwer.co.nz
www.toiwer.co.nz
www.tiower.co.nz
www.tkwer.co.nz
www.tokwer.co.nz
www.tkower.co.nz
www.tlwer.co.nz
www.tolwer.co.nz
www.tlower.co.nz
www.tpwer.co.nz
www.topwer.co.nz
www.tpower.co.nz
www.toer.co.nz
www.toqer.co.nz
www.towqer.co.nz
www.toqwer.co.nz
www.toaer.co.nz
www.towaer.co.nz
www.toawer.co.nz
www.toser.co.nz
www.towser.co.nz
www.toswer.co.nz
www.toeer.co.nz
www.toweer.co.nz
www.toewer.co.nz
www.towr.co.nz
www.towwr.co.nz
www.towewr.co.nz
www.towwer.co.nz
www.towsr.co.nz
www.towesr.co.nz
www.towdr.co.nz
www.towedr.co.nz
www.towder.co.nz
www.towrr.co.nz
www.towerr.co.nz
www.towrer.co.nz
www.towe.co.nz
www.towee.co.nz
www.towere.co.nz
www.towed.co.nz
www.towerd.co.nz
www.towef.co.nz
www.towerf.co.nz
www.towefr.co.nz
www.towet.co.nz
www.towert.co.nz
www.towetr.co.nz
tower.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.
tower.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.