5.1 sec in total
452 ms
4.6 sec
103 ms
Welcome to dme.ru homepage info - get ready to check Dme best content for Russia right away, or after learning these important things about dme.ru
Официальный сайт Московского аэропорта Домодедово. Онлайн-табло. Расписание рейсов. Актуальная информация о рейсах. Контакты авиакомпаний.
Visit dme.ruWe analyzed Dme.ru page load time and found that the first response time was 452 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
dme.ru performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value5.1 s
25/100
25%
Value8.0 s
22/100
10%
Value720 ms
41/100
30%
Value0.001
100/100
15%
Value12.2 s
15/100
10%
452 ms
784 ms
261 ms
482 ms
371 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 77% of them (46 requests) were addressed to the original Dme.ru, 7% (4 requests) were made to Top-fwz1.mail.ru and 5% (3 requests) were made to Bitrix.dme.ru. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Dme.ru.
Page size can be reduced by 863.6 kB (23%)
3.7 MB
2.9 MB
In fact, the total size of Dme.ru main page is 3.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. 45% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 434.7 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 434.7 kB or 78% of the original size.
Potential reduce by 378.9 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. Obviously, Dme needs image optimization as it can save up to 378.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 49.9 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 49.9 kB or 15% of the original size.
Potential reduce by 127 B
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. Dme.ru needs all CSS files to be minified and compressed as it can save up to 127 B or 55% of the original size.
Number of requests can be reduced by 32 (57%)
56
24
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
dme.ru
452 ms
dme.ru
784 ms
css
261 ms
css
482 ms
visioweb
371 ms
PaidServicesCss
385 ms
jquery
521 ms
jqueryui
770 ms
daterangepicker
758 ms
visioglobeSDK
1454 ms
visioglobe
520 ms
es5-shims.min.js
469 ms
share.js
703 ms
scripts
944 ms
utils.js
700 ms
PaidServicesJs
543 ms
opensansregular.svg
152 ms
shadow_left.png
147 ms
shadow_right.png
146 ms
3diuvhqe.png
147 ms
GLAZ.png
317 ms
dmestore-home-banner_DPT.png
255 ms
%D0%9F%D1%80%D0%BE%D0%B2%D0%BE%D0%B4%D0%B8%D0%BC%20%D0%B7%D0%B0%20%D0%92%D0%B0%D1%81%20%D0%BF%D1%80%D0%B0%D0%B2%D0%BA%D0%B8%20%D1%82%D0%B5%D0%BA%D1%81%D1%82%20JPEG.jpg
373 ms
%D0%92%D1%81%D1%82%D1%80%D0%B5%D1%82%D0%B8%D0%BC%20%D0%B7%D0%B0%20%D0%92%D0%B0%D1%81%20%D0%BF%D1%80%D0%B0%D0%B2%D0%BA%D0%B8%20%D1%82%D0%B5%D0%BA%D1%81%D1%82%20JPEG.jpg
233 ms
dmestore-FastTrack-banner_DPT.png
386 ms
Frame%203615%20(1).png
1130 ms
%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80%20%D0%BD%D0%B0%20%D1%81%D0%B0%D0%B9%D1%82%20(%D0%BF%D1%80%D0%B5%D0%B4%D0%BE%D1%81%D1%82%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5%20%D1%81%D0%BA%D0%B8%D0%B4%D0%BA%D0%B8).png
470 ms
dmestore-lounge-banner_DPT.png
653 ms
ststus_reisa.jpg
712 ms
wusyndgu_147x148.png
517 ms
watch.png
508 ms
ounaz43p_147x148.png
606 ms
tudnp5df_147x148.png
628 ms
aeroexpress_logo.svg
647 ms
p4cxe0lb.png
722 ms
oosmrkq3.png
718 ms
LUPA.png
739 ms
TG.PNG
747 ms
VK.PNG
806 ms
INST.PNG
830 ms
opensansregular.woff
836 ms
YOUTUBE.PNG
860 ms
projbapf_crop955x278.jpg
876 ms
animate_btn.png
922 ms
form_sprite.png
970 ms
switch_arrow.png
972 ms
tag.js
992 ms
script.js
138 ms
hit
535 ms
code.js
764 ms
shadow_bottom.png
976 ms
loader_1_tbfmc0.js
854 ms
loader_2_azekbc.js
897 ms
sync-loader.js
951 ms
counter
153 ms
dyn-goal-config.js
262 ms
call.tracker.js
150 ms
advert.gif
534 ms
print.css
125 ms
tracker
128 ms
dme.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
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
Document doesn't have a <title> element
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
dme.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
Page has valid source maps
dme.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dme.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 Dme.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.
dme.ru
Open Graph description is not detected on the main page of Dme. 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: