4.4 sec in total
527 ms
3.5 sec
367 ms
Visit lonelyplanet.ru now to see the best up-to-date Lonelyplanet content for Russia and also check out these interesting facts you probably never knew about lonelyplanet.ru
Visit lonelyplanet.ruWe analyzed Lonelyplanet.ru page load time and found that the first response time was 527 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.
lonelyplanet.ru performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value3.1 s
76/100
25%
Value5.9 s
47/100
10%
Value440 ms
63/100
30%
Value0.369
29/100
15%
Value9.5 s
30/100
10%
527 ms
302 ms
259 ms
260 ms
263 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 45% of them (55 requests) were addressed to the original Lonelyplanet.ru, 16% (20 requests) were made to Static.xx.fbcdn.net and 11% (13 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Lonelyplanet.ru.
Page size can be reduced by 650.1 kB (30%)
2.2 MB
1.5 MB
In fact, the total size of Lonelyplanet.ru main page is 2.2 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 32.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 7.0 kB, which is 17% 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 32.0 kB or 76% of the original size.
Potential reduce by 67.8 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. Lonelyplanet images are well optimized though.
Potential reduce by 470.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 470.5 kB or 69% of the original size.
Potential reduce by 79.8 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. Lonelyplanet.ru needs all CSS files to be minified and compressed as it can save up to 79.8 kB or 81% of the original size.
Number of requests can be reduced by 61 (51%)
120
59
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lonelyplanet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
lonelyplanet.ru
527 ms
jquery.js
302 ms
core.css
259 ms
style.css
260 ms
style.css
263 ms
style.css
280 ms
style.css
384 ms
styles.css
389 ms
template_styles.css
395 ms
core.js
552 ms
core_ajax.js
430 ms
session.js
510 ms
fontface.css
518 ms
960_24_col.css
521 ms
jquery.mousewheel.js
559 ms
jquery.jscrollpane.min.js
636 ms
cicle.js
766 ms
jquery.jscrollpane.css
647 ms
openapi.js
368 ms
index.js
649 ms
openapi.js
614 ms
3_0_FFFFFFFF_FFFFFFFF_1_pageviews
395 ms
bg_top.png
169 ms
b964ea76a6085d4ca7417524d39be4c4.jpg
392 ms
advertisment.gif
169 ms
logo.gif
168 ms
popup_menu_top.png
169 ms
c9debfff642442ffeec7f116addf43cd.jpg
1874 ms
4796770c4443f8d8833e62e991c857f1.jpg
833 ms
5651c7f60c076eb73514acdc0b53476b.jpg
696 ms
a5d522a7ba0f2766b957fb35ecaf25d1.jpg
694 ms
f6de955167e8e4784c5c44db5888e7df.jpg
2209 ms
dest_vostok_175_45.png
678 ms
dest_ujn_amer_57_74.png
693 ms
dest_sev_amer_3_0.png
833 ms
dest_australia_251_105.png
830 ms
dest_asia_181_18.png
831 ms
dest_arctic_58_168.png
939 ms
dest_africa_123_38.png
946 ms
dest_evropa_94_0.png
947 ms
ec161863d2e14ca7ed598c94c62584c1.jpg
1952 ms
a5c7d1b2ac07b5c266bb52f21ab1c010.jpg
1072 ms
fd24cb1d7bf045010582ecb029f2db78.jpg
1732 ms
dce89ed085b7ca2f2d9f9eaf2e021cbb.jpg
2081 ms
right_del.gif
1201 ms
3_300%D1%85250.jpg
1460 ms
footer_logo.jpg
1589 ms
search_bg.gif
1708 ms
big_banner_text_bg.png
1834 ms
banner-sprite.gif
1850 ms
index_map_bg.jpg
1947 ms
map-name-bg.png
1961 ms
sn_sprite2.gif
1978 ms
li_ico_orange.gif
2058 ms
index_overflow_bg.png
2078 ms
all.js
14 ms
upload.gif
150 ms
footer_bg.gif
2075 ms
widget_community.php
282 ms
hit
262 ms
watch.js
637 ms
ga.js
72 ms
165 ms
top100.js
268 ms
orange-arrow-up.png
1988 ms
orange-arrow-down.png
2057 ms
xd_arbiter.php
37 ms
xd_arbiter.php
50 ms
__utm.gif
24 ms
like_box.php
187 ms
xd_arbiter.php
8 ms
hit
145 ms
loader_nav19188_3.js
205 ms
lite.css
128 ms
lite.js
472 ms
lang3_0.js
348 ms
widget_community.css
349 ms
xdm.js
350 ms
al_community.js
349 ms
top100.scn
381 ms
McLpmVM3wCm.css
54 ms
VH4VPudaxfN.css
59 ms
6JjmkAGJU83.css
70 ms
1kPfZUdGrka.js
72 ms
sc76ANiqxZ6.js
71 ms
Mpe38fuBVZ2.js
105 ms
n8qIhCw3vMx.js
108 ms
d20DxWMAn1e.js
110 ms
qcMicXoOToy.js
124 ms
57RpJa05x58.js
115 ms
7B-2ZS3Qt8r.js
112 ms
pf3FNnit_ev.js
115 ms
BmFj6FmaQGO.js
115 ms
hGrOQrzI1QD.js
115 ms
qf1RiuO5N-I.js
116 ms
12063822_922293824485600_6215147983977486052_n.png
135 ms
12074571_936636679717981_1391239276546325396_n.png
67 ms
1860_1114797778570584_8014052438585911785_n.jpg
67 ms
12573730_143098472732754_61375697329402798_n.jpg
66 ms
1619278_566649400157680_7449870710070770999_n.jpg
65 ms
11035976_123117158053271_106518781514423498_n.jpg
64 ms
10411101_10153150387414914_8692580113654720489_n.jpg
68 ms
12523865_192470421127718_5952055635063080008_n.jpg
68 ms
12790900_187763344931964_592725029500441655_n.jpg
66 ms
wL6VQj7Ab77.png
56 ms
s7jcwEQH7Sx.png
57 ms
gxbPuQdXIZP.png
55 ms
advert.gif
119 ms
VXcANLwwL5J.js
3 ms
AmlxWlqMvlv.js
33 ms
FEauHRzEHLc.jpg
367 ms
z87YEuYXDf4.jpg
370 ms
OKzN71D3OSA.jpg
364 ms
UAW_ZeMMokY.jpg
377 ms
DuMdU6bhOBg.jpg
373 ms
FxhEKGnys0Y.jpg
359 ms
o9eyZWM5nnU.jpg
370 ms
KdBbisz3fbw.jpg
365 ms
3ZplL8vXjVw.jpg
381 ms
camera_50.png
154 ms
w_logo.png
120 ms
1
92 ms
lonelyplanet.ru 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.
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.
lonelyplanet.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
lonelyplanet.ru 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lonelyplanet.ru can be misinterpreted by Google and other search engines. Our service has detected that English 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 Lonelyplanet.ru 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.
lonelyplanet.ru
Open Graph description is not detected on the main page of Lonelyplanet. 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: