liturgy.co.nz Website Information
Daily Unique Visits: 2,626
Daily Page Views: 7,878
Income Per Day: $24
Estimated Value: $8,640
This website is located in Australia and is using following IP address 45.76.112.206. See the complete list of popular websites hosted in Australia.
liturgy.co.nz is registered under .NZ top-level domain. Please check other sites in .NZ zone.
Website liturgy.co.nz is using the following name servers:
- ns14.zoneedit.com
- ns7.zoneedit.com
and is probably hosted by AS-CHOOPA - Choopa, LLC, US. See the full list of other websites hosted by AS-CHOOPA - Choopa, LLC, US.
The highest website liturgy.co.nz position in Alexa rank database was 19375 and the lowest rank position was 998843. Current position of liturgy.co.nz in Alexa rank database is 409591.
Desktop speed score of liturgy.co.nz (70/100) is better than the results of 50.91% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of liturgy.co.nz (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.
Mobile speed score of liturgy.co.nz (72/100) is better than the results of 79.79% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
liturgy.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.
liturgy.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.
%
% 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-10T10:53:55+13:00
domain_name: liturgy.co.nz
query_status: 200 Active
domain_dateregistered: 2006-04-12T15:16:16+12:00
domain_datelastmodified: 2020-03-30T12:18:30+13:00
domain_datecreated: 2006-04-12T15:16:16+12:00
domain_delegaterequested: yes
domain_signed: no
%
registrar_name: 1st Domains
registrar_address1: P O Box 1520
registrar_address2: Christchurch Mail Centre
registrar_city: Christchurch
registrar_province: Canterbury
registrar_country: NZ (NEW ZEALAND)
registrar_phone: +64 3 962 9520
registrar_fax: +64 3 962 9513
registrar_email: hostmaster@1stdomains.net.nz
%
ns_name_01: ns7.zoneedit.com
ns_name_02: ns14.zoneedit.com
%
% Additional information may be available at https://www.dnc.org.nz/whois/search?domain_name=liturgy.co.nz
%
liturgy.co.nz server information
Servers Location
liturgy.co.nz desktop page speed rank
Last tested: 2019-06-30
liturgy.co.nz Desktop Speed Test Quick Summary
priority - 25Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 247.5KiB (76% reduction).
Compressing https://liturgy.co.nz/wp-content/uploads/2014/11/Liturgylogo.jpg could save 1.7KiB (34% reduction).
Compressing https://liturgy.co.nz/wp-content/uploads/2019/06/Collar-sml.jpg could save 604B (28% reduction).
Compressing https://liturgy.co.nz/wp-content/uploads/2019/06/Baryon-Sml.jpg could save 541B (22% reduction).
Compressing https://liturgy.co.nz/wp-content/uploads/2019/06/G…MarkKoineGreek-Sml.jpg could save 501B (22% reduction).
Compressing https://liturgy.co.nz/wp-content/uploads/2018/06/Matariki-Cluster-Sml.jpg could save 489B (21% reduction).
Compressing https://www.liturgy.co.nz/images/twit.gif could save 309B (17% reduction).
Compressing https://yt3.ggpht.com/-7_5g2jHrGX0/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 274B (24% reduction).
priority - 9Leverage 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://liturgy.co.nz/wp-content/uploads/2015/10/profile.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2018/06/Matariki-Cluster-Sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/Anthelm-Sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/Baryon-Sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/Collar-sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/Corpus-Christi-Sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/G…MarkKoineGreek-Sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/Peter-and-Paul-Sml.jpg (expiration not specified)
https://www.liturgy.co.nz/images/face.gif (expiration not specified)
https://www.liturgy.co.nz/images/rss.gif (expiration not specified)
https://www.liturgy.co.nz/images/twit.gif (expiration not specified)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://connect.facebook.net/en_GB/sdk.js (20 minutes)
https://cse.google.com/coop/cse/brand?form=cse-search-box&lang=en (30 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 9 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://liturgy.co.nz/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
https://liturgy.co.nz/wp-content/themes/headway/li…936af6105f7656b4df403e
https://liturgy.co.nz/wp-content/uploads/headway/c…936af6105f7656b4df403e
https://liturgy.co.nz/wp-content/plugins/google-an…ntend.min.js?ver=7.7.1
https://liturgy.co.nz/wp-content/plugins/add-to-any/addtoany.min.js?ver=1.1
https://liturgy.co.nz/wp-content/themes/headway/li…936af6105f7656b4df403e
https://liturgy.co.nz/wp-content/uploads/headway/c…936af6105f7656b4df403e
http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en
Optimize CSS Delivery of the following:
https://liturgy.co.nz/wp-content/uploads/headway/c…936af6105f7656b4df403e
https://liturgy.co.nz/wp-content/uploads/headway/c…936af6105f7656b4df403e
https://liturgy.co.nz/wp-content/uploads/headway/c…936af6105f7656b4df403e
https://liturgy.co.nz/wp-includes/css/dist/block-l…936af6105f7656b4df403e
https://liturgy.co.nz/wp-content/plugins/tablepres…ault.min.css?ver=1.9.2
https://liturgy.co.nz/wp-content/plugins/add-to-an…toany.min.css?ver=1.15
priority - 0Minify 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.6KiB (37% reduction).
Minifying https://liturgy.co.nz/wp-content/themes/headway/li…936af6105f7656b4df403e could save 592B (39% reduction) after compression.
Minifying https://liturgy.co.nz/wp-content/themes/headway/li…936af6105f7656b4df403e could save 379B (32% reduction) after compression.
liturgy.co.nz Desktop Resource Breakdown
Total Resources | 71 |
Number of Hosts | 19 |
Static Resources | 31 |
JavaScript Resources | 27 |
CSS Resources | 8 |
liturgy.co.nz mobile page speed rank
Last tested: 2019-06-28
liturgy.co.nz Mobile Speed Test Quick Summary
priority - 32Eliminate 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.
Optimize CSS Delivery of the following:
priority - 6Leverage 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://liturgy.co.nz/wp-content/uploads/2019/06/Anthelm-Sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/Baryon-Sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/Collar-sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/uploads/2019/06/Peter-and-Paul-Sml.jpg (expiration not specified)
https://liturgy.co.nz/wp-content/wptouch-data/cach…47eb0dc849b5373ffee.js (expiration not specified)
https://connect.facebook.net/en_GB/sdk.js (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1.6KiB (24% reduction).
Compressing https://liturgy.co.nz/wp-content/uploads/2019/06/Baryon-Sml.jpg could save 541B (22% reduction).
Compressing https://liturgy.co.nz/wp-content/uploads/2018/06/Matariki-Cluster-Sml.jpg could save 489B (21% reduction).
priority - 0Minify 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 855B (11% reduction).
priority - 0Minify 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 674B (39% reduction).
liturgy.co.nz Mobile Resource Breakdown
Total Resources | 26 |
Number of Hosts | 6 |
Static Resources | 10 |
JavaScript Resources | 9 |
CSS Resources | 6 |
liturgy.co.nz mobile page usability
Last tested: 2019-06-28
liturgy.co.nz HTML validation
Errors
Bad value “//fonts.googleapis.com/css?family=Bree+Serif|Open+Sans” for attribute “href” on element “link”: Illegal character in query: “|” is not allowed.
"...heets --> <link rel='stylesheet' id='headway-google-fonts' href='//fonts.googleapis.com/css?family=Bree+Serif|Open+Sans' type='text/css' media='all' /> <st..."
Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.
"...jpg" /> <link rel='https://api.w.org/' href='http://liturgy.co.nz/wp-json/' /> <link..."
Bad start tag in “div” in “head”.
"...<noscript><div class="statcounter"><a tit..."
Stray end tag “noscript”.
"...</a></div></noscript> <!-..."
A “link” element must not appear as a descendant of a “body” element unless the “link” element has an “itemprop” attribute or has a “rel” attribute whose value contains “dns-prefetch”, “pingback”, “preconnect”, “prefetch”, “preload”, “prerender”, or “stylesheet”.
"... </script><link rel="shortcut icon" href="/wp-content/uploads/fbrfg/favicon.ico"> <link..." Line: 209 Column: 1 - 103
"...con.ico"> <link rel="apple-touch-icon" sizes="57x57" href="/wp-content/uploads/fbrfg/apple-touch-icon-57x57.png"> <link..." Line: 210 Column: 1 - 107
"...x57.png"> <link rel="apple-touch-icon" sizes="114x114" href="/wp-content/uploads/fbrfg/apple-touch-icon-114x114.png"> <link..." Line: 211 Column: 1 - 103
"...114.png"> <link rel="apple-touch-icon" sizes="72x72" href="/wp-content/uploads/fbrfg/apple-touch-icon-72x72.png"> <link..." Line: 212 Column: 1 - 107
"...x72.png"> <link rel="apple-touch-icon" sizes="144x144" href="/wp-content/uploads/fbrfg/apple-touch-icon-144x144.png"> <link..." Line: 213 Column: 1 - 103
"...144.png"> <link rel="apple-touch-icon" sizes="60x60" href="/wp-content/uploads/fbrfg/apple-touch-icon-60x60.png"> <link..." Line: 214 Column: 1 - 107
"...x60.png"> <link rel="apple-touch-icon" sizes="120x120" href="/wp-content/uploads/fbrfg/apple-touch-icon-120x120.png"> <link..." Line: 215 Column: 1 - 103
"...120.png"> <link rel="apple-touch-icon" sizes="76x76" href="/wp-content/uploads/fbrfg/apple-touch-icon-76x76.png"> <link..." Line: 216 Column: 1 - 107
"...x76.png"> <link rel="apple-touch-icon" sizes="152x152" href="/wp-content/uploads/fbrfg/apple-touch-icon-152x152.png"> <link..." Line: 217 Column: 1 - 107
"...152.png"> <link rel="apple-touch-icon" sizes="180x180" href="/wp-content/uploads/fbrfg/apple-touch-icon-180x180.png"> <link..." Line: 218 Column: 1 - 103
"...180.png"> <link rel="icon" type="image/png" href="/wp-content/uploads/fbrfg/favicon-192x192.png" sizes="192x192"> <link..." Line: 219 Column: 1 - 103
"...192x192"> <link rel="icon" type="image/png" href="/wp-content/uploads/fbrfg/favicon-160x160.png" sizes="160x160"> <link..." Line: 220 Column: 1 - 99
"...160x160"> <link rel="icon" type="image/png" href="/wp-content/uploads/fbrfg/favicon-96x96.png" sizes="96x96"> <link..." Line: 221 Column: 1 - 99
"...="96x96"> <link rel="icon" type="image/png" href="/wp-content/uploads/fbrfg/favicon-16x16.png" sizes="16x16"> <link..." Line: 222 Column: 1 - 99
"...="16x16"> <link rel="icon" type="image/png" href="/wp-content/uploads/fbrfg/favicon-32x32.png" sizes="32x32"> <meta..." Line: 228 Column: 3 - 108
".../style> <link rel="icon" href="http://liturgy.co.nz/wp-content/uploads/2014/11/cropped-logo3.jpg" sizes="32x32" /> <link..." Line: 229 Column: 1 - 108
"...32x32" /> <link rel="icon" href="http://liturgy.co.nz/wp-content/uploads/2014/11/cropped-logo3.jpg" sizes="192x192" /> <link..." Line: 230 Column: 1 - 116
"...2x192" /> <link rel="apple-touch-icon-precomposed" href="http://liturgy.co.nz/wp-content/uploads/2014/11/cropped-logo3.jpg" /> <meta..."
Attribute “name” not allowed on element “meta” at this point.
"...="32x32"> <meta name="msapplication-TileColor" content="#99cc33"> <meta..." Line: 224 Column: 1 - 92
"...#99cc33"> <meta name="msapplication-TileImage" content="/wp-content/uploads/fbrfg/mstile-144x144.png"> <meta..." Line: 225 Column: 1 - 88
"...144.png"> <meta name="msapplication-config" content="/wp-content/uploads/fbrfg/browserconfig.xml"><style..." Line: 231 Column: 1 - 115
"...3.jpg" /> <meta name="msapplication-TileImage" content="http://liturgy.co.nz/wp-content/uploads/2014/11/cropped-logo3.jpg" /> <styl..."
Element “meta” is missing one or more of the following attributes: “itemprop”, “property”.
"...="32x32"> <meta name="msapplication-TileColor" content="#99cc33"> <meta..." Line: 224 Column: 1 - 92
"...#99cc33"> <meta name="msapplication-TileImage" content="/wp-content/uploads/fbrfg/mstile-144x144.png"> <meta..." Line: 225 Column: 1 - 88
"...144.png"> <meta name="msapplication-config" content="/wp-content/uploads/fbrfg/browserconfig.xml"><style..." Line: 231 Column: 1 - 115
"...3.jpg" /> <meta name="msapplication-TileImage" content="http://liturgy.co.nz/wp-content/uploads/2014/11/cropped-logo3.jpg" /> <styl..."
Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)
"...nfig.xml"><style data-context="foundation-flickity-css">/*! Fl..." Line: 227 Column: 1816 - 1861
"...1}</style><style data-context="foundation-slideout-css">.slide..." Line: 227 Column: 2278 - 2300
"...</style> <style type="text/css">.recen..." Line: 232 Column: 1 - 7
"...3.jpg" /> <style>.ios7...."
Stray end tag “head”.
"...}</style> </head> <bod..."
Start tag “body” seen but an element of the same type was already open.
"... </head> <body class="home blog custom firefox gecko responsive-grid-enabled responsive-grid-active layout-index layout-using-index" itemscope itemtype="http://schema.org/WebPage"> <di..."
Cannot recover after last error. Any further errors will be ignored.
"... </head> <body class="home blog custom firefox gecko responsive-grid-enabled responsive-grid-active layout-index layout-using-index" itemscope itemtype="http://schema.org/WebPage"> <di..."
Warnings
Consider avoiding viewport values that prevent users from resizing documents.
"....php" /> <meta name="viewport" content="width=device-width, minimum-scale=1.0, maximum-scale=1.0" /> <link..."
liturgy.co.nz similar domains
www.liturgy.net
www.liturgy.org
www.liturgy.info
www.liturgy.biz
www.liturgy.us
www.liturgy.mobi
www.iturgy.co.nz
www.liturgy.co.nz
www.piturgy.co.nz
www.lpiturgy.co.nz
www.pliturgy.co.nz
www.oiturgy.co.nz
www.loiturgy.co.nz
www.oliturgy.co.nz
www.kiturgy.co.nz
www.lkiturgy.co.nz
www.kliturgy.co.nz
www.lturgy.co.nz
www.luturgy.co.nz
www.liuturgy.co.nz
www.luiturgy.co.nz
www.ljturgy.co.nz
www.lijturgy.co.nz
www.ljiturgy.co.nz
www.lkturgy.co.nz
www.likturgy.co.nz
www.loturgy.co.nz
www.lioturgy.co.nz
www.liurgy.co.nz
www.lirurgy.co.nz
www.litrurgy.co.nz
www.lirturgy.co.nz
www.lifurgy.co.nz
www.litfurgy.co.nz
www.lifturgy.co.nz
www.ligurgy.co.nz
www.litgurgy.co.nz
www.ligturgy.co.nz
www.liyurgy.co.nz
www.lityurgy.co.nz
www.liyturgy.co.nz
www.litrgy.co.nz
www.lityrgy.co.nz
www.lituyrgy.co.nz
www.lithrgy.co.nz
www.lituhrgy.co.nz
www.lithurgy.co.nz
www.litjrgy.co.nz
www.litujrgy.co.nz
www.litjurgy.co.nz
www.litirgy.co.nz
www.lituirgy.co.nz
www.litiurgy.co.nz
www.litugy.co.nz
www.lituegy.co.nz
www.lituregy.co.nz
www.lituergy.co.nz
www.litudgy.co.nz
www.liturdgy.co.nz
www.litudrgy.co.nz
www.litufgy.co.nz
www.liturfgy.co.nz
www.litufrgy.co.nz
www.litutgy.co.nz
www.liturtgy.co.nz
www.litutrgy.co.nz
www.litury.co.nz
www.liturfy.co.nz
www.liturgfy.co.nz
www.liturvy.co.nz
www.liturgvy.co.nz
www.liturvgy.co.nz
www.liturty.co.nz
www.liturgty.co.nz
www.liturby.co.nz
www.liturgby.co.nz
www.liturbgy.co.nz
www.lituryy.co.nz
www.liturgyy.co.nz
www.liturygy.co.nz
www.liturhy.co.nz
www.liturghy.co.nz
www.liturhgy.co.nz
www.liturg.co.nz
www.liturgt.co.nz
www.liturgyt.co.nz
www.liturgg.co.nz
www.liturgyg.co.nz
www.liturggy.co.nz
www.liturgh.co.nz
www.liturgyh.co.nz
www.liturgu.co.nz
www.liturgyu.co.nz
www.liturguy.co.nz
liturgy.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.
liturgy.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.