9.8 sec in total
1 sec
8.4 sec
376 ms
Welcome to orangehealth.co.nz homepage info - get ready to check Orange Health best content right away, or after learning these important things about orangehealth.co.nz
We treat the cause! What you eat and how you sleep are all clues to help us find the underlying cause of your ill health. We then develop a treatment plan for you.
Visit orangehealth.co.nzWe analyzed Orangehealth.co.nz page load time and found that the first response time was 1 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
orangehealth.co.nz performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value18.5 s
0/100
25%
Value17.3 s
0/100
10%
Value21,870 ms
0/100
30%
Value0.001
100/100
15%
Value28.8 s
0/100
10%
1036 ms
291 ms
1003 ms
1008 ms
371 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 44% of them (44 requests) were addressed to the original Orangehealth.co.nz, 24% (24 requests) were made to Fonts.gstatic.com and 13% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Orangehealth.co.nz.
Page size can be reduced by 258.9 kB (27%)
956.4 kB
697.4 kB
In fact, the total size of Orangehealth.co.nz main page is 956.4 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. 70% of websites need less resources to load. Images take 449.2 kB which makes up the majority of the site volume.
Potential reduce by 232.9 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 232.9 kB or 86% of the original size.
Potential reduce by 5.6 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. Orange Health images are well optimized though.
Potential reduce by 20.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 20.3 kB or 11% of the original size.
Potential reduce by 71 B
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. Orangehealth.co.nz has all CSS files already compressed.
Number of requests can be reduced by 47 (68%)
69
22
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orange Health. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
orangehealth.co.nz
1036 ms
wc-blocks-vendors-style.css
291 ms
wc-blocks-style.css
1003 ms
woocommerce-layout.css
1008 ms
woocommerce.css
371 ms
public-main.css
1052 ms
front.min.css
1023 ms
wp_dtb-style-5133656.css
137 ms
style.css
483 ms
style.css
497 ms
public-main.js
1450 ms
front.min.js
1731 ms
et-core-unified-52386.min.css
999 ms
email-decode.min.js
804 ms
js
58 ms
jquery.min.js
1790 ms
jquery-migrate.min.js
1209 ms
jquery.blockUI.min.js
1928 ms
add-to-cart.min.js
1977 ms
js.cookie.min.js
2150 ms
woocommerce.min.js
1701 ms
cart-fragments.min.js
2700 ms
scripts.min.js
3024 ms
smoothscroll.js
2193 ms
jquery.fitvids.js
2234 ms
frontend-bundle.min.js
3174 ms
common.js
3103 ms
toolbox-scripts.js
3222 ms
main.js
2695 ms
motion-effects.js
3351 ms
style.css
3158 ms
hotjar-3101003.js
231 ms
embed
363 ms
OH-Logo-Design-v10_E__1_-removebg-preview.png
1556 ms
laura-ohlman-jvUU71_rfSM-unsplash-1.jpg
1344 ms
FISH.png
1310 ms
OH-Logo-Design-v10_E.jpeg
1130 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
54 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
57 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
56 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
54 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
47 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
51 ms
Outfit-Light.ttf
402 ms
Outfit-Regular.ttf
1066 ms
modules.ttf
1622 ms
Outfit-Bold.ttf
1302 ms
fa-solid-900.woff
1410 ms
fa-brands-400.woff
1489 ms
fa-regular-400.woff
2175 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
48 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
50 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
48 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
58 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff
59 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
61 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
59 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
61 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff
60 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
62 ms
et-divi-dynamic-tb-33-tb-40-52386-late.css
2281 ms
modules.21c2ce197b1deec7582e.js
17 ms
js
20 ms
gen_204
22 ms
init_embed.js
26 ms
common.js
62 ms
util.js
88 ms
map.js
81 ms
overlay.js
75 ms
onion.js
69 ms
search_impl.js
68 ms
StaticMapService.GetMapImage
219 ms
openhand_8_8.cur
47 ms
kh
53 ms
ViewportInfoService.GetViewportInfo
48 ms
AuthenticationService.Authenticate
23 ms
vt
150 ms
vt
153 ms
vt
132 ms
vt
136 ms
vt
142 ms
vt
129 ms
vt
174 ms
QuotaService.RecordEvent
17 ms
controls.js
4 ms
css
77 ms
css
77 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
6 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
4 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
8 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
8 ms
woocommerce-smallscreen.css
952 ms
orangehealth.co.nz
864 ms
analytics.js
21 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
34 ms
collect
69 ms
visit-data
454 ms
orangehealth.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
orangehealth.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
orangehealth.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
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 Orangehealth.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 Orangehealth.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.
orangehealth.co.nz
Open Graph data is detected on the main page of Orange Health. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: