4.3 sec in total
599 ms
3.5 sec
199 ms
Welcome to orl.org.nz homepage info - get ready to check Orl best content right away, or after learning these important things about orl.org.nz
Visit orl.org.nzWe analyzed Orl.org.nz page load time and found that the first response time was 599 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
orl.org.nz performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value8.5 s
1/100
25%
Value5.8 s
49/100
10%
Value490 ms
59/100
30%
Value0.223
56/100
15%
Value7.8 s
44/100
10%
599 ms
759 ms
194 ms
385 ms
582 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 95% of them (42 requests) were addressed to the original Orl.org.nz, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Orl.org.nz.
Page size can be reduced by 151.6 kB (47%)
324.0 kB
172.4 kB
In fact, the total size of Orl.org.nz main page is 324.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 150.3 kB which makes up the majority of the site volume.
Potential reduce by 8.7 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 1.4 kB, which is 11% 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 8.7 kB or 70% of the original size.
Potential reduce by 12.0 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. Orl images are well optimized though.
Potential reduce by 100.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 100.4 kB or 67% of the original size.
Potential reduce by 30.6 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. Orl.org.nz needs all CSS files to be minified and compressed as it can save up to 30.6 kB or 81% of the original size.
Number of requests can be reduced by 29 (69%)
42
13
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
orl.org.nz
599 ms
www.orl.org.nz
759 ms
screen.css
194 ms
formcheck.css
385 ms
mootools-1.2.js
582 ms
en.js
385 ms
formcheck.js
391 ms
qscroller.js
393 ms
reset.css
201 ms
master.css
384 ms
btn_login.gif
197 ms
bg_header.gif
195 ms
tab_rgt_memberlogin.gif
198 ms
tab_lft_memberlogin.gif
198 ms
logo_nzsohns.gif
196 ms
bg_search.gif
193 ms
btn_search_magnify.gif
384 ms
bg_nav_selected.gif
387 ms
bg_home_mid.gif
386 ms
showimage.php
809 ms
bg_featureimage_punch.png
387 ms
welcome_arrow.gif
387 ms
bg_mid_light.gif
575 ms
bg_tri_mid_light.gif
576 ms
dots_white.gif
579 ms
bg_main.gif
580 ms
bg_main_divider.gif
579 ms
icn_rss.gif
764 ms
bg_hd_latestnews.gif
767 ms
dots_content.gif
770 ms
bg_widget_skyblue.gif
773 ms
bullet_more_skyblue.gif
773 ms
widget_punch.png
955 ms
bg_widget_lightblue.gif
957 ms
bullet_more_lightblue.gif
970 ms
bg_sidebar_gradient.gif
971 ms
showimage.php
1359 ms
showimage.php
1028 ms
banner_sponsors.gif
1146 ms
bg_footer.gif
1147 ms
siteby72dpi.gif
1161 ms
ga.js
8 ms
__utm.gif
26 ms
print.css
194 ms
orl.org.nz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
orl.org.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
orl.org.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orl.org.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Orl.org.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.
orl.org.nz
Open Graph description is not detected on the main page of Orl. 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: