amp.co.nz website information.
amp.co.nz domain name is registered by .NZ top-level domain registry. See the other sites registred in .NZ domain zone.
No name server records were found.
and probably website amp.co.nz is hosted by RAKUTEN Rakuten,Inc., JP web hosting company. Check the complete list of other most popular websites hosted by RAKUTEN Rakuten,Inc., JP hosting company.
According to Alexa traffic rank the highest website amp.co.nz position was 22486 (in the world). The lowest Alexa rank position was 998830. Now website amp.co.nz ranked in Alexa database as number 772005 (in the world).
Website amp.co.nz Desktop speed measurement score (48/100) is better than the results of 21.82% of other sites shows that the page desktop performance can be improved.
amp.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 amp.co.nz (31/100) is better than the results of 10.59% 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-23-2024 | 772,005 | -7,121 |
| Sep-22-2024 | 764,884 | -8,729 |
| Sep-21-2024 | 756,155 | -8,927 |
| Sep-20-2024 | 747,228 | -8,808 |
| Sep-19-2024 | 738,420 | 21,847 |
| Sep-18-2024 | 760,267 | -22,241 |
| Sep-17-2024 | 738,026 | 61,517 |
Advertisement
amp.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.
amp.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-12-14T19:26:55+13:00
domain_name: amp.co.nz
query_status: 200 Active
domain_dateregistered: 1996-11-07T00:00:00+13:00
domain_datelastmodified: 2021-11-25T00:00:12+13:00
domain_datecreated: 1996-11-07T00:00:00+13:00
domain_delegaterequested: yes
domain_signed: no
%
registrar_name: Metaname
registrar_address1: PO Box 32133
registrar_city: Christchurch
registrar_province: Canterbury
registrar_postalcode: 8147
registrar_country: NZ (NEW ZEALAND)
registrar_phone: +64 800 00 12 93
registrar_email: support@metaname.co.nz
%
ns_name_01: ns1.metaname.net
ns_name_02: ns2.metaname.net
ns_name_03: ns3.metaname.net
%
% Additional information may be available at https://www.dnc.org.nz/whois/search?domain_name=amp.co.nz
%
amp.co.nz server information
Servers Location
| IP Address |
|---|
| Country |
|---|
amp.co.nz desktop page speed rank
Last tested: 2019-01-18
amp.co.nz Desktop Speed Test Quick Summary
priority - 84 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 822.8KiB (75% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/hhl…ce_homepage-banner.jpg could save 259.7KiB (72% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/nwf/amp-in-the-community.jpg could save 167.9KiB (76% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/nwf/amp-logo.jpg could save 121.5KiB (81% reduction).
Compressing https://d3f5l8ze0o4j2m.cloudfront.net/m87/close.png could save 3.1KiB (23% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/inl…womens-refuge-logo.png could save 1.5KiB (28% reduction).
priority - 21 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 204.2KiB (49% reduction).
Minifying https://www.amp.co.nz/etc/clientlibs/amp-libs.js could save 63.5KiB (50% reduction) after compression.
Minifying https://www.amp.co.nz/etc/clientlibs/global-libs/component-libs.js could save 12.4KiB (44% reduction) after compression.
Minifying https://www.amp.co.nz/content/dam/ampnz/assets/slick/slick.js could save 3.5KiB (26% reduction) after compression.
Minifying https://www.amp.co.nz/content/dam/ampnz/home-product/js/home-product2.js could save 921B (37% reduction) after compression.
Minifying https://connect.facebook.net/en_US/fbds.js could save 695B (34% reduction) after compression.
Minifying https://api.ipdata.co/?api-key=1a31485dfcd75b47274…5d9ba6ce95eee1ee785c30 could save 375B (33% reduction).
Minifying https://www.amp.co.nz/content/dam/ampnz/assets/car…p-carousel-homepage.js could save 272B (27% reduction) after compression.
Minifying https://www.amp.co.nz/content/dam/ampnz/assets/car…-homepage-enhanced1.js could save 110B (28% reduction) after compression.
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 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.
Optimize CSS Delivery of the following:
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://d3f5l8ze0o4j2m.cloudfront.net/m87/k33spt.js (expiration not specified)
https://www.googletagmanager.com/gtag/js?id=DC-3096901 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-MSRP2N (15 minutes)
https://connect.facebook.net/en_US/fbds.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/162877…6234?v=2.8.37&r=stable (20 minutes)
https://assets.adobedtm.com/2852c894343904db05de67…d77a14e5e7d67b04992.js (60 minutes)
https://assets.adobedtm.com/2852c894343904db05de67…6e1242148985e7873f8.js (60 minutes)
https://assets.adobedtm.com/2852c894343904db05de67…f7e64746d0b920057c5.js (60 minutes)
https://cdn.tt.omtrdc.net/cdn/target.js (60 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
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 5.9KiB (23% reduction).
Minifying https://www.amp.co.nz/etc/clientlibs/global-libs/component-libs.css could save 2.5KiB (25% reduction) after compression.
Minifying https://www.amp.co.nz/content/dam/ampnz/home-product/css/home-product.css could save 798B (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 2.7KiB (17% reduction).
Minifying https://3096901.fls.doubleclick.net/activityi;dc_p…2F%2Fwww.amp.co.nz%2F? could save 216B (20% reduction) after compression.
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 1KiB (55% reduction).
Compressing https://ampserviceslimited.tt.omtrdc.net/m2/ampser…o.nz%2F&mboxVersion=63 could save 347B (50% reduction).
amp.co.nz Desktop Resources
| Total Resources | 75 |
| Number of Hosts | 25 |
| Static Resources | 15 |
| JavaScript Resources | 32 |
| CSS Resources | 10 |
amp.co.nz Desktop Resource Breakdown
amp.co.nz mobile page speed rank
Last tested: 2019-01-18
amp.co.nz Mobile Speed Test Quick Summary
priority - 112 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 15 blocking script resources and 10 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://assets.adobedtm.com/2852c894343904db05de67…d77a14e5e7d67b04992.js
https://cdn.tt.omtrdc.net/cdn/target.js
https://assets.adobedtm.com/2852c894343904db05de67…6e1242148985e7873f8.js
https://assets.adobedtm.com/2852c894343904db05de67…d77a14e5e7d67b04992.js
https://cdn.tt.omtrdc.net/cdn/target.js
https://ampserviceslimited.tt.omtrdc.net/m2/ampser…o.nz%2F&mboxVersion=63
https://assets.adobedtm.com/2852c894343904db05de67…f7e64746d0b920057c5.js
https://www.amp.co.nz/etc/clientlibs/amp-libs.js
https://www.amp.co.nz/etc/clientlibs/global-libs/aem-libs.js
https://www.amp.co.nz/etc/clientlibs/global-libs/header-libs.js
https://ajax.googleapis.com/ajax/libs/jquery/2.1.0/jquery.min.js
https://www.amp.co.nz/etc/designs/amp/clientLibraries/swiftype-libs.js
https://www.amp.co.nz/content/dam/ampnz/assets/slick/slick.js
https://www.amp.co.nz/etc/clientlibs/global-libs/component-libs.js
Optimize CSS Delivery of the following:
https://fonts.googleapis.com/css?family=Open+Sans:…,600italic,400,300,600
https://cloud.typography.com/6591112/739504/css/fonts.css
https://fonts.googleapis.com/css?family=Open+Sans:…,600italic,400,300,600
https://www.amp.co.nz/etc/clientlibs/global-libs/icon-libs.css
https://www.amp.co.nz/etc/clientlibs/global-libs/header-libs.css
https://www.amp.co.nz/etc/designs/amp/clientLibraries/swiftype-libs.css
https://www.amp.co.nz/content/dam/ampnz/assets/slick/slick.css
https://www.amp.co.nz/etc/clientlibs/amp-libs.css
https://www.amp.co.nz/etc/clientlibs/global-libs/component-libs.css
priority - 95 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 929.2KiB (75% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/hhl…ce_homepage-banner.jpg could save 259.7KiB (72% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/nwf/amp-in-the-community.jpg could save 167.9KiB (76% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/nwf/amp-logo.jpg could save 121.5KiB (81% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/hhs…page-banner_mobile.jpg could save 54.5KiB (71% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/hhs…-out-banner_mobile.jpg could save 51.9KiB (78% reduction).
Compressing https://d3f5l8ze0o4j2m.cloudfront.net/m87/close.png could save 3.1KiB (23% reduction).
Compressing https://www.amp.co.nz/content/dam/ampnz/images/inl…womens-refuge-logo.png could save 1.5KiB (28% reduction).
priority - 21 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 204.2KiB (49% reduction).
Minifying https://www.amp.co.nz/etc/clientlibs/amp-libs.js could save 63.5KiB (50% reduction) after compression.
Minifying https://www.amp.co.nz/etc/clientlibs/global-libs/component-libs.js could save 12.4KiB (44% reduction) after compression.
Minifying https://www.amp.co.nz/content/dam/ampnz/assets/slick/slick.js could save 3.5KiB (26% reduction) after compression.
Minifying https://www.amp.co.nz/content/dam/ampnz/home-product/js/home-product2.js could save 921B (37% reduction) after compression.
Minifying https://connect.facebook.net/en_US/fbds.js could save 695B (34% reduction) after compression.
Minifying https://api.ipdata.co/?api-key=1a31485dfcd75b47274…5d9ba6ce95eee1ee785c30 could save 375B (33% reduction).
Minifying https://www.amp.co.nz/content/dam/ampnz/assets/car…p-carousel-homepage.js could save 272B (27% reduction) after compression.
Minifying https://www.amp.co.nz/content/dam/ampnz/assets/car…-homepage-enhanced1.js could save 110B (28% reduction) after compression.
priority - 9 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://www.googletagmanager.com/gtag/js?id=DC-3096901 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-MSRP2N (15 minutes)
https://connect.facebook.net/en_US/fbds.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/162877…6234?v=2.8.37&r=stable (20 minutes)
https://assets.adobedtm.com/2852c894343904db05de67…d77a14e5e7d67b04992.js (60 minutes)
https://assets.adobedtm.com/2852c894343904db05de67…6e1242148985e7873f8.js (60 minutes)
https://assets.adobedtm.com/2852c894343904db05de67…f7e64746d0b920057c5.js (60 minutes)
https://cdn.tt.omtrdc.net/cdn/target.js (60 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
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 5.9KiB (23% reduction).
Minifying https://www.amp.co.nz/etc/clientlibs/global-libs/component-libs.css could save 2.5KiB (25% reduction) after compression.
Minifying https://www.amp.co.nz/content/dam/ampnz/home-product/css/home-product.css could save 798B (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 2.7KiB (17% reduction).
Minifying https://3096901.fls.doubleclick.net/activityi;src=…2F%2Fwww.amp.co.nz%2F? could save 215B (21% reduction) after compression.
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 1KiB (55% reduction).
Compressing https://ampserviceslimited.tt.omtrdc.net/m2/ampser…o.nz%2F&mboxVersion=63 could save 347B (50% reduction).
amp.co.nz Mobile Resources
| Total Resources | 72 |
| Number of Hosts | 25 |
| Static Resources | 15 |
| JavaScript Resources | 31 |
| CSS Resources | 10 |
amp.co.nz Mobile Resource Breakdown
amp.co.nz mobile page usability
Last tested: 2019-01-18
amp.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.
<a href="#close" class="notif__close scrollTo"></a> is close to 1 other tap targets.The tap target
<a href="http://www.you…/AMPNewZealand">Youtube</a> and 3 others are close to other tap targets.<a href="#main" class="scrollTo back-to-top"></a> is close to 1 other tap targets.amp.co.nz similar domains
www.amp.net
www.amp.org
www.amp.info
www.amp.biz
www.amp.us
www.amp.mobi
www.mp.co.nz
www.amp.co.nz
www.qmp.co.nz
www.aqmp.co.nz
www.qamp.co.nz
www.wmp.co.nz
www.awmp.co.nz
www.wamp.co.nz
www.smp.co.nz
www.asmp.co.nz
www.samp.co.nz
www.zmp.co.nz
www.azmp.co.nz
www.zamp.co.nz
www.ap.co.nz
www.anp.co.nz
www.amnp.co.nz
www.anmp.co.nz
www.ajp.co.nz
www.amjp.co.nz
www.ajmp.co.nz
www.akp.co.nz
www.amkp.co.nz
www.akmp.co.nz
www.am.co.nz
www.amo.co.nz
www.ampo.co.nz
www.amop.co.nz
www.aml.co.nz
www.ampl.co.nz
www.amlp.co.nz
amp.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.
amp.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.