8.1 sec in total
1.2 sec
6.6 sec
236 ms
Visit ora.co.nz now to see the best up-to-date Ora content and also check out these interesting facts you probably never knew about ora.co.nz
A Gift from our land to you.
Visit ora.co.nzWe analyzed Ora.co.nz page load time and found that the first response time was 1.2 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ora.co.nz performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value8.9 s
1/100
25%
Value6.5 s
38/100
10%
Value1,150 ms
22/100
30%
Value0.068
96/100
15%
Value10.9 s
21/100
10%
1235 ms
224 ms
433 ms
433 ms
441 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 88% of them (66 requests) were addressed to the original Ora.co.nz, 3% (2 requests) were made to Apis.google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ora.co.nz.
Page size can be reduced by 496.1 kB (37%)
1.3 MB
827.1 kB
In fact, the total size of Ora.co.nz main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 670.1 kB which makes up the majority of the site volume.
Potential reduce by 25.0 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 4.2 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.0 kB or 77% of the original size.
Potential reduce by 1.2 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Ora images are well optimized though.
Potential reduce by 416.4 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 416.4 kB or 75% of the original size.
Potential reduce by 53.4 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Ora.co.nz needs all CSS files to be minified and compressed as it can save up to 53.4 kB or 79% of the original size.
Number of requests can be reduced by 51 (69%)
74
23
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.ora.co.nz
1235 ms
widgets.css
224 ms
html5.reset.css
433 ms
ora.content.css
433 ms
ora.layout.css
441 ms
ora.generic.css
442 ms
ora.category.css
443 ms
ora.product.css
444 ms
ora.gift.css
644 ms
ora.cart.css
645 ms
ora.wishlist.css
648 ms
ora.form.css
649 ms
ora.wheretobuy.css
652 ms
ora.media.css
658 ms
ora.account.css
856 ms
ora.blog.css
856 ms
ora.tooltip.css
862 ms
ora.lightbox.css
861 ms
j2t_autoadd.css
885 ms
jquery.fancybox.css
885 ms
prototype.js
1508 ms
ccard.js
1067 ms
validation.js
1075 ms
builder.js
1073 ms
effects.js
1104 ms
dragdrop.js
1104 ms
controls.js
1495 ms
slider.js
1290 ms
js.js
1289 ms
form.js
1321 ms
menu.js
1329 ms
translate.js
1501 ms
cookies.js
1543 ms
jquery-1.7.min.js
1766 ms
jquery.cycle.all-2.99.js
1547 ms
jquery.simpletip-1.3.1.pack.js
2420 ms
all.js
11 ms
widgets.js
128 ms
plusone.js
32 ms
ora.js
1715 ms
ora.backgrounds.js
1512 ms
ora.product.js
1298 ms
jquery.fancybox.pack.js
1340 ms
cb=gapi.loaded_0
86 ms
slide-dark1.jpg
889 ms
slide-dark2.jpg
883 ms
slide-dark3.jpg
649 ms
slide-dark4.jpg
1521 ms
slide-light3.jpg
645 ms
slide-light1.jpg
1697 ms
slide-light2.jpg
1066 ms
promo-spa.jpg
859 ms
promo-pamper.jpg
1074 ms
promo-revival.jpg
1088 ms
video.jpg
1095 ms
238 ms
ga.js
59 ms
Logo.png
1261 ms
Button.png
1269 ms
Dotted.png
1287 ms
ReadMore.png
1294 ms
xd_arbiter.php
212 ms
xd_arbiter.php
226 ms
input-green.png
1423 ms
btn-white.png
1433 ms
Facebook.png
1454 ms
Twitter.png
1463 ms
Payment.png
1636 ms
OraBrand-Book.woff
1835 ms
OraBrand-Semibold.woff
1845 ms
OraBrand-Light.woff
1864 ms
__utm.gif
21 ms
Dotted-40.png
1515 ms
slide-pager.png
1675 ms
print.css
221 ms
ora.co.nz accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
ora.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ora.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ora.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ora.co.nz main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
ora.co.nz
Open Graph description is not detected on the main page of Ora. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: