6 sec in total
503 ms
5.2 sec
308 ms
Visit marte.ru now to see the best up-to-date Marte content for Russia and also check out these interesting facts you probably never knew about marte.ru
Занятия танцами в Москве - школа танцев
Visit marte.ruWe analyzed Marte.ru page load time and found that the first response time was 503 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
marte.ru performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value11.5 s
0/100
25%
Value10.9 s
6/100
10%
Value2,530 ms
4/100
30%
Value0.199
62/100
15%
Value19.2 s
2/100
10%
503 ms
797 ms
135 ms
35 ms
46 ms
Our browser made a total of 175 requests to load all elements on the main page. We found that 39% of them (69 requests) were addressed to the original Marte.ru, 24% (42 requests) were made to Fonts.gstatic.com and 10% (18 requests) were made to Core-renderer-tiles.maps.yandex.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Marte.ru.
Page size can be reduced by 924.7 kB (24%)
3.8 MB
2.9 MB
In fact, the total size of Marte.ru main page is 3.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. 70% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 301.1 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 301.1 kB or 82% of the original size.
Potential reduce by 283.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. Obviously, Marte needs image optimization as it can save up to 283.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 337.4 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 337.4 kB or 33% of the original size.
Potential reduce by 2.6 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. Marte.ru needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 15% of the original size.
Number of requests can be reduced by 55 (44%)
124
69
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marte. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
marte.ru
503 ms
marte.ru
797 ms
styles.css
135 ms
font-awesome.min.css
35 ms
css2
46 ms
jquery-2.2.4.js
408 ms
jquery.maskedinput.min.js
401 ms
jquery.min.js
28 ms
tinycarousel.css
401 ms
jquery.tinycarousel.js
400 ms
main.js
401 ms
form.js
404 ms
jquery.tablesorter.min.js
534 ms
jquery.fancybox.css
533 ms
jquery.fancybox.pack.js
535 ms
jquery.cookie.min.js
467 ms
733 ms
jquery.cookie.js
537 ms
slick.min.js
537 ms
max.js
539 ms
slick.css
665 ms
slick-theme.css
665 ms
max.css
666 ms
media.css
666 ms
api.js
44 ms
web.css
669 ms
api.js
64 ms
alloka.js
762 ms
full-f7aad75f4136fd546efbbe29908f2112821adcbc.js
1026 ms
fbevents.js
71 ms
rtrg
473 ms
recaptcha__en.js
122 ms
gtm.js
163 ms
bg.jpg
241 ms
logo2.png
275 ms
metro.png
239 ms
phone.png
239 ms
connector.php
321 ms
connector.php
281 ms
connector.php
389 ms
connector.php
698 ms
connector.php
521 ms
connector.php
545 ms
schedule_child.png
415 ms
schedule_adult.png
455 ms
connector.php
806 ms
connector.php
567 ms
connector.php
606 ms
connector.php
935 ms
connector.php
697 ms
connector.php
780 ms
connector.php
781 ms
connector.php
802 ms
connector.php
848 ms
connector.php
864 ms
connector.php
909 ms
connector.php
956 ms
connector.php
2388 ms
connector.php
1384 ms
connector.php
1242 ms
connector.php
1243 ms
connector.php
1243 ms
connector.php
1107 ms
connector.php
1524 ms
connector.php
1462 ms
connector.php
1398 ms
connector.php
1401 ms
connector.php
1549 ms
connector.php
1495 ms
recaptcha__ru.js
141 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
96 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
204 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
220 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
221 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
221 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
219 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
224 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
225 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
225 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
221 ms
KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff
224 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
224 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
234 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
236 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
235 ms
KFOlCnqEu92Fr1MmSU5fChc-AMP6lbBP.woff
233 ms
KFOlCnqEu92Fr1MmSU5fCxc-AMP6lbBP.woff
234 ms
KFOlCnqEu92Fr1MmSU5fBxc-AMP6lbBP.woff
236 ms
KFOlCnqEu92Fr1MmSU5fCBc-AMP6lbBP.woff
236 ms
KFOlCnqEu92Fr1MmSU5fABc-AMP6lbBP.woff
236 ms
KFOlCnqEu92Fr1MmSU5fCRc-AMP6lbBP.woff
237 ms
KFOkCnqEu92Fr1MmgVxIIzQXKMny.woff
237 ms
KFOkCnqEu92Fr1MmgVxGIzQXKMnyrYk.woff
238 ms
KFOkCnqEu92Fr1MmgVxHIzQXKMnyrYk.woff
238 ms
KFOkCnqEu92Fr1MmgVxLIzQXKMnyrYk.woff
239 ms
KFOkCnqEu92Fr1MmgVxEIzQXKMnyrYk.woff
238 ms
KFOkCnqEu92Fr1MmgVxMIzQXKMnyrYk.woff
239 ms
KFOkCnqEu92Fr1MmgVxFIzQXKMnyrYk.woff
240 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
241 ms
KFOlCnqEu92Fr1MmWUlfChc-AMP6lbBP.woff
240 ms
KFOlCnqEu92Fr1MmWUlfCxc-AMP6lbBP.woff
239 ms
KFOlCnqEu92Fr1MmWUlfBxc-AMP6lbBP.woff
240 ms
KFOlCnqEu92Fr1MmWUlfCBc-AMP6lbBP.woff
241 ms
KFOlCnqEu92Fr1MmWUlfABc-AMP6lbBP.woff
241 ms
KFOlCnqEu92Fr1MmWUlfCRc-AMP6lbBP.woff
242 ms
KFOlCnqEu92Fr1MmYUtfBBc-AMP6lQ.woff
244 ms
hit
578 ms
bundle.min.js
174 ms
modal.css
570 ms
KFOlCnqEu92Fr1MmYUtfChc-AMP6lbBP.woff
152 ms
KFOlCnqEu92Fr1MmYUtfCxc-AMP6lbBP.woff
45 ms
connector.php
1291 ms
next_pre.png
1433 ms
line.png
1432 ms
KFOlCnqEu92Fr1MmYUtfBxc-AMP6lbBP.woff
30 ms
KFOlCnqEu92Fr1MmYUtfCBc-AMP6lbBP.woff
30 ms
KFOlCnqEu92Fr1MmYUtfABc-AMP6lbBP.woff
31 ms
KFOlCnqEu92Fr1MmYUtfCRc-AMP6lbBP.woff
30 ms
aboniment.png
1399 ms
time_les.png
1393 ms
concertmeister.png
1369 ms
near_metro.png
1345 ms
price.png
1351 ms
border_title.png
1344 ms
video.png
1279 ms
sprites2.png
1276 ms
telegram3.png
1300 ms
widget.js
51 ms
tag.js
886 ms
fallback
107 ms
ajax-loader.gif
1163 ms
fallback__ltr.css
4 ms
css
17 ms
logo_48.png
4 ms
grab.cur
250 ms
grabbing.cur
248 ms
help.cur
440 ms
zoom_in.cur
428 ms
699 ms
tiles
871 ms
720 ms
867 ms
937 ms
961 ms
962 ms
1009 ms
1007 ms
1010 ms
1059 ms
1096 ms
1101 ms
1115 ms
1123 ms
1135 ms
tiles
1008 ms
tiles
1172 ms
tiles
1330 ms
tiles
1371 ms
tiles
1337 ms
tiles
1364 ms
tiles
1357 ms
tiles
1379 ms
tiles
1526 ms
tiles
1555 ms
tiles
1524 ms
tiles
1567 ms
tiles
1562 ms
tiles
1556 ms
tiles
1716 ms
273 ms
advert.gif
699 ms
tiles
927 ms
sync_cookie_image_decide
148 ms
tiles
738 ms
1
135 ms
marte.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
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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>).
marte.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
marte.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
Tap targets are not sized appropriately
![]()
RU
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Marte.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 Marte.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.
marte.ru
Open Graph description is not detected on the main page of Marte. 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: