3.8 sec in total
448 ms
3 sec
328 ms
Visit lunchme.ru now to see the best up-to-date Lunchme content and also check out these interesting facts you probably never knew about lunchme.ru
Узнать подробнее о домене в магазине доменов RU-CENTER.
Visit lunchme.ruWe analyzed Lunchme.ru page load time and found that the first response time was 448 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
lunchme.ru performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.6 s
8/100
25%
Value12.4 s
3/100
10%
Value1,430 ms
15/100
30%
Value0.147
77/100
15%
Value17.2 s
4/100
10%
448 ms
36 ms
244 ms
399 ms
163 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 53% of them (70 requests) were addressed to the original Lunchme.ru, 26% (34 requests) were made to Maps.googleapis.com and 8% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Lunchme.ru.
Page size can be reduced by 884.5 kB (19%)
4.8 MB
3.9 MB
In fact, the total size of Lunchme.ru main page is 4.8 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. 75% 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 92.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 92.3 kB or 83% of the original size.
Potential reduce by 163.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. Lunchme images are well optimized though.
Potential reduce by 522.7 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 522.7 kB or 68% of the original size.
Potential reduce by 106.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. Lunchme.ru needs all CSS files to be minified and compressed as it can save up to 106.2 kB or 87% of the original size.
Number of requests can be reduced by 42 (35%)
121
79
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lunchme. 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 10 to 1 for CSS and as a result speed up the page load time.
lunchme.ru
448 ms
css
36 ms
styles.css
244 ms
jquery-1.11.1.min.js
399 ms
socialShare.js
163 ms
jquery.mCustomScrollbar.css
326 ms
jquery-ui.css
170 ms
style_tree.css
172 ms
styles_select.css
244 ms
css
67 ms
styles-block-search.css
252 ms
prettyphoto.css
257 ms
jquery-ui.min.js
481 ms
ui.js
429 ms
ui-select.js
336 ms
ui-tree.js
343 ms
jquery.mCustomScrollbar.concat.min.js
492 ms
js
55 ms
richmarker-compiled.js
429 ms
mapsData.js
598 ms
jquery.prettyphoto.js
472 ms
fon-headr.jpg
352 ms
logo.png
97 ms
google_pl.png
138 ms
app.png
145 ms
icon-spoon-fork.png
150 ms
social2.png
174 ms
arrow-up.png
263 ms
ph1.png
442 ms
vk-share.png
263 ms
tw-share.png
263 ms
fb-share.png
283 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
23 ms
RjgO7rYTmqiVp7vzi-Q5UT8E0i7KZn-EPnyo3HZu7kw.woff
15 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
26 ms
k3k702ZOKiLJc3WVjuplzIraN7vELC11_xip9Rz-hMs.woff
20 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
28 ms
icons.png
157 ms
select-arrow.png
156 ms
b-tree-decor.png
164 ms
tree-chek.png
246 ms
card.png
247 ms
wifi.png
248 ms
fon-search.png
250 ms
map-search.png
256 ms
icon-close.png
301 ms
analytics.js
59 ms
common.js
37 ms
map.js
37 ms
util.js
100 ms
geocoder.js
37 ms
controls.js
39 ms
places_impl.js
36 ms
kitchens.php
248 ms
restserver.php
98 ms
restserver.php
93 ms
slider-pointer.png
256 ms
collect
68 ms
onion.js
32 ms
openhand_8_8.cur
100 ms
ViewportInfoService.GetViewportInfo
131 ms
stats.js
75 ms
infowindow.js
67 ms
css
36 ms
transparent.png
60 ms
powered-by-google-on-white3.png
60 ms
autocomplete-icons.png
61 ms
google4.png
61 ms
mapcnt6.png
62 ms
sv5.png
62 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
35 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
36 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
36 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
36 ms
tmapctrl.png
42 ms
tmapctrl4.png
44 ms
imgs8.png
43 ms
vt
56 ms
vt
107 ms
vt
49 ms
vt
73 ms
vt
66 ms
vt
70 ms
vt
89 ms
vt
102 ms
vt
121 ms
vt
121 ms
vt
125 ms
vt
139 ms
vt
152 ms
vt
170 ms
vt
165 ms
vt
169 ms
vt
172 ms
vt
200 ms
vt
206 ms
vt
210 ms
vt
214 ms
public.php
250 ms
share.php
266 ms
AuthenticationService.Authenticate
179 ms
overlay.js
51 ms
20150401153942.jpg
487 ms
20150401153103.jpg
481 ms
20150331133509.jpg
407 ms
20150401151741.jpg
516 ms
20150401144828.jpg
483 ms
20150401143717.jpg
547 ms
20150401143247.jpg
731 ms
20150326110734.jpg
799 ms
20150401142903.jpg
723 ms
20150401141042.jpg
729 ms
20150401141326.jpg
772 ms
20150401140727.jpg
797 ms
20150326163840.jpg
888 ms
20150329130140.jpg
891 ms
20150401132929.jpg
892 ms
20150401135120.jpg
1029 ms
20150326083814.jpg
966 ms
20150401130119.jpg
956 ms
20150401131625.jpg
1044 ms
20150401093033.jpg
972 ms
fon-rating.png
974 ms
sprite2.png
1036 ms
wifi_web.png
1048 ms
cards_web.png
1053 ms
lunch_more.png
1053 ms
share.php
199 ms
20150127132108.png
1088 ms
map-point.png
1093 ms
20150127132149.png
1096 ms
20150127131836.png
1106 ms
lunchme.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
lunchme.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lunchme.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lunchme.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 Lunchme.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.
lunchme.ru
Open Graph data is detected on the main page of Lunchme. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: