10.9 sec in total
613 ms
9.1 sec
1.2 sec
Welcome to olondon.ru homepage info - get ready to check O London best content right away, or after learning these important things about olondon.ru
Разработка и поддержка сайтов, услуги для успешного бизнеса в интернете.
Visit olondon.ruWe analyzed Olondon.ru page load time and found that the first response time was 613 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
olondon.ru performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value9.0 s
1/100
25%
Value7.8 s
24/100
10%
Value150 ms
95/100
30%
Value0
100/100
15%
Value6.3 s
61/100
10%
613 ms
1228 ms
362 ms
358 ms
83 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 84% of them (69 requests) were addressed to the original Olondon.ru, 4% (3 requests) were made to Yastatic.net and 2% (2 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain Olondon.ru.
Page size can be reduced by 321.2 kB (5%)
5.9 MB
5.5 MB
In fact, the total size of Olondon.ru main page is 5.9 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. 65% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.
Potential reduce by 34.3 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 34.3 kB or 74% of the original size.
Potential reduce by 168.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. O London images are well optimized though.
Potential reduce by 64.1 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 64.1 kB or 58% of the original size.
Potential reduce by 54.2 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. Olondon.ru needs all CSS files to be minified and compressed as it can save up to 54.2 kB or 84% of the original size.
Number of requests can be reduced by 16 (21%)
76
60
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O 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 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
olondon.ru
613 ms
www.olondon.ru
1228 ms
jquery-1.8.2.min.js
362 ms
jquery.lazyload.min.js
358 ms
cnt.share.js
83 ms
jquery-ui.css
466 ms
style.css
356 ms
style.css
470 ms
kernel_main.css
462 ms
template_e6feff7383f09fe9513c19b72c5d12df.css
538 ms
kernel_main.js
1277 ms
core_db.min.js
651 ms
core_frame_cache.min.js
653 ms
flappy.js
2345 ms
logo.png
228 ms
11ab6c4cedbea88a7f367f7d069e69cf.png
1099 ms
560f4d6ea5f90a1991cc6ef1071d1728.png
1118 ms
28162ad768a3c3713721d1b53c3a3dca.png
2352 ms
4a1674f2e03aa635d3da4914df45cc34.png
1048 ms
a4f8a8c6e6206aadad4f63796cb42e10.png
969 ms
a6133658b0356124c5d87c006d205bac.png
1100 ms
709abbb37426f9fa096d3203ecb44f57.jpg
1180 ms
707943ad93a1ed2111cf41d3b7182d4d.jpg
1238 ms
0cb92a842754d67f224646ea49fb72fe.jpg
1418 ms
3611cb2e0de945f9553068d015ba3e0c.jpg
1258 ms
839b22b1187d9ad4a6c382a0768d5623.jpg
1509 ms
60fab7ace01e949ae733b59b6be8c188.jpg
1422 ms
4dde774798986f48302d09a99d4c5d7e.jpg
1434 ms
131d60491e8ae95113c8153edbc00ba5.jpg
1601 ms
dbafcfec8b28130934df73d6e85d442f.jpg
1601 ms
41cc3c19a19ffb96fe21ecca70b11c8f.jpg
1620 ms
18f19c54fc83080f6f628389435bc393.jpg
1832 ms
d34c69123cbf0682f91543f6537b2dc0.png
2343 ms
320ccec1d24994b58b5caa52811c74f6.png
4312 ms
22959d2e6a6895f6f0bbb2a122e873de.png
2590 ms
d55ee35d4a22baef4f0a2551d3e58f47.png
4130 ms
5d83da59132a81e6b972236f0ea61c17.png
4481 ms
bc7aa85821247e1703d06610c59d0414.png
5404 ms
d4a70b04a161fb10ad340b5803dfe26f.png
2456 ms
a34733195d596401b7b1a09a412b1aa3.png
2906 ms
b8777e19974f44041fd6af1f74be3d1e.png
4179 ms
64bd9ab2a3e3d176d0c5c6cebfea1ace.png
3253 ms
2beb078580a5a3eb3f6bc55a64f53c8d.png
3898 ms
05efa8d95721af5b19761c22dfb4e364.png
4355 ms
watch.js
26 ms
a791fa6ae2253c891b4171c8891f0960.png
6517 ms
cfbc7d8c00a0cfcec208f96ea8975bcf.png
5622 ms
job.png
4305 ms
bird.png
4344 ms
bebasneue_bold-webfont.woff
4444 ms
ba.js
192 ms
bebasneue_book-webfont.woff
3813 ms
click.png
3776 ms
bx.png
3773 ms
footer-cake.jpg
3929 ms
corner.png
3807 ms
bg-main.png
3885 ms
background.png
3905 ms
bird_Sprite.png
3944 ms
order-close.png
3955 ms
site-order-small.png
3853 ms
show-more.png
3949 ms
bg-footer.jpg
3968 ms
footer-shadow.jpg
3942 ms
icon-footer-phone.png
3936 ms
icon-footer-address.png
3973 ms
icon-footer-skype.png
4187 ms
icon-footer-mail.png
3817 ms
ya-share-cnt.html
313 ms
watch.js
296 ms
bx_stat
356 ms
site_order.php
3616 ms
b-share-icon.png
129 ms
b-share_counter_small.png
138 ms
798 ms
share_count
2860 ms
dk
869 ms
fql.query
713 ms
share.php
765 ms
bitrix_order.php
3636 ms
site-order-big.png
3371 ms
captcha.php
871 ms
olondon.ru accessibility score
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
olondon.ru 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
Browser errors were logged to the console
olondon.ru 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
RU
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olondon.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Olondon.ru main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
olondon.ru
Open Graph description is not detected on the main page of O 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: