7.9 sec in total
1.7 sec
6.1 sec
121 ms
Welcome to saferx.co.nz homepage info - get ready to check Safe Rx best content for New Zealand right away, or after learning these important things about saferx.co.nz
Visit saferx.co.nzWe analyzed Saferx.co.nz page load time and found that the first response time was 1.7 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
saferx.co.nz performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value4.2 s
44/100
25%
Value6.6 s
38/100
10%
Value120 ms
97/100
30%
Value0.493
17/100
15%
Value7.6 s
47/100
10%
1668 ms
766 ms
2751 ms
666 ms
762 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 70% of them (28 requests) were addressed to the original Saferx.co.nz, 18% (7 requests) were made to and 5% (2 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Saferx.co.nz.
Page size can be reduced by 488.2 kB (49%)
987.3 kB
499.0 kB
In fact, the total size of Saferx.co.nz main page is 987.3 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. 35% of websites need less resources to load. Javascripts take 554.5 kB which makes up the majority of the site volume.
Potential reduce by 13.1 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 13.1 kB or 60% of the original size.
Potential reduce by 32.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. Safe Rx images are well optimized though.
Potential reduce by 393.8 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 393.8 kB or 71% of the original size.
Potential reduce by 49.2 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. Saferx.co.nz needs all CSS files to be minified and compressed as it can save up to 49.2 kB or 81% of the original size.
Number of requests can be reduced by 12 (38%)
32
20
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Safe Rx. 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 as a result speed up the page load time.
saferx.co.nz
1668 ms
328a65559a21dc7af55ccec985f25ddb.36.css
766 ms
2add648e0135c3065b8b6a183eaf85d2.36.js
2751 ms
superfish.css
666 ms
WebResource.axd
762 ms
jquery.cycle.all.min.js
1143 ms
module.js
390 ms
Telerik.Web.UI.WebResource.axd
1383 ms
dnn.js
1140 ms
939d4146295282bee2dee4b31e6b227f.36.js
767 ms
jquery.watermark.min.js
952 ms
wkx4nbx.js
144 ms
initWidgets.js
770 ms
ga.js
6 ms
hoverIntent.js
193 ms
logo.png
195 ms
wdhb.png
224 ms
Bulletins.jpg
784 ms
ConversionGuide.jpg
1554 ms
ConversionGuide2.jpg
1523 ms
paracetamol2.jpg
1521 ms
Patient-and-Pharmacist.jpg
1721 ms
tramadolguide.jpg
2004 ms
__utm.gif
22 ms
superfish.js
791 ms
search-icon.gif
198 ms
nav-bg.png
406 ms
nav-sep.png
577 ms
red-button-bg.png
695 ms
grey-button-bg.png
696 ms
p.gif
121 ms
wkx4nbx-d.css
292 ms
DotNetNukeAjaxShared.js
608 ms
QhNleo8v9xnqA3AAAAAAABAAAAAMbULpkAAAAAyTePJAAAAADJOVVB
17 ms
DH4PNx70v4r3gro99FR8ATwPxMOdfQ2HiZeb+KnMejv+MZI4TZZJMlinyPnPMbvDlfAFzWSErJYcZhX5F34KnbDOLd8ou2Y3NJbL3f2k5N8cAAAAAAQAAAADG1C6ZAAAAAMk3jygAAAAAyTlVSg==
14 ms
D3kCkbPIeb1WxtuHzDu36H26IUZEAAAAAAAABAAAAAMbULpkAAAAAyTePIAAAAADJOVU4
12 ms
g92IrJ0AAAAAQAAAADG1C6ZAAAAAMfrKvQAAAAAyRtkCA==
12 ms
wErM7IrAAAAAQAAAADG1C6ZAAAAAMfrKvQAAAAAyRtj3Q==
11 ms
aXVohAAAAAAAAAEAAAAAxtQumQAAAADH6yr0AAAAAMkbZBM=
11 ms
mZ9A+eoV+p4P0BmUC3qYsOk7v0EnAu5RLefQenaVi2vkfZD9tmgAAAAAAAQAAAADG1C6ZAAAAAMfrKvQAAAAAyRtj6A==
9 ms
saferx.co.nz accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
saferx.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
saferx.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saferx.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 Saferx.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.
saferx.co.nz
Open Graph description is not detected on the main page of Safe Rx. 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: