5.6 sec in total
526 ms
4.9 sec
173 ms
Visit nlr.ru now to see the best up-to-date Nlr content for Russia and also check out these interesting facts you probably never knew about nlr.ru
Официальный сайт Российской национальной библиотеки (Санкт-Петербург)
Visit nlr.ruWe analyzed Nlr.ru page load time and found that the first response time was 526 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nlr.ru performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value6.2 s
11/100
25%
Value4.1 s
78/100
10%
Value780 ms
37/100
30%
Value0.003
100/100
15%
Value6.7 s
56/100
10%
526 ms
969 ms
342 ms
362 ms
738 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 91% of them (43 requests) were addressed to the original Nlr.ru, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Helper.nlr.ru. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Nlr.ru.
Page size can be reduced by 220.0 kB (24%)
925.0 kB
704.9 kB
In fact, the total size of Nlr.ru main page is 925.0 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. 15% of websites need less resources to load. Images take 640.8 kB which makes up the majority of the site volume.
Potential reduce by 30.2 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 5.5 kB, which is 14% 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 30.2 kB or 77% of the original size.
Potential reduce by 29.3 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. Nlr images are well optimized though.
Potential reduce by 127.3 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 127.3 kB or 62% of the original size.
Potential reduce by 33.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. Nlr.ru needs all CSS files to be minified and compressed as it can save up to 33.2 kB or 82% of the original size.
Number of requests can be reduced by 13 (30%)
44
31
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nlr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
nlr.ru
526 ms
www.nlr.ru
969 ms
styles_gen.css
342 ms
menuvert-white.css
362 ms
b.php
738 ms
294 ms
start.gif
295 ms
search.gif
295 ms
sitemap.gif
296 ms
help.gif
296 ms
eng.gif
466 ms
zagl.jpg
730 ms
li_about.gif
863 ms
li_serv.gif
650 ms
li_news.gif
825 ms
logo_cinema.gif
779 ms
facebook.png
965 ms
twitter.png
1102 ms
rss.gif
1225 ms
logo_kont_24.png
1228 ms
live.png
1228 ms
you-tube.jpg
1232 ms
instagram.png
1361 ms
avtograf.jpg
1766 ms
lavr_man.jpg
2039 ms
litkarta.jpg
1912 ms
reg.jpg
2042 ms
expositions.jpg
2051 ms
all_spb.jpg
1911 ms
jquery-1.7.1.min.js
2719 ms
jquery.menuvert.js
2151 ms
jquery-ui.min.js
2907 ms
gen_page.js
2278 ms
watch.js
10 ms
natlib.jpg
2287 ms
attention.png
2292 ms
15.jpg
2903 ms
rba.jpg
2543 ms
ReadingStat.jpg
2557 ms
13796_m.jpeg
2561 ms
13795_m.jpeg
2853 ms
13783_m.jpeg
2883 ms
13737_m.jpeg
2617 ms
children.jpg
3173 ms
sign1.gif
2878 ms
ga.js
18 ms
__utm.gif
32 ms
nlr.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
nlr.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
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
Issues were logged in the Issues panel in Chrome Devtools
nlr.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nlr.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 Nlr.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
nlr.ru
Open Graph description is not detected on the main page of Nlr. 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: