iticket.co.nz website information.
iticket.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 iticket.co.nz domain:
- ns14.dnsmadeeasy.com
- ns12.dnsmadeeasy.com
- ns11.dnsmadeeasy.com
- ns10.dnsmadeeasy.com
- ns13.dnsmadeeasy.com
- ns15.dnsmadeeasy.com
and probably website iticket.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 iticket.co.nz position was 83569 (in the world). The lowest Alexa rank position was 999968. Now website iticket.co.nz ranked in Alexa database as number 342666 (in the world).
Website iticket.co.nz Desktop speed measurement score (70/100) is better than the results of 50.91% of other sites shows that the page desktop performance can be improved.
iticket.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 iticket.co.nz (56/100) is better than the results of 45.93% 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-26-2024 | 342,666 | -6,394 |
Nov-25-2024 | 336,272 | 14,901 |
Nov-24-2024 | 351,173 | -9,926 |
Nov-23-2024 | 341,247 | 2,773 |
Nov-22-2024 | 344,020 | 451 |
Nov-21-2024 | 344,471 | -3,724 |
Nov-20-2024 | 340,747 | -1,047 |
Advertisement
iticket.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.
iticket.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-16T23:08:14+13:00
domain_name: iticket.co.nz
query_status: 200 Active
domain_dateregistered: 2003-09-04T10:51:53+12:00
domain_datelastmodified: 2021-09-12T13:24:16+12:00
domain_datecreated: 2003-09-04T10:51:53+12:00
domain_delegaterequested: yes
domain_signed: no
%
registrar_name: Dreamscape Networks International Pte Ltd T/A Crazy Domains
registrar_address1: 3 Irving Road, #09-01 Tai Seng Centre,
registrar_city: Singapore
registrar_province: Dubai
registrar_postalcode: 369522
registrar_country: SG (SINGAPORE)
registrar_phone: +65 6914788
registrar_fax: +61 894220801
registrar_email: registry@dreamscapenetworks.com
%
ns_name_01: ns10.dnsmadeeasy.com
ns_name_02: ns11.dnsmadeeasy.com
ns_name_03: ns12.dnsmadeeasy.com
ns_name_04: ns13.dnsmadeeasy.com
%
% Additional information may be available at https://www.dnc.org.nz/whois/search?domain_name=iticket.co.nz
%
iticket.co.nz server information
Servers Location
IP Address |
---|
96.45.82.2 |
96.45.83.41 |
96.45.82.243 |
96.45.83.168 |
iticket.co.nz desktop page speed rank
Last tested: 2015-09-13
iticket.co.nz Desktop Speed Test Quick Summary
priority - 12 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://az280491.vo.msecnd.net/backgrounds/repeater_grey.png (expiration not specified)
https://az280491.vo.msecnd.net/events/7874/7874_210_245.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/7874/7874_400_200.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8156/8156_210_245.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8156/8156_400_200.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8175/8175_210_245.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8175/8175_400_200.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8197/8197_210_245.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8197/8197_400_200.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8224/8224_210_245.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8224/8224_400_200.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8246/8246_210_245.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8246/8246_400_200.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8315/8315_210_245.jpg (expiration not specified)
https://az280491.vo.msecnd.net/events/8315/8315_400_200.jpg (expiration not specified)
https://az280491.vo.msecnd.net/themes/iticket/images/100kiwi.png (expiration not specified)
https://static.hotjar.com/c/hotjar-54620.js?sv=5 (60 seconds)
https://www.googletagmanager.com/gtm.js?id=GTM-5Z9JT8 (15.3 minutes)
https://connect.facebook.net/en_US/all.js (20 minutes)
https://connect.facebook.net/en_US/fbds.js (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://script.crazyegg.com/pages/scripts/0036/7850.js?400593 (60 minutes)
https://www.google-analytics.com/plugins/ua/ecommerce.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 12 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 8 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.iticket.co.nz/assets/libs/modernizr/modernizr.js
Optimize CSS Delivery of the following:
https://www.iticket.co.nz/assets/fonts/fonts-refresh.css
https://www.iticket.co.nz/assets/fonts/fontello/css/animation.css
https://www.iticket.co.nz/assets/fonts/awesome/css/font-awesome.css
https://www.iticket.co.nz/assets/fonts/fontello/css/fontello-codes.css
https://www.iticket.co.nz/assets/fonts/fontello/css/fontello.css
https://www.iticket.co.nz/cassette.axd/stylesheet/…/assets/themes/iticket
https://az280491.vo.msecnd.net/css/background_home.css?v=3
priority - 7 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.iticket.co.nz/
https://www.iticket.co.nz/
priority - 4 Reduce server response time
In our test, your server responded in 0.40 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 - 4 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 35.5KiB (78% reduction).
Compressing https://script.crazyegg.com/pages/scripts/0036/7850.js?400593 could save 4.7KiB (59% reduction).
Compressing https://az280491.vo.msecnd.net/files/status.js?bust=20150913-0904 could save 2.1KiB (63% reduction).
priority - 2 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 16.5KiB (15% reduction).
Minifying https://fbstatic-a.akamaihd.net/rsrc.php/v2/yD/r/8wzTZDWntz9.js could save 1.1KiB (2% reduction) after compression.
Minifying https://az280491.vo.msecnd.net/files/status.js?bust=20150913-0904 could save 1.1KiB (33% reduction).
Minifying https://www.iticket.co.nz/assets/js/global.js?bust=20150817.0928 could save 768B (37% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20150817.0928 could save 732B (37% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20150817.0928 could save 706B (44% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20150817.0928 could save 682B (35% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20150817.0928 could save 647B (40% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20150817.0928 could save 628B (46% reduction) after compression.
priority - 1 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 9.8KiB (27% reduction).
Losslessly compressing https://az280491.vo.msecnd.net/themes/iticket/images/100kiwi.png could save 2.7KiB (23% reduction).
Losslessly compressing https://www.iticket.co.nz/cassette.axd/file/assets…0c56c6a0e38dfc76a7.png could save 1.1KiB (16% reduction).
Losslessly compressing https://www.iticket.co.nz/cassette.axd/file/assets…a2bbc06c107a8a6673.png could save 1.1KiB (13% reduction).
Losslessly compressing https://www.iticket.co.nz/cassette.axd/file/assets…5da7e75d174c1eeb42.png could save 667B (26% reduction).
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 8.2KiB (33% reduction).
Minifying https://www.iticket.co.nz/assets/fonts/fontello/css/fontello-codes.css could save 3.4KiB (33% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/fonts/awesome/css/font-awesome.css could save 1,006B (33% 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 793B (10% reduction).
iticket.co.nz Desktop Resources
Total Resources | 99 |
Number of Hosts | 17 |
Static Resources | 72 |
JavaScript Resources | 39 |
CSS Resources | 8 |
iticket.co.nz Desktop Resource Breakdown
iticket.co.nz mobile page speed rank
Last tested: 2019-06-25
iticket.co.nz Mobile Speed Test Quick Summary
priority - 64 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 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://www.iticket.co.nz/assets/libs/modernizr/modernizr.js
Optimize CSS Delivery of the following:
https://fonts.googleapis.com/css?family=Montserrat:400,400i,700,700i
https://www.iticket.co.nz/cassette.axd/stylesheet/…ac/assets/themes/fonts
https://www.iticket.co.nz/assets/fonts/fonts-refresh.css
https://www.iticket.co.nz/assets/fonts/fontello/css/animation.css
https://www.iticket.co.nz/assets/fonts/awesome/css/font-awesome.css
https://www.iticket.co.nz/assets/fonts/fontello/css/fontello-codes.css
https://www.iticket.co.nz/assets/fonts/fontello/css/fontello.css
https://www.iticket.co.nz/cassette.axd/stylesheet/…/assets/themes/iticket
https://iticket.imgix.net/css/background_home.css?v=3
priority - 8 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 81.1KiB (68% reduction).
Compressing https://platform.twitter.com/widgets/widget_iframe…2F%2Fwww.iticket.co.nz could save 9.2KiB (61% reduction).
Compressing https://platform.twitter.com/js/button.509719336ca39171c37a321231ccaf83.js could save 4.5KiB (66% reduction).
Compressing https://az280491.vo.msecnd.net/files/status.js?bust=20190625-0616 could save 1.8KiB (60% reduction).
priority - 7 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://syndication.twitter.com/settings (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-5Z9JT8 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/en_US/sdk.js (20 minutes)
https://connect.facebook.net/signals/config/749572…1662?v=2.8.51&r=stable (20 minutes)
https://connect.facebook.net/signals/plugins/inferredEvents.js?v=2.8.51 (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 2 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 21.1KiB (45% reduction).
Minifying https://www.iticket.co.nz/assets/libs/angular/sani….js?bust=20190618.0754 could save 2.8KiB (52% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20190618.0754 could save 732B (37% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20190618.0754 could save 706B (44% reduction) after compression.
Minifying https://az280491.vo.msecnd.net/files/status.js?bust=20190625-0616 could save 685B (23% reduction).
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20190618.0754 could save 682B (35% reduction) after compression.
Minifying https://connect.facebook.net/en_US/sdk.js could save 672B (39% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20190618.0754 could save 647B (40% reduction) after compression.
Minifying https://connect.facebook.net/signals/plugins/inferredEvents.js?v=2.8.51 could save 646B (85% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20190618.0754 could save 628B (46% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/libs/bootstrap/js….js?bust=20190618.0754 could save 503B (66% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/js/global.js?bust=20190618.0754 could save 351B (22% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/polyfills/Array.shim.js?bust=20190618.0754 could save 316B (28% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/dist/Common/pubsub.js?bust=20190618.0754 could save 296B (28% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/dist/AccountBar/app.js?bust=20190618.0754 could save 269B (17% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/dist/Common/data.js?bust=20190618.0754 could save 266B (17% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/dist/Search/app.js?bust=20190618.0754 could save 264B (13% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/dist/GlobalEvents.js?bust=20190618.0754 could save 201B (49% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/dist/EventCalenda….js?bust=20190618.0754 could save 193B (20% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/dist/Common/logging.js?bust=20190618.0754 could save 147B (20% reduction) after compression.
Minifying https://www.iticket.co.nz/cassette.axd/script/17d7…urefill/picturefill.js could save 117B (23% reduction) after compression.
priority - 1 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 13.7KiB (16% reduction).
Compressing https://iticket.imgix.net/events/24833/24833_210_245.jpg?v=1 could save 3.5KiB (13% reduction).
Compressing https://www.iticket.co.nz/cassette.axd/file/assets…f1323b63f9d267bbb1.png could save 3.5KiB (51% reduction).
Compressing https://iticket.imgix.net/events/16325/16325_210_245.jpg?v=1 could save 2.5KiB (11% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y5/r/OqOE21UvWe3.png could save 201B (50% reduction).
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 8.9KiB (32% reduction).
Minifying https://www.iticket.co.nz/assets/fonts/fontello/css/fontello-codes.css could save 3.3KiB (33% reduction) after compression.
Minifying https://www.iticket.co.nz/assets/fonts/awesome/css/font-awesome.css could save 1,006B (33% reduction) after compression.
Minifying https://unpkg.com/leaflet@1.3.1/dist/leaflet.css could save 672B (21% 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,009B (11% reduction).
iticket.co.nz Mobile Resources
Total Resources | 102 |
Number of Hosts | 21 |
Static Resources | 81 |
JavaScript Resources | 49 |
CSS Resources | 11 |
iticket.co.nz Mobile Resource Breakdown
iticket.co.nz mobile page usability
Last tested: 2019-06-25
iticket.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>x</a>
is close to 2 other tap targets.<a href="https://passphere.com/merger" class="pull-right btn ribbon-button">LEARN MORE</a>
is close to 2 other tap targets.<a href="#" class="btn btn-small…ropdown-toggle">0</a>
is close to 1 other tap targets.The tap target
<a href="https://boxoff…iticket.co.nz/">Promoter Boxoffice</a>
is close to 1 other tap targets.The tap target
<a href="/home/terms-and-conditions">TERMS & CONDITIONS</a>
is close to 1 other tap targets.iticket.co.nz similar domains
www.iticket.net
www.iticket.org
www.iticket.info
www.iticket.biz
www.iticket.us
www.iticket.mobi
www.ticket.co.nz
www.iticket.co.nz
www.uticket.co.nz
www.iuticket.co.nz
www.uiticket.co.nz
www.jticket.co.nz
www.ijticket.co.nz
www.jiticket.co.nz
www.kticket.co.nz
www.ikticket.co.nz
www.kiticket.co.nz
www.oticket.co.nz
www.ioticket.co.nz
www.oiticket.co.nz
www.iicket.co.nz
www.iricket.co.nz
www.itricket.co.nz
www.irticket.co.nz
www.ificket.co.nz
www.itficket.co.nz
www.ifticket.co.nz
www.igicket.co.nz
www.itgicket.co.nz
www.igticket.co.nz
www.iyicket.co.nz
www.ityicket.co.nz
www.iyticket.co.nz
www.itcket.co.nz
www.itucket.co.nz
www.itiucket.co.nz
www.ituicket.co.nz
www.itjcket.co.nz
www.itijcket.co.nz
www.itjicket.co.nz
www.itkcket.co.nz
www.itikcket.co.nz
www.itkicket.co.nz
www.itocket.co.nz
www.itiocket.co.nz
www.itoicket.co.nz
www.itiket.co.nz
www.itixket.co.nz
www.iticxket.co.nz
www.itixcket.co.nz
www.itidket.co.nz
www.iticdket.co.nz
www.itidcket.co.nz
www.itifket.co.nz
www.iticfket.co.nz
www.itifcket.co.nz
www.itivket.co.nz
www.iticvket.co.nz
www.itivcket.co.nz
www.iticet.co.nz
www.iticjet.co.nz
www.itickjet.co.nz
www.iticjket.co.nz
www.iticiet.co.nz
www.itickiet.co.nz
www.iticiket.co.nz
www.iticmet.co.nz
www.itickmet.co.nz
www.iticmket.co.nz
www.iticlet.co.nz
www.iticklet.co.nz
www.iticlket.co.nz
www.iticoet.co.nz
www.itickoet.co.nz
www.iticoket.co.nz
www.itickt.co.nz
www.itickwt.co.nz
www.itickewt.co.nz
www.itickwet.co.nz
www.itickst.co.nz
www.itickest.co.nz
www.itickset.co.nz
www.itickdt.co.nz
www.itickedt.co.nz
www.itickdet.co.nz
www.itickrt.co.nz
www.itickert.co.nz
www.itickret.co.nz
www.iticke.co.nz
www.iticker.co.nz
www.iticketr.co.nz
www.itickef.co.nz
www.iticketf.co.nz
www.itickeft.co.nz
www.itickeg.co.nz
www.iticketg.co.nz
www.itickegt.co.nz
www.itickey.co.nz
www.itickety.co.nz
www.itickeyt.co.nz
iticket.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.
iticket.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.