6.6 sec in total
1.3 sec
4 sec
1.3 sec
Visit aviva.com now to see the best up-to-date Aviva content for United Kingdom and also check out these interesting facts you probably never knew about aviva.com
Our global corporate website for investors, shareholders, career hunters, the media and people interested in our social purpose.
Visit aviva.comWe analyzed Aviva.com page load time and found that the first response time was 1.3 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
aviva.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value3.8 s
56/100
25%
Value5.2 s
61/100
10%
Value2,210 ms
6/100
30%
Value0.016
100/100
15%
Value8.6 s
37/100
10%
1252 ms
176 ms
178 ms
359 ms
187 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 89% of them (65 requests) were addressed to the original Aviva.com, 4% (3 requests) were made to S7.addthis.com and 3% (2 requests) were made to Avivauk.tt.omtrdc.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source M.addthis.com.
Page size can be reduced by 854.4 kB (59%)
1.5 MB
604.0 kB
In fact, the total size of Aviva.com main page is 1.5 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. 35% of websites need less resources to load. Javascripts take 890.3 kB which makes up the majority of the site volume.
Potential reduce by 67.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 67.7 kB or 74% of the original size.
Potential reduce by 16.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. Aviva images are well optimized though.
Potential reduce by 605.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 605.8 kB or 68% of the original size.
Potential reduce by 164.3 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. Aviva.com needs all CSS files to be minified and compressed as it can save up to 164.3 kB or 78% of the original size.
Number of requests can be reduced by 41 (58%)
71
30
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aviva. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.aviva.com
1252 ms
jquery.fancybox.css
176 ms
utils.css
178 ms
base.css
359 ms
header.css
187 ms
footer.css
363 ms
logo.css
271 ms
skip-links.css
346 ms
search.css
262 ms
share-price.css
365 ms
country-select.css
435 ms
nav-main.css
449 ms
cookies-banner.css
518 ms
fancybox.css
527 ms
buttons.css
450 ms
content-rows.css
454 ms
content-blocks.css
522 ms
back-top-links.css
541 ms
grid-system-legacy.css
540 ms
nav-page.css
544 ms
hero.css
604 ms
site-selector.css
610 ms
section-headings.css
614 ms
pods.css
716 ms
homepage.css
721 ms
modernizr-2.8.3.js
724 ms
jquery.min.js
992 ms
jquery.fancybox.js
869 ms
global.js
785 ms
addthis_widget.js
16 ms
satelliteLib-e8013b342ae6e497ceec2d71c3df6d7c5dab6bbc.js
1180 ms
mbox.js
941 ms
enquire.js
825 ms
jquery.waypoints.js
883 ms
jquery.scrollTo.js
1136 ms
jquery.scrollup.event.js
1133 ms
site.js
1136 ms
data-layer.js
1136 ms
target.js
15 ms
Good-thinking-family-shot-pod.jpg
712 ms
management-adrian.jpg
178 ms
management-mark.jpg
264 ms
management-tom.jpg
180 ms
standard
9 ms
info-icon.png
180 ms
list-links.svg
108 ms
icon-globe.svg
259 ms
icon-search.svg
217 ms
menu-bars.svg
227 ms
show-hide-plus.svg
269 ms
united-kingdom.png
387 ms
shareprice-up-large.svg
306 ms
united-states.png
316 ms
Hero-1186x520.jpg
727 ms
union-jack.svg
361 ms
globe.svg
480 ms
twitter.svg
407 ms
calendar.svg
455 ms
4472_Aviva-ARA-2014.pdf.jpg.100x100_q85.jpg
561 ms
4528_Aviva-SR-2014.pdf.jpg.100x100_q85.jpg
583 ms
4476_CR-Report-2014.pdf.jpg.100x100_q85.jpg
635 ms
back-top.svg
568 ms
home_sprite.svg
765 ms
btn-arrows.svg
659 ms
jquery.animateOnAppear.js
629 ms
jquery.appear.min.js
671 ms
menu.c20a7f164de4760a4fae.js
25 ms
s_code.js
882 ms
frutigerltw01-45light.woff
740 ms
sh.808a95620474b05b281a4965.html
23 ms
300lo.json
1253 ms
standard
8 ms
s07895687317941
10 ms
aviva.com 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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
aviva.com 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
Page has valid source maps
aviva.com SEO score
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 Aviva.com 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 Aviva.com 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.
aviva.com
Open Graph description is not detected on the main page of Aviva. 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: