IRD.GOVT.NZ Inland Revenue - Te Tari Taake


ird.govt.nz website information.

ird.govt.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 ird.govt.nz domain:

  • ns3.digital.govt.nz
  • ns4.digital.govt.nz
  • ns5.digital.govt.nz
  • ns1.digital.govt.nz
  • ns2.digital.govt.nz

According to Alexa traffic rank the highest website ird.govt.nz position was 4459 (in the world). The lowest Alexa rank position was 249933. Current position of ird.govt.nz in Alexa rank database is below 1 million.

Website ird.govt.nz Desktop speed measurement score (84/100) is better than the results of 78.07% of other sites and shows that the page is performing great on desktop computers.

ird.govt.nz Mobile usability score (94/100) is better than the results of 36.81% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of ird.govt.nz (67/100) is better than the results of 70.58% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Apr-26-2024 N/AN/A
Apr-25-2024 N/AN/A
Apr-24-2024 N/AN/A
Apr-23-2024 N/AN/A
Apr-22-2024 N/AN/A
Apr-21-2024 N/AN/A
Apr-20-2024 N/AN/A

Advertisement

ird.govt.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.



ird.govt.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-04-26T00:13:52+12:00
domain_name: govt.nz
query_status: 520 This domain is not available for registration
%
% Additional information may be available at https://www.dnc.org.nz/whois/
%

ird.govt.nz server information

Servers Location

IP Address
103.241.84.213
Region
Wellington
City
Wellington

ird.govt.nz desktop page speed rank

Last tested: 2016-08-08


Desktop Speed Medium
84/100

ird.govt.nz Desktop Speed Test Quick Summary


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

Your page has 5 blocking script resources and 5 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.ird.govt.nz/resources/6/1/619281004d816…2d/jquery-1.3.2.min.js
http://www.ird.govt.nz/resources/c/6/c660ef004d816…ui-1.7.1.custom.min.js
https://apis.google.com/js/platform.js
http://www.ird.govt.nz/resources/f/9/f9557308-0fa5…806/ird-mobile-menu.js
http://www.ird.govt.nz/resources/9/0/907fc600424d6…d82245c33b7/rotator.js

Optimize CSS Delivery of the following:

http://www.ird.govt.nz/about-this-site/site-design/css/ir-layout.css
http://www.ird.govt.nz/about-this-site/site-design/css/ir-menu.css
http://www.ird.govt.nz/about-this-site/site-design/css/ir-menu-dna.css
http://www.ird.govt.nz/about-this-site/site-design…-mobile-overwrites.css
http://www.ird.govt.nz/about-this-site/site-design/css/ir-mobile-media.css

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:

http://platform.twitter.com/widgets.js (30 minutes)
https://apis.google.com/js/platform.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://www.google-analytics.com/plugins/ga/inpage_linkid.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
http://www.ird.govt.nz/resources/6/1/619281004d816…2d/jquery-1.3.2.min.js (2 days)
http://www.ird.govt.nz/resources/9/0/907fc600424d6…d82245c33b7/rotator.js (2 days)
http://www.ird.govt.nz/resources/c/6/c660ef004d816…ui-1.7.1.custom.min.js (2 days)
http://www.ird.govt.nz/resources/f/9/f9557308-0fa5…806/ird-mobile-menu.js (2 days)

priority - 3 Optimize images

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

Optimize the following images to reduce their size by 29.9KiB (38% reduction).

Losslessly compressing http://www.ird.govt.nz/resources/a/4/a4e1cb804ba37…9ef8e4b077/irdlogo.gif could save 13.3KiB (85% reduction).
Losslessly compressing http://www.ird.govt.nz/resources/e/a/eab47671-923a…ts_carousel_22june.jpg could save 9.1KiB (19% reduction).
Losslessly compressing http://www.ird.govt.nz/resources/2/1/210d368043464…4be/sprite-buttons.gif could save 2.6KiB (43% reduction).
Losslessly compressing http://www.ird.govt.nz/resources/2/3/239362004c8ae…7f75f0fc5c95c/myir.png could save 2.5KiB (63% reduction).
Losslessly compressing http://www.ird.govt.nz/resources/0/0/0014b58042448…33b7/forward-arrow.gif could save 1.3KiB (69% reduction).
Losslessly compressing http://www.ird.govt.nz/resources/5/0/500198ff-f443…188/makepayment-bg.png could save 1.1KiB (33% reduction).

priority - 0 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 2.8KiB (65% reduction).

Compressing https://platform.twitter.com/js/button.1813ea3f78757294e1ba1cea21b068a0.js could save 2.8KiB (65% 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 2.2KiB (13% reduction).

Minifying http://www.ird.govt.nz/about-this-site/site-design/css/ir-layout.css could save 2.2KiB (13% 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.2KiB (11% reduction).

Minifying http://www.ird.govt.nz/ could save 1.2KiB (11% reduction) after compression.

ird.govt.nz Desktop Resources

Total Resources72
Number of Hosts13
Static Resources61
JavaScript Resources18
CSS Resources8

ird.govt.nz Desktop Resource Breakdown

ird.govt.nz mobile page speed rank

Last tested: 2019-12-07


Mobile Speed Medium
67/100

ird.govt.nz Mobile Speed Test Quick Summary


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

Your page has 5 blocking script resources and 5 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.ird.govt.nz/resources/6/1/619281004d816…2d/jquery-1.3.2.min.js
http://www.ird.govt.nz/resources/c/6/c660ef004d816…ui-1.7.1.custom.min.js
https://apis.google.com/js/platform.js
http://www.ird.govt.nz/resources/f/9/f9557308-0fa5…806/ird-mobile-menu.js
http://www.ird.govt.nz/resources/9/0/907fc600424d6…d82245c33b7/rotator.js

Optimize CSS Delivery of the following:

http://www.ird.govt.nz/about-this-site/site-design/css/ir-layout.css
http://www.ird.govt.nz/about-this-site/site-design/css/ir-menu.css
http://www.ird.govt.nz/about-this-site/site-design/css/ir-menu-dna.css
http://www.ird.govt.nz/about-this-site/site-design…-mobile-overwrites.css
http://www.ird.govt.nz/about-this-site/site-design/css/ir-mobile-media.css

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:

http://platform.twitter.com/widgets.js (30 minutes)
https://apis.google.com/js/platform.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://www.google-analytics.com/plugins/ga/inpage_linkid.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
http://www.ird.govt.nz/resources/6/1/619281004d816…2d/jquery-1.3.2.min.js (2 days)
http://www.ird.govt.nz/resources/9/0/907fc600424d6…d82245c33b7/rotator.js (2 days)
http://www.ird.govt.nz/resources/c/6/c660ef004d816…ui-1.7.1.custom.min.js (2 days)
http://www.ird.govt.nz/resources/f/9/f9557308-0fa5…806/ird-mobile-menu.js (2 days)

priority - 3 Optimize images

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

Optimize the following images to reduce their size by 26.1KiB (37% reduction).

Losslessly compressing http://www.ird.govt.nz/resources/a/4/a4e1cb804ba37…9ef8e4b077/irdlogo.gif could save 13.3KiB (85% reduction).
Losslessly compressing http://www.ird.govt.nz/resources/e/a/eab47671-923a…ts_carousel_22june.jpg could save 9.1KiB (19% reduction).
Losslessly compressing http://www.ird.govt.nz/resources/2/3/239362004c8ae…7f75f0fc5c95c/myir.png could save 2.5KiB (63% reduction).
Losslessly compressing http://www.ird.govt.nz/resources/0/0/0014b58042448…33b7/forward-arrow.gif could save 1.3KiB (69% 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 2.2KiB (13% reduction).

Minifying http://www.ird.govt.nz/about-this-site/site-design/css/ir-layout.css could save 2.2KiB (13% 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.2KiB (11% reduction).

Minifying http://www.ird.govt.nz/ could save 1.2KiB (11% reduction) after compression.

ird.govt.nz Mobile Resources

Total Resources56
Number of Hosts13
Static Resources45
JavaScript Resources18
CSS Resources8

ird.govt.nz Mobile Resource Breakdown

ird.govt.nz mobile page usability

Last tested: 2019-12-07


Mobile Usability Good
94/100

ird.govt.nz Mobile Usability Test Quick Summary


priority - 5 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="/how-to/irdnumbers?id=footer">IRD numbers</a> and 18 others are close to other tap targets.

ird.govt.nz similar domains

Similar domains:
www.ird.com
www.ird.net
www.ird.org
www.ird.info
www.ird.biz
www.ird.us
www.ird.mobi
www.rd.govt.nz
www.ird.govt.nz
www.urd.govt.nz
www.iurd.govt.nz
www.uird.govt.nz
www.jrd.govt.nz
www.ijrd.govt.nz
www.jird.govt.nz
www.krd.govt.nz
www.ikrd.govt.nz
www.kird.govt.nz
www.ord.govt.nz
www.iord.govt.nz
www.oird.govt.nz
www.id.govt.nz
www.ied.govt.nz
www.ired.govt.nz
www.ierd.govt.nz
www.idd.govt.nz
www.irdd.govt.nz
www.idrd.govt.nz
www.ifd.govt.nz
www.irfd.govt.nz
www.ifrd.govt.nz
www.itd.govt.nz
www.irtd.govt.nz
www.itrd.govt.nz
www.ir.govt.nz
www.irx.govt.nz
www.irdx.govt.nz
www.irxd.govt.nz
www.irs.govt.nz
www.irds.govt.nz
www.irsd.govt.nz
www.ire.govt.nz
www.irde.govt.nz
www.irr.govt.nz
www.irdr.govt.nz
www.irrd.govt.nz
www.irf.govt.nz
www.irdf.govt.nz
www.irc.govt.nz
www.irdc.govt.nz
www.ircd.govt.nz

ird.govt.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.


ird.govt.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.