4.2 sec in total
266 ms
3.7 sec
209 ms
Welcome to lifecompared.com homepage info - get ready to check Lifecompared best content for United Kingdom right away, or after learning these important things about lifecompared.com
LifeCompared offer FREE life insurance quotes and impartial advice with no obligations. Save money with our exclusive deals, it only takes 30 seconds!
Visit lifecompared.comWe analyzed Lifecompared.com page load time and found that the first response time was 266 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
lifecompared.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value4.8 s
30/100
25%
Value5.0 s
63/100
10%
Value1,510 ms
14/100
30%
Value0
100/100
15%
Value10.0 s
27/100
10%
266 ms
591 ms
258 ms
262 ms
285 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 80% of them (57 requests) were addressed to the original Lifecompared.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Lifecompared.com.
Page size can be reduced by 242.3 kB (64%)
378.0 kB
135.7 kB
In fact, the total size of Lifecompared.com main page is 378.0 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. 30% of websites need less resources to load. Javascripts take 309.6 kB which makes up the majority of the site volume.
Potential reduce by 35.6 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 35.6 kB or 79% of the original size.
Potential reduce by 189.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 189.0 kB or 61% of the original size.
Potential reduce by 17.7 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. Lifecompared.com needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 77% of the original size.
Number of requests can be reduced by 28 (41%)
68
40
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifecompared. 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 from 4 to 1 for CSS and as a result speed up the page load time.
lifecompared.com
266 ms
www.lifecompared.com
591 ms
reset.css
258 ms
layout.css
262 ms
owl.carousel.css
285 ms
ouibounce.min.css
277 ms
jquery.js
415 ms
parsley.js
388 ms
owl.carousel.min.js
615 ms
jquery.quovolver.min.js
530 ms
ouibounce.js
543 ms
background-grid.jpg
444 ms
logo-main.png
168 ms
trustseal.png
287 ms
comodo-secure-padlock.png
289 ms
family.png
362 ms
steps-1.png
294 ms
steps-2.png
461 ms
steps-3.png
560 ms
aviva.jpg
562 ms
brightgrey.jpg
567 ms
friendslife.jpg
651 ms
prudential.jpg
721 ms
legalandgeneral.jpg
731 ms
hsbc.jpg
809 ms
liverpoolvictoria.jpg
838 ms
rsa.jpg
834 ms
johnlewis.jpg
941 ms
axa.jpg
967 ms
nationwide.jpg
1005 ms
santander.jpg
1056 ms
sunlifedirect.jpg
1108 ms
ageas.jpg
1115 ms
aegon.jpg
1207 ms
greenbee.jpg
1228 ms
standardlife.jpg
1256 ms
endsleigh.jpg
1312 ms
equitablelife.jpg
1352 ms
aig.jpg
1361 ms
zurich.jpg
1497 ms
royalliverassurance.jpg
1489 ms
scottishwidows.jpg
1537 ms
royallondonplus.jpg
1560 ms
thecooperativeinsurance.jpg
1617 ms
scottishprovident.jpg
1624 ms
dpl.png
1733 ms
gtm.js
137 ms
pixel.gif
1764 ms
analytics.js
63 ms
conversion_async.js
103 ms
js
109 ms
0f24704f-3108-465f-a5f6-07a0fe943e71.js
107 ms
bat.js
183 ms
fbds.js
105 ms
background-header.png
1630 ms
collect
21 ms
46 ms
115 ms
field-bg.png
1559 ms
sprites.png
1580 ms
splash.jpg
1694 ms
38 ms
ga-audiences
39 ms
tick.png
1632 ms
in.php
285 ms
background-insurers.jpg
1607 ms
background-message.png
1602 ms
background-message-corners.png
1555 ms
lifecompared-rating.png
1573 ms
background-copyright.png
1662 ms
22 ms
lifecompared.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lifecompared.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
Missing source maps for large first-party JavaScript
lifecompared.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifecompared.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lifecompared.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.
lifecompared.com
Open Graph description is not detected on the main page of Lifecompared. 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: