4.1 sec in total
722 ms
3.2 sec
212 ms
Click here to check amazing Public content for Russia. Otherwise, check out these important facts you probably never knew about public.ru
АО «Публичная библиотека» предоставляет сервисы «электронная библиотека периодики» и «мониторинг СМИ»
Visit public.ruWe analyzed Public.ru page load time and found that the first response time was 722 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
public.ru performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value5.0 s
27/100
25%
Value4.1 s
78/100
10%
Value660 ms
45/100
30%
Value0.014
100/100
15%
Value6.5 s
58/100
10%
722 ms
147 ms
267 ms
272 ms
423 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 68% of them (49 requests) were addressed to the original Public.ru, 17% (12 requests) were made to Search.public.ru and 7% (5 requests) were made to Openstat.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Public.ru.
Page size can be reduced by 213.5 kB (50%)
427.1 kB
213.5 kB
In fact, the total size of Public.ru main page is 427.1 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. 35% of websites need less resources to load. Javascripts take 189.7 kB which makes up the majority of the site volume.
Potential reduce by 32.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. 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 32.5 kB or 77% of the original size.
Potential reduce by 36.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. Obviously, Public needs image optimization as it can save up to 36.3 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 130.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 130.0 kB or 69% of the original size.
Potential reduce by 14.7 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. Public.ru needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 74% of the original size.
Number of requests can be reduced by 30 (43%)
69
39
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
public.ru
722 ms
common.css
147 ms
forms.css
267 ms
gradients.css
272 ms
common.js
423 ms
common.js
270 ms
ajax.js
277 ms
window.js
277 ms
sources.js
401 ms
forms.js
415 ms
xtcore.js
408 ms
hit.xiti
318 ms
login_external2.pu
484 ms
top100.cnt
250 ms
w2.gif
247 ms
logo.png
134 ms
services_icons.png
155 ms
PR_red.gif
148 ms
Demodostup.gif
165 ms
menu-close.png
149 ms
diletant2014.bmp
287 ms
2016.02.19_Digital_100x100.gif
405 ms
LKV_100x100.gif
421 ms
2016.05.31_mmr_100x100.gif
414 ms
buttons5.jpg
295 ms
newresearch.gif
309 ms
34920923102011.jpg
434 ms
olympic.jpg
438 ms
itogi_2013.gif
452 ms
blog.gif
556 ms
no_on.jpg
561 ms
arctika.gif
557 ms
pressa-4.jpg
584 ms
vubory_icon1.jpg
578 ms
foul_language_anons.jpg
725 ms
anons_portret_goda.jpg
692 ms
books.jpg
695 ms
serebranii_lucnik.jpg
698 ms
meeting_anons.jpg
717 ms
putin_i_medvedev.jpg
729 ms
social2011.gif
831 ms
banner_video_public.gif
833 ms
160316.png
968 ms
lypa.gif
853 ms
vector-info.jpg
864 ms
b468x60.gif
865 ms
amr.gif
964 ms
aif.gif
972 ms
sovetnik.gif
1052 ms
soob.gif
1058 ms
hit
253 ms
iamik.gif
1029 ms
cnt.js
374 ms
911544.js
122 ms
16021016_jquery.js
274 ms
16021016_pub.js
264 ms
16021016_collapse.js
266 ms
16021016_dropdownMenu.js
264 ms
16021016_systemMessage.js
271 ms
16021016_common.js
287 ms
16021016_login_ext2.css
393 ms
16021016_cookies.js
394 ms
16021016_placeholder.js
396 ms
forms.css
461 ms
gradients.css
470 ms
16021016_form.js
405 ms
16021016_login.js
404 ms
91.gif
122 ms
cnt
240 ms
f.gif
122 ms
counter
263 ms
YIVPBiRvSZSv_iJm1KAr1w
116 ms
public.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
Links do not have a discernible name
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.
public.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
public.ru SEO score
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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Public.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 Public.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.
public.ru
Open Graph description is not detected on the main page of Public. 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: