15 sec in total
2.1 sec
11.6 sec
1.3 sec
Visit orly.co.nz now to see the best up-to-date Orly content and also check out these interesting facts you probably never knew about orly.co.nz
Video Production Christchurch, Wellington, Auckland, Orly | Leading NZ Video Production Company, 3D Animation Company Studio, Film production company, Explainer Video Producer, Best Videographer Chris...
Visit orly.co.nzWe analyzed Orly.co.nz page load time and found that the first response time was 2.1 sec and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
orly.co.nz performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value9.7 s
0/100
25%
Value20.3 s
0/100
10%
Value3,320 ms
2/100
30%
Value0.111
87/100
15%
Value17.4 s
4/100
10%
2115 ms
33 ms
48 ms
256 ms
730 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 16% of them (16 requests) were addressed to the original Orly.co.nz, 34% (34 requests) were made to Maps.googleapis.com and 33% (33 requests) were made to Assets.orly.co.nz. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source Assets.orly.co.nz.
Page size can be reduced by 1.0 MB (28%)
3.5 MB
2.5 MB
In fact, the total size of Orly.co.nz main page is 3.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 85.6 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 85.6 kB or 85% of the original size.
Potential reduce by 138.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. Orly images are well optimized though.
Potential reduce by 695.2 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 695.2 kB or 65% of the original size.
Potential reduce by 84.1 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. Orly.co.nz needs all CSS files to be minified and compressed as it can save up to 84.1 kB or 80% of the original size.
Number of requests can be reduced by 29 (31%)
93
64
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orly. 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 as a result speed up the page load time.
www.orly.co.nz
2115 ms
font-awesome.min.css
33 ms
rkv2ebo.js
48 ms
style.css
256 ms
modernizr-custom.min.js
730 ms
jquery.js
754 ms
jquery-migrate.min.js
519 ms
js
193 ms
page.js
75 ms
plugins.min.js
1011 ms
ScrollToPlugin.min.js
508 ms
isotope.pkgd.min.js
509 ms
init.js
747 ms
scripts.js
841 ms
wp-embed.min.js
840 ms
wp-emoji-release.min.js
899 ms
orly_header_home.jpg
5731 ms
logo.svg
277 ms
ntoggle.svg
278 ms
bar-top.png
276 ms
play-white.svg
275 ms
Orly_fashion-shoot-2016_3_BLURRED.jpg
5697 ms
Girl-on-hat_fashion_video-your-way_POSTER_921x385.jpg
5940 ms
orly_header_video.jpg
5942 ms
orly-promo_beer-tvc_BLURRED.jpg
5955 ms
orly-promo_beer-tvc.jpg
5963 ms
orly_header_commercials.jpg
5942 ms
commercials_bg.jpg
5952 ms
commercials_panel_tall_1.jpg
6188 ms
commercials_panel_tall_2.jpg
6190 ms
commercials_panel_tall_3.jpg
6191 ms
commercials_video_panel_wide.jpg
6194 ms
surface.png
6439 ms
berry1_2.png
6205 ms
berry3.png
6430 ms
berry4.png
6430 ms
berry5_8.png
6431 ms
berry6_7.png
6434 ms
orly_header_animation.jpg.jpg
6462 ms
Orly-wave.jpg
6673 ms
Orly-logo-in-water-ocean-animation_980x550.jpg
6908 ms
Animation-thumbnails_1_23062017A-1024x288.jpg
6676 ms
Animation-thumbnails_2_23062017A-1024x288.jpg
6679 ms
Animation-thumbnails_4_23062017A-1024x288.jpg
6684 ms
orly_header_interactive.jpg
6713 ms
Inspire-1-Pro_V1.jpg
7149 ms
THUMBNAIL-IMAGES_Work_1-1024x288.jpg
6914 ms
THUMBNAIL-IMAGES_Work_2-1024x288.jpg
6915 ms
THUMBNAIL-IMAGES_Work_3-1024x288.jpg
6962 ms
Client-logos-on-grey_1000px.jpg
6970 ms
orly_header_contact.jpg
7148 ms
orly_contact_top.jpg
7155 ms
orly_contact_bottom.jpg
7154 ms
fontawesome-webfont.woff
20 ms
common.js
7 ms
map.js
31 ms
util.js
67 ms
marker.js
66 ms
onion.js
27 ms
openhand_8_8.cur
99 ms
ViewportInfoService.GetViewportInfo
82 ms
controls.js
34 ms
infowindow.js
10 ms
css
85 ms
spotlight-poi.png
61 ms
transparent.png
62 ms
google_white5.png
57 ms
mapcnt6.png
155 ms
sv9.png
60 ms
vt
145 ms
vt
126 ms
vt
122 ms
vt
123 ms
vt
124 ms
vt
124 ms
vt
162 ms
vt
127 ms
vt
162 ms
vt
126 ms
vt
162 ms
vt
126 ms
vt
163 ms
vt
161 ms
vt
162 ms
vt
193 ms
vt
165 ms
vt
166 ms
vt
169 ms
vt
193 ms
vt
193 ms
vt
254 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
66 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
90 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
98 ms
d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff
98 ms
d
11 ms
d
37 ms
AuthenticationService.Authenticate
43 ms
p.gif
111 ms
stats.js
2 ms
QuotaService.RecordEvent
29 ms
orly.co.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
orly.co.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
Page has valid source maps
orly.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orly.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 Orly.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.
orly.co.nz
Open Graph data is detected on the main page of Orly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: