8.8 sec in total
640 ms
4.8 sec
3.3 sec
Click here to check amazing Livelonger content. Otherwise, check out these important facts you probably never knew about livelonger.co.nz
At Hi Ho our digital marketing team are masters of creating bespoke websites & fully automated digital marketing campaigns that convert. Let’s strategise!
Visit livelonger.co.nzWe analyzed Livelonger.co.nz page load time and found that the first response time was 640 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
livelonger.co.nz performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value3.6 s
59/100
25%
Value6.9 s
34/100
10%
Value400 ms
67/100
30%
Value0.011
100/100
15%
Value14.8 s
8/100
10%
640 ms
1203 ms
32 ms
866 ms
664 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Livelonger.co.nz, 58% (29 requests) were made to Hiho.co.nz and 8% (4 requests) were made to Pixel-geo.prfct.co. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Hiho.co.nz.
Page size can be reduced by 243.2 kB (80%)
303.1 kB
59.8 kB
In fact, the total size of Livelonger.co.nz main page is 303.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. 65% of websites need less resources to load. HTML takes 293.0 kB which makes up the majority of the site volume.
Potential reduce by 242.7 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 242.7 kB or 83% of the original size.
Potential reduce by 554 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 37 (90%)
41
4
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Livelonger. 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 as a result speed up the page load time.
livelonger.co.nz
640 ms
hiho.co.nz
1203 ms
css
32 ms
jquery.min.js
866 ms
jquery-migrate.min.js
664 ms
flatpickr.min.js
874 ms
select2.min.js
872 ms
createjs.min.js
1129 ms
lava.js
396 ms
sharpspring.js
396 ms
typed.js
652 ms
typed.fe.js
1017 ms
frontend.min.js
580 ms
typewriter.min.js
1235 ms
hoverIntent.min.js
584 ms
flatsome.js
1667 ms
flatsome-wp-rocket.js
1236 ms
flatsome-instant-page.js
1316 ms
flatsome-live-search.js
1479 ms
core.min.js
1703 ms
pum-site-scripts.js
2117 ms
frm.min.js
2394 ms
api.js
125 ms
mobile-detect.min.js
1326 ms
maxmegamenu.js
2006 ms
packery.pkgd.min.js
2219 ms
lazyload.min.js
1675 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
27 ms
1756PLBenguiatCaslon.woff
2649 ms
883SourceSerif.woff
2882 ms
fl-icons.ttf
2562 ms
email-decode.min.js
2023 ms
ss.js
105 ms
hiho-logo-rev.svg
645 ms
koi
110 ms
5e30b73776b2187db0000b0b.js
25 ms
fbevents.js
17 ms
tagjs
3 ms
21 ms
adsct
140 ms
tap.php
61 ms
pixel
85 ms
sd
5 ms
3 ms
bounce
21 ms
pixel
31 ms
cb
2 ms
bounce
20 ms
cb
11 ms
livelonger.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.
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
ARIA IDs are not unique
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.
livelonger.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
Missing source maps for large first-party JavaScript
livelonger.co.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
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 Livelonger.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 Livelonger.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.
livelonger.co.nz
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: