7.5 sec in total
1.9 sec
4.4 sec
1.2 sec
Click here to check amazing Assurity content. Otherwise, check out these important facts you probably never knew about assurity.nz
Our customer-centric approach and expertise ensure you get the ideal solution delivered right.
Visit assurity.nzWe analyzed Assurity.nz page load time and found that the first response time was 1.9 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
assurity.nz performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value9.0 s
1/100
25%
Value12.0 s
4/100
10%
Value1,560 ms
13/100
30%
Value0.007
100/100
15%
Value19.5 s
2/100
10%
1938 ms
273 ms
304 ms
437 ms
505 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 76% of them (66 requests) were addressed to the original Assurity.nz, 7% (6 requests) were made to Unpkg.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Assurity.nz.
Page size can be reduced by 1.1 MB (32%)
3.3 MB
2.2 MB
In fact, the total size of Assurity.nz main page is 3.3 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 87.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 87.1 kB or 82% of the original size.
Potential reduce by 160.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. Assurity images are well optimized though.
Potential reduce by 299.0 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 299.0 kB or 65% of the original size.
Potential reduce by 511.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. Assurity.nz needs all CSS files to be minified and compressed as it can save up to 511.0 kB or 84% of the original size.
Number of requests can be reduced by 43 (53%)
81
38
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Assurity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
assurity.nz
1938 ms
style.min.css
273 ms
bundle.client.css
304 ms
bootstrap.min.css
437 ms
all.min.css
505 ms
swiper-bundle.min.css
47 ms
lity.min.css
240 ms
style.css
371 ms
post-3034.css
447 ms
post-11316.css
342 ms
post-2.css
378 ms
dynamic_css.css
415 ms
css
46 ms
search-forms.css
448 ms
style.css
452 ms
consent-mode.js
485 ms
jQuery.min.js
576 ms
x-frontend.js
523 ms
swiper-bundle.min.css
16 ms
swiper-bundle.min.css
23 ms
embed.js
49 ms
21020761.js
148 ms
bundle.client.js
392 ms
popper.min.js
393 ms
bootstrap.notooltips.min.js
428 ms
bootstrap_3.3.7.min.js
445 ms
lottie.min.js
53 ms
webfont.js
44 ms
swiper-bundle.min.js
47 ms
lity.min.js
546 ms
meta.js
546 ms
front.js
547 ms
front.js
582 ms
zu.global.min.js
582 ms
animatedburger.js
581 ms
inert.js
579 ms
front.js
580 ms
frontend.js
580 ms
post-3034.js
720 ms
script.min.js
721 ms
x-frontend-run.js
721 ms
swiper-bundle.min.js
14 ms
swiper-bundle.min.js
28 ms
gtm.js
318 ms
custom-logo.png
294 ms
ASSURITY-logo.png
238 ms
Trainer-leading-agile-course.jpg
434 ms
heart.png
237 ms
shutterstock_1615159249_V2-scaled.jpg
418 ms
AA-3.png
691 ms
Assurity-Enable-Web-3.jpg
502 ms
rocket.png
353 ms
photo-1565120130276-dfbd9a7a3ad7.jpeg
355 ms
Farmlands-Business-Analysis.jpg
428 ms
chart.png
429 ms
ird.png
489 ms
mercury.png
501 ms
worksafe.png
503 ms
internal-affairs.png
507 ms
enable.png
561 ms
nzqa.png
645 ms
logo-uc.png
575 ms
logo-aia.png
574 ms
logo-aucklandtransport.png
580 ms
logo-norwood.png
632 ms
logo-statsnz.png
648 ms
logo-sky.png
649 ms
logo-wsp.png
653 ms
logo-anzco.png
647 ms
westpac.png
664 ms
logo-carrfields.png
662 ms
banner.js
230 ms
fb.js
252 ms
21020761.js
286 ms
collectedforms.js
252 ms
css
147 ms
font
224 ms
fa-solid-900.woff
633 ms
logo-connexis.png
657 ms
logo-nzx.png
668 ms
social-icon-30px-fb-30x30x_c_802_1710145266.png
685 ms
social-icon-30px-li-30x30x_c_823_1710145266.png
700 ms
social-icons-30px-x.png
702 ms
social-icon-30px-is-30x30x_c_965_1710145266.png
578 ms
social-icon-30px-yt-30x30x_c_820_1710145266.png
569 ms
insight.min.js
64 ms
insight_tag_errors.gif
92 ms
assurity.nz accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
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
assurity.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
Browser errors were logged to the console
Page has valid source maps
assurity.nz SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Assurity.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 Assurity.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.
assurity.nz
Open Graph data is detected on the main page of Assurity. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: