21.1 sec in total
537 ms
14.3 sec
6.2 sec
Click here to check amazing Orel Mts content for Russia. Otherwise, check out these important facts you probably never knew about orel.mts.ru
Актуальные новости не только о тарифах и услугах связи, но и новых продуктах МТС: цифровых приложениях для работы и отдыха, ТВ и медиа, финансовых сервисах, технологиях для запуска и продвижения бизне...
Visit orel.mts.ruWe analyzed Orel.mts.ru page load time and found that the first response time was 537 ms and then it took 20.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
orel.mts.ru performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value41.6 s
0/100
25%
Value45.7 s
0/100
10%
Value86,020 ms
0/100
30%
Value0.01
100/100
15%
Value109.7 s
0/100
10%
537 ms
302 ms
582 ms
1180 ms
1285 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 23% of them (23 requests) were addressed to the original Orel.mts.ru, 56% (55 requests) were made to Static.mts.ru and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Static.mts.ru.
Page size can be reduced by 271.4 kB (38%)
711.2 kB
439.8 kB
In fact, the total size of Orel.mts.ru main page is 711.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% 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. HTML takes 299.5 kB which makes up the majority of the site volume.
Potential reduce by 241.5 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 46.2 kB, which is 15% 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 241.5 kB or 81% of the original size.
Potential reduce by 8.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 21.3 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. Orel.mts.ru has all CSS files already compressed.
Number of requests can be reduced by 49 (54%)
91
42
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orel Mts. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
personal
537 ms
shared_mts16.css
302 ms
base_personal.css
582 ms
shared_personal.css
1180 ms
shared_static.css
1285 ms
banners-v2.css
1287 ms
startPage.css
1309 ms
headsection-es5.js
385 ms
polyfills-es5.js
1279 ms
zone-es5.js
520 ms
zone-es2015.js
517 ms
globals-es5.js
1070 ms
globals-es2015.js
1070 ms
profile-widget.bundle.js
2667 ms
moduleCreator-es5.js
1278 ms
base-es5.js
2716 ms
startPage-es5.js
2662 ms
qaScripts-es5.js
517 ms
layout-es2015.js
2664 ms
layout-es5.js
1894 ms
api_dynamic.js
220 ms
api_static.js
232 ms
banners-es5.js
1045 ms
media.css
2635 ms
poll.css
1226 ms
pollWidget-es5.js
1149 ms
pollWidget-es2015.js
1203 ms
sspBanner-es5.js
2588 ms
banners-es5.js
2588 ms
mainPage-es2015.js
2621 ms
mainPage-es5.js
2614 ms
mtsmoney-export-1.0.min.css
2510 ms
mtsmoney-export-1.0.min.js
2541 ms
gtm.js
1840 ms
warning.svg
1587 ms
logo.svg
1622 ms
a-pay.svg
1623 ms
a-pay-white.svg
1620 ms
g-pay.svg
1653 ms
g-pay-light.svg
1621 ms
visa.svg
1836 ms
visa-light.svg
1835 ms
mastercard.svg
1838 ms
mir.svg
1837 ms
lk.svg
1884 ms
app-store.svg
1897 ms
app-store-light.svg
1988 ms
google-play.svg
1907 ms
google-play-light.svg
2011 ms
app-gallery.svg
1953 ms
app-gallery-light.svg
1926 ms
sim.svg
2049 ms
premium-plus.svg
2398 ms
kion-logo.svg
2375 ms
books.svg
2377 ms
2_Memory_.svg
2403 ms
music.svg
2400 ms
footer-moy-mts-qr.svg
2404 ms
app-store.svg
2531 ms
google-play.svg
2534 ms
app-gallery.svg
2575 ms
st
1233 ms
arrow_gray.svg
1040 ms
purse.svg
1031 ms
help.svg
1032 ms
arrow_black.svg
1033 ms
MTSSans-Medium__W.woff
524 ms
MTSSans-Regular__W.woff
524 ms
MTSSans-Bold__W.woff
595 ms
MTSSans-Black__W.woff
594 ms
MTSSans-UltraWide__W.woff
582 ms
search.svg
583 ms
close.svg
585 ms
cart.svg
584 ms
dy-coll-nojq-min.js
320 ms
tag.js
885 ms
arrow-down-gray.svg
271 ms
my-mts.svg
211 ms
kion.svg
1589 ms
img-1-5.svg
372 ms
img-2-3.svg
193 ms
img-3-2.svg
310 ms
books.svg
308 ms
connect.svg
373 ms
music.svg
347 ms
cashback.svg
262 ms
all-2.svg
345 ms
analytics.js
1520 ms
collect
229 ms
collect
290 ms
sync_cookie_image_decide
174 ms
collect
68 ms
collect
57 ms
collect
55 ms
1
178 ms
1
235 ms
ga-audiences
142 ms
advert.gif
471 ms
orel.mts.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.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
<object> elements do not have alternate text
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.
orel.mts.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
Missing source maps for large first-party JavaScript
orel.mts.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Orel.mts.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 Orel.mts.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.
orel.mts.ru
Open Graph description is not detected on the main page of Orel Mts. 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: