3.9 sec in total
239 ms
3.4 sec
262 ms
Welcome to leo.co.uk homepage info - get ready to check Leo best content for United Kingdom right away, or after learning these important things about leo.co.uk
Exclusive office environments, meeting rooms and event spaces, with the most prestigious London addresses. Find out more here.
Visit leo.co.ukWe analyzed Leo.co.uk page load time and found that the first response time was 239 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
leo.co.uk performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value13.2 s
0/100
25%
Value9.8 s
10/100
10%
Value840 ms
34/100
30%
Value0.248
50/100
15%
Value14.7 s
8/100
10%
239 ms
1717 ms
77 ms
151 ms
153 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 72% of them (53 requests) were addressed to the original Leo.co.uk, 4% (3 requests) were made to Gateway3.whoson.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Leo.co.uk.
Page size can be reduced by 275.4 kB (7%)
4.1 MB
3.8 MB
In fact, the total size of Leo.co.uk main page is 4.1 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 50.0 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. This page needs HTML code to be minified as it can gain 6.8 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.0 kB or 80% of the original size.
Potential reduce by 87.4 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. Leo images are well optimized though.
Potential reduce by 77.5 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 77.5 kB or 65% of the original size.
Potential reduce by 60.5 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. Leo.co.uk needs all CSS files to be minified and compressed as it can save up to 60.5 kB or 86% of the original size.
Number of requests can be reduced by 50 (74%)
68
18
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leo. 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 14 to 1 for CSS and as a result speed up the page load time.
leo.co.uk
239 ms
www.leo.co.uk
1717 ms
twemoji.js
77 ms
wp-emoji.js
151 ms
wpfp.css
153 ms
formidablepro.css
159 ms
prettyPhoto.css
154 ms
wp-video-lightbox.css
164 ms
front.css
165 ms
owl.carousel.css
224 ms
style.css
227 ms
main.css
382 ms
sow-button-atom-594ad7f47f45.css
237 ms
style.css
237 ms
jquery.js
327 ms
jquery-migrate.js
298 ms
jquery.prettyPhoto.js
303 ms
video-lightbox.js
311 ms
owl.carousel.js
314 ms
owl.script.js
371 ms
jquery.cycle.all.min.js
379 ms
rotating_tweet.js
426 ms
wpfp.js
427 ms
MyFontsWebfontsKit.css
429 ms
js
37 ms
infobox.js
44 ms
font-awesome.min.css
48 ms
materialize.min.js
58 ms
57106.js
59 ms
jquery.mCustomScrollbar.concat.min.js
48 ms
jquery.mCustomScrollbar.min.css
49 ms
include.js
193 ms
main.js
535 ms
wp-embed.js
483 ms
jquery.placeholder.js
483 ms
formidable.js
547 ms
widgets.js
205 ms
300d57
22 ms
loader.js
10 ms
logo.png
149 ms
OPS-2.jpg
686 ms
3-23.jpg
691 ms
MichelinHouse_header.jpg
535 ms
14_Curzon.jpg
700 ms
MH.jpg
686 ms
balloon.png
175 ms
ajax_loader.gif
246 ms
slide_25.png
489 ms
slide_27.png
653 ms
slide_29.png
613 ms
seet.png
688 ms
hand_shake.png
735 ms
icons__IT.png
765 ms
logo_white.png
765 ms
quantum_logo.png
763 ms
fb_ico.png
766 ms
twitter_ico.png
773 ms
vimeo_ico.png
814 ms
linkedin_ico.png
838 ms
instagram_ico.png
839 ms
gtm.js
135 ms
logo-slider.png
836 ms
gateway3.whoson.com
133 ms
invite.js
168 ms
impl-1_22.js
28 ms
form_arrow.png
813 ms
analytics.js
78 ms
300D57_1_0.woff
779 ms
300D57_0_0.woff
830 ms
collect
18 ms
collect
55 ms
collect
11 ms
collect
56 ms
ga-audiences
42 ms
leo.co.uk 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
leo.co.uk 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
leo.co.uk 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leo.co.uk 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 Leo.co.uk 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.
leo.co.uk
Open Graph data is detected on the main page of Leo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: