1.7 sec in total
167 ms
1.3 sec
232 ms
Click here to check amazing Purple Oar content. Otherwise, check out these important facts you probably never knew about purpleoar.co.nz
Contract programming for web sites, mobile and desktop applications. PHP, Javascript, Android, Delphi, Java .NET VB and C#, SQL, CSS, HTML5.
Visit purpleoar.co.nzWe analyzed Purpleoar.co.nz page load time and found that the first response time was 167 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
purpleoar.co.nz performance score
name
value
score
weighting
Value2.7 s
62/100
10%
Value3.2 s
72/100
25%
Value3.2 s
92/100
10%
Value1,250 ms
19/100
30%
Value0.072
96/100
15%
Value4.9 s
78/100
10%
167 ms
601 ms
144 ms
74 ms
57 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 59% of them (19 requests) were addressed to the original Purpleoar.co.nz, 25% (8 requests) were made to Apis.google.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (601 ms) belongs to the original domain Purpleoar.co.nz.
Page size can be reduced by 177.7 kB (70%)
255.1 kB
77.3 kB
In fact, the total size of Purpleoar.co.nz main page is 255.1 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. 40% of websites need less resources to load. Javascripts take 181.0 kB which makes up the majority of the site volume.
Potential reduce by 22.4 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 22.4 kB or 73% of the original size.
Potential reduce by 45 B
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. Purple Oar images are well optimized though.
Potential reduce by 123.3 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 123.3 kB or 68% of the original size.
Potential reduce by 32.0 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. Purpleoar.co.nz needs all CSS files to be minified and compressed as it can save up to 32.0 kB or 77% of the original size.
Number of requests can be reduced by 23 (79%)
29
6
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Purple Oar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
purpleoar.co.nz
167 ms
www.purpleoar.co.nz
601 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
144 ms
css_GXDiyT6XnwoWW7bNbQ5m1j9IUfXjxjvqTSUqTwxweVc.css
74 ms
css_EJ7VuZoUb_JFwE7c65FtIN4JhIQtnstOcrkhIXDTOPw.css
57 ms
css_LtUwwi_C4ZUa3wzyTARmxrw2w6TFubTXWyjTkip9M0k.css
51 ms
css_LuFKySO_wZsxSWmmZsdhzhcoNHSjeoWuMSIpYO3Lv_w.css
90 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
137 ms
js_uvgUomgWRDecmOPO_7f75pcoYGSMgROXSc-zcnF9t5Y.js
184 ms
js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js
127 ms
js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js
166 ms
analytics.js
48 ms
plusone.js
73 ms
pattern_062.gif
90 ms
header.gif
90 ms
li-yellow.png
61 ms
en.png
90 ms
es.png
76 ms
JSIcon32trans.png
59 ms
powered-gray-80x15.png
150 ms
extlink_s.png
110 ms
collect
16 ms
cb=gapi.loaded_0
9 ms
cb=gapi.loaded_1
23 ms
fastbutton
180 ms
postmessageRelay
37 ms
3193398744-postmessagerelay.js
39 ms
rpc:shindig_random.js
31 ms
cb=gapi.loaded_0
3 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
13 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
26 ms
purpleoar.co.nz accessibility score
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
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.
purpleoar.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
purpleoar.co.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
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 Purpleoar.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 Purpleoar.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.
purpleoar.co.nz
Open Graph description is not detected on the main page of Purple Oar. 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: