25.9 sec in total
499 ms
24.9 sec
425 ms
Welcome to econ.lenobl.ru homepage info - get ready to check Econ Lenobl best content for Russia right away, or after learning these important things about econ.lenobl.ru
Комитет экономического развития и инвестиционной деятельности ЛО: новости, общая информация, направления работы и документы
Visit econ.lenobl.ruWe analyzed Econ.lenobl.ru page load time and found that the first response time was 499 ms and then it took 25.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
econ.lenobl.ru performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value10.7 s
0/100
25%
Value27.5 s
0/100
10%
Value1,280 ms
18/100
30%
Value0.207
60/100
15%
Value29.2 s
0/100
10%
499 ms
2895 ms
469 ms
625 ms
930 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 77% of them (56 requests) were addressed to the original Econ.lenobl.ru, 10% (7 requests) were made to Pos.gosuslugi.ru and 7% (5 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Stat.sputnik.ru.
Page size can be reduced by 1.1 MB (29%)
3.8 MB
2.7 MB
In fact, the total size of Econ.lenobl.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. 60% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 619.4 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 165.4 kB, which is 24% 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 619.4 kB or 90% of the original size.
Potential reduce by 269.5 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. Econ Lenobl images are well optimized though.
Potential reduce by 0 B
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 235.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. Econ.lenobl.ru needs all CSS files to be minified and compressed as it can save up to 235.2 kB or 75% of the original size.
Number of requests can be reduced by 24 (44%)
54
30
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Econ Lenobl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
econ.lenobl.ru
499 ms
econ.lenobl.ru
2895 ms
jquery-ui.f0afdea84832.css
469 ms
bootstrap.min.52266d6c5059.css
625 ms
style.16c39b67d887.css
930 ms
audioplayer.6212eac05c2d.css
466 ms
font-awesome.min.269550530cc1.css
469 ms
jquery-3.3.1.slim.min.a09e13ee94d5.js
307 ms
jquery-1.10.2.min.628072e7212d.js
466 ms
script.min.js
594 ms
671 ms
493 ms
bootstrap.ba101e5651d6.js
477 ms
jquery-ui.min.8cbf62fc0208.js
864 ms
jquery.ellipsis.min.d08f4080deff.js
470 ms
polls.61caf5dca59b.js
624 ms
fotorama.24f286f263a6.js
628 ms
scripts.22add0cd3f8f.js
864 ms
soundmanager2-nodebug-jsmin.83f8f4a73604.js
651 ms
ui.audioplayer.cd3679b8877a.js
861 ms
el-masonry.d18f3572033d.js
862 ms
mediaelement-and-player.661d0c117aa4.js
1022 ms
me-i18n-locale-ru.b7b14d3e9822.js
1020 ms
agency_main_banners.0004eb65907b.js
1020 ms
gosuslugi-logo.svg
194 ms
%D0%BE%D0%B1%D0%BB%D0%BE%D0%B6%D0%BA%D0%B0_900_1.svg
978 ms
gerb.5b476f22c1de.svg
200 ms
vk.23d3db70625a.svg
203 ms
telegram.9c5a5ce011ac.svg
202 ms
ok.c3ebf3ee8c7a.svg
354 ms
eye_new2.0ca7fa1ca0b0.svg
350 ms
user.71301bac0bdd.svg
348 ms
appeal.d06c57b23415.svg
351 ms
close.6593be38e040.svg
355 ms
gerb_mob.63295623ff4a.svg
351 ms
burger-menu.6797ebb4c832.svg
505 ms
carousel-prev-btn.75140108cd5e.svg
584 ms
carousel-next-btn.4195cfccb927.svg
582 ms
brandbook.svg
504 ms
9d5b739c6908ed2de60aa495a3edfe96.png
962 ms
fcd29a52c218603f66bb955337b06d24.png
1151 ms
ba7ad48352b94c19afbe0ec7f8fa5eb6.png
814 ms
332344a28235529f462da74fcd32cc94.png
965 ms
aa42f22bf5daddd667c189b881d3dd55.png
906 ms
0ac9cc3450cf84c4d68e21af32ea4169.png
890 ms
2c7f1067e934cd76b722dc2299a2d839.png
972 ms
113442cce10d5dd05dbd0161d22393ab.png
1197 ms
a021ca33627c21a7fea79edc3ccb9ee0.png
1066 ms
31cac7c801ba59b2b3c42bc19cf7684a.png
1118 ms
a14b9e79907be4ae08704f876ba25b6a.png
1122 ms
lenobl_gerb.0b0203cd6965.svg
1127 ms
ASMR_1456x180.gif
1279 ms
PTSans-Regular.096c2e929368.woff
1190 ms
PTSans-Bold.b22afc9b53e2.woff
1248 ms
fontawesome-webfont.woff
1248 ms
fontawesome-webfont.fee66e712a8a.woff
1270 ms
view
307 ms
Lato-Regular.woff
1033 ms
Lato-Bold.woff
1013 ms
full-834306d5db5f8be221970cfe95d51754b7962be8.js
1242 ms
tag.js
1017 ms
cnt.js
20490 ms
slick.woff
1030 ms
app2.css
124 ms
app_widget_legacy.2d8e1d174fee980228b9603fb4c58a8c.js
961 ms
fontawesome-webfont.ttf
281 ms
slick.ttf
200 ms
grab.cur
141 ms
grabbing.cur
155 ms
help.cur
295 ms
zoom_in.cur
410 ms
fontawesome-webfont.svg
162 ms
slick.svg
154 ms
econ.lenobl.ru accessibility score
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
<frame> or <iframe> elements do not have a title
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
econ.lenobl.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
econ.lenobl.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Econ.lenobl.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Econ.lenobl.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.
econ.lenobl.ru
Open Graph description is not detected on the main page of Econ Lenobl. 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: