Tools & Wizards About Us
nlr.ru screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

nlr.ru

Российская национальная библиотека, Санкт-Петербург

Page Load Speed

4.7 sec in total

First Response

852 ms

Resources Loaded

3.4 sec

Page Rendered

353 ms

nlr.ru screenshot

About Website

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.ru

Key Findings

We analyzed Nlr.ru page load time and found that the first response time was 852 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

nlr.ru performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

nlr.ru

852 ms

bootstrap.min.css

521 ms

horizontal.css

391 ms

custom_new.css

393 ms

special.js

400 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 73% of them (60 requests) were addressed to the original Nlr.ru, 10% (8 requests) were made to Helper.nlr.ru and 6% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Nlr.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.7 kB (6%)

Content Size

3.4 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nlr.ru main page is 3.4 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. 80% 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. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 30.0 kB

  • Original 39.2 kB
  • After minification 35.8 kB
  • After compression 9.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. 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 30.0 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 167.8 kB

  • Original 2.9 MB
  • After minification 2.7 MB

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.

JavaScript Optimization

-1%

Potential reduce by 4.3 kB

  • Original 368.2 kB
  • After minification 368.2 kB
  • After compression 364.0 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.

CSS Optimization

-3%

Potential reduce by 2.6 kB

  • Original 89.0 kB
  • After minification 89.0 kB
  • After compression 86.4 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (26%)

Requests Now

74

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 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 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nlr.ru

nlr.ru

852 ms

bootstrap.min.css

bootstrap.min.css

521 ms

horizontal.css

horizontal.css

391 ms

custom_new.css

custom_new.css

393 ms

special.js

special.js

400 ms

js

js

51 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

388 ms

jquery-ui.min.js

jquery-ui.min.js

689 ms

bootstrap.min.js

bootstrap.min.js

348 ms

nlr_article_new2.js

nlr_article_new2.js

387 ms

plugins.js

plugins.js

416 ms

sly.min.js

sly.min.js

416 ms

horizontal2.js

horizontal2.js

485 ms

tag.js

tag.js

1076 ms

b1.php

b1.php

914 ms

b1.php

b1.php

919 ms

slide28.jpg

slide28.jpg

567 ms

krim1.jpg

krim1.jpg

538 ms

NA24247.png

NA24247.png

566 ms

NA84140.png

NA84140.png

689 ms

NA84638.jpg

NA84638.jpg

785 ms

NA84623.jpg

NA84623.jpg

565 ms

NA85234.jpg

NA85234.jpg

565 ms

NA85232.jpg

NA85232.jpg

777 ms

NA85223.jpg

NA85223.jpg

825 ms

NA84636.png

NA84636.png

776 ms

NA85230.jpg

NA85230.jpg

776 ms

NA84629.png

NA84629.png

776 ms

NA84142.png

NA84142.png

1040 ms

NA85242.jpg

NA85242.jpg

914 ms

NA84753.jpg

NA84753.jpg

914 ms

NA85244.jpg

NA85244.jpg

909 ms

NA85479.jpg

NA85479.jpg

1061 ms

vk.svg

vk.svg

954 ms

ok.png

ok.png

1055 ms

rutube.png

rutube.png

1056 ms

zen.svg

zen.svg

1059 ms

lj.svg

lj.svg

1125 ms

telegram.svg

telegram.svg

1169 ms

7Q2Sj_aczxs

7Q2Sj_aczxs

138 ms

OpenSans-Regular.woff2

OpenSans-Regular.woff2

1078 ms

golos-text_demibold.woff2

golos-text_demibold.woff2

1088 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1092 ms

OpenSans-Bold.woff2

OpenSans-Bold.woff2

1094 ms

faust3.jpg

faust3.jpg

1246 ms

NA85239.jpg

NA85239.jpg

1202 ms

NA85405.jpg

NA85405.jpg

1213 ms

NA85343.jpg

NA85343.jpg

1228 ms

NA85344.jpeg

NA85344.jpeg

1201 ms

NA85315.jpg

NA85315.jpg

1199 ms

NA85270.jpg

NA85270.jpg

1301 ms

www-player.css

www-player.css

7 ms

NA85060.jpeg

NA85060.jpeg

1241 ms

www-embed-player.js

www-embed-player.js

24 ms

base.js

base.js

48 ms

ad_status.js

ad_status.js

175 ms

client.php

client.php

640 ms

HJLpC_KsHO9WNnzI89ITV8EL_3UMlOCJVEGkvNJwaGU.js

HJLpC_KsHO9WNnzI89ITV8EL_3UMlOCJVEGkvNJwaGU.js

120 ms

embed.js

embed.js

54 ms

NA85131.jpg

NA85131.jpg

929 ms

NA84996.jpeg

NA84996.jpeg

907 ms

NA85340.jpg

NA85340.jpg

903 ms

NA85332.jpg

NA85332.jpg

913 ms

book12.png

book12.png

999 ms

natlib2.png

natlib2.png

1007 ms

id

id

96 ms

Create

Create

89 ms

rinc2.png

rinc2.png

913 ms

edu.png

edu.png

824 ms

grant2.png

grant2.png

825 ms

GenerateIT

GenerateIT

16 ms

chat.css

chat.css

133 ms

logo_nlr.png

logo_nlr.png

145 ms

close.gif

close.gif

144 ms

captcha.php

captcha.php

266 ms

advert.gif

advert.gif

615 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

422 ms

quadrat.gif

quadrat.gif

136 ms

golos-ui_medium.woff

golos-ui_medium.woff

492 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

503 ms

print.css

print.css

136 ms

sync_cookie_image_decide

sync_cookie_image_decide

126 ms

Accessibility Review

nlr.ru accessibility score

62

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

nlr.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

nlr.ru SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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 it matches the claimed language. Our system also found out that Nlr.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.

Social Sharing Optimization

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: