8.8 sec in total
1.6 sec
5.9 sec
1.3 sec
Welcome to lifeafterlondon.com homepage info - get ready to check Life After London best content for United Kingdom right away, or after learning these important things about lifeafterlondon.com
It can be hard to know where to turn when you're thinking of leaving London! We're here to help you access a wealth of local knowledge and FREE advice.
Visit lifeafterlondon.comWe analyzed Lifeafterlondon.com page load time and found that the first response time was 1.6 sec and then it took 7.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.
lifeafterlondon.com performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value48.0 s
0/100
25%
Value18.6 s
0/100
10%
Value6,890 ms
0/100
30%
Value0.026
100/100
15%
Value41.9 s
0/100
10%
1561 ms
113 ms
154 ms
180 ms
270 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 86% of them (66 requests) were addressed to the original Lifeafterlondon.com, 8% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Lifeafterlondon.com.
Page size can be reduced by 1.8 MB (14%)
12.7 MB
10.8 MB
In fact, the total size of Lifeafterlondon.com main page is 12.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.8 MB which makes up the majority of the site volume.
Potential reduce by 38.2 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 38.2 kB or 78% of the original size.
Potential reduce by 1.1 MB
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. Life After London images are well optimized though.
Potential reduce by 241.4 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 241.4 kB or 82% of the original size.
Potential reduce by 413.6 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. Lifeafterlondon.com needs all CSS files to be minified and compressed as it can save up to 413.6 kB or 87% of the original size.
Number of requests can be reduced by 41 (59%)
69
28
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life After London. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.lifeafterlondon.com
1561 ms
shareaholic.js
113 ms
twemoji.js
154 ms
wp-emoji.js
180 ms
bbpress.css
270 ms
styles.css
178 ms
cli-style.css
181 ms
woocommerce-layout.css
272 ms
woocommerce.css
326 ms
css
39 ms
css
39 ms
style.css
786 ms
style.css
266 ms
public.css
270 ms
shortcodes.css
442 ms
shortcodes_responsive.css
362 ms
s2member-o.php
1180 ms
jquery.js
537 ms
jquery-migrate.js
414 ms
script.js
448 ms
cookielawinfo.js
504 ms
mediaelementplayer-legacy.min.css
530 ms
wp-mediaelement.css
537 ms
editor.js
590 ms
scripts.js
620 ms
add-to-cart.js
627 ms
jquery.blockUI.js
628 ms
js.cookie.js
679 ms
woocommerce.js
710 ms
cart-fragments.js
717 ms
jquery.fitvids.js
717 ms
waypoints.min.js
769 ms
jquery.magnific-popup.js
815 ms
custom.js
899 ms
smoothscroll.js
839 ms
common.js
858 ms
s2member-o.php
1627 ms
wp-embed.js
836 ms
mediaelement-and-player.js
1116 ms
mediaelement-migrate.js
897 ms
wp-mediaelement.js
835 ms
fbevents.js
166 ms
Life-After-London-Logo-Trans-Mini.png
311 ms
Copy-of-View-our-Previous-Featured-Properties-1-300x300.png
297 ms
Copy-of-View-our-Previous-Featured-Properties-2.png
675 ms
View-our-Previous-Featured-Properties-2-1-300x300.png
563 ms
Featured-partner-compare-my-move-300x300.png
297 ms
Forums.png
827 ms
Forums-8.jpg
441 ms
Forums-9.jpg
573 ms
Forums-3.png
570 ms
Forums-2.jpg
788 ms
Forums-2.png
824 ms
Forums-1.jpg
632 ms
Forums-7.jpg
682 ms
Screen-Shot-2016-05-25-at-15.25.00.jpg
701 ms
SIGN-UP-NOW.png
740 ms
How-to-train-your-puppy-2.jpg
774 ms
Renting-out-your-property-advice-1.png
795 ms
Forum-Search-2.png
841 ms
School-1.png
869 ms
Life-After-London-Footer-Banner-v7-Light-Green-Medium-Trees.png
877 ms
Twitter.png
886 ms
Facebook.png
904 ms
Google.png
908 ms
LinkedIn.png
930 ms
overlay.png
958 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
186 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
167 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
167 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
183 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
157 ms
ETmodules_v2.ttf
828 ms
1259191644097607
87 ms
www.lifeafterlondon.com
1180 ms
woocommerce-smallscreen.css
92 ms
lifeafterlondon.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.
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.
lifeafterlondon.com 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
lifeafterlondon.com 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
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 Lifeafterlondon.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 Lifeafterlondon.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.
lifeafterlondon.com
Open Graph description is not detected on the main page of Life After London. 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: