9.9 sec in total
305 ms
6.3 sec
3.2 sec
Welcome to rubook.org homepage info - get ready to check Rubook best content for Russia right away, or after learning these important things about rubook.org
Приветствуем Вас в нашей онлайн библиотеке. В библиотеке представлены различные жанры: проза, фантастика, детектив и многое другое.
Visit rubook.orgWe analyzed Rubook.org page load time and found that the first response time was 305 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rubook.org performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value6.4 s
9/100
25%
Value5.4 s
56/100
10%
Value1,340 ms
17/100
30%
Value0.005
100/100
15%
Value9.5 s
30/100
10%
305 ms
1246 ms
587 ms
46 ms
62 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rubook.org, 72% (105 requests) were made to Lyasse.ru and 14% (21 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Lyasse.ru.
Page size can be reduced by 1.8 MB (12%)
14.5 MB
12.7 MB
In fact, the total size of Rubook.org main page is 14.5 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. Only a small number of websites need less resources to load. Images take 14.2 MB which makes up the majority of the site volume.
Potential reduce by 180.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 52.3 kB, which is 26% 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 180.5 kB or 89% of the original size.
Potential reduce by 1.6 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. Obviously, Rubook needs image optimization as it can save up to 1.6 MB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 15 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 524 B
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. Rubook.org needs all CSS files to be minified and compressed as it can save up to 524 B or 16% of the original size.
Number of requests can be reduced by 15 (12%)
122
107
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rubook. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
rubook.org
305 ms
lyasse.ru
1246 ms
app.js
587 ms
swiper-bundle.min.js
46 ms
css
62 ms
css2
82 ms
css2
86 ms
css2
85 ms
swiper-bundle.min.css
47 ms
bootstrap.min.css
49 ms
bootstrap.bundle.min.js
59 ms
site.css
390 ms
e5b8335da0.js
89 ms
jquery-3.6.0.min.js
47 ms
star-rating.min.css
59 ms
theme.css
71 ms
star-rating.min.js
73 ms
theme.js
74 ms
ru.js
91 ms
2090 ms
512 ms
775 ms
576 ms
712 ms
898 ms
676 ms
740 ms
825 ms
1000 ms
918 ms
962 ms
1102 ms
1103 ms
1139 ms
1169 ms
1179 ms
1174 ms
1254 ms
1340 ms
1337 ms
1345 ms
1355 ms
1421 ms
1520 ms
1507 ms
1506 ms
1519 ms
1598 ms
1683 ms
1703 ms
1699 ms
1672 ms
1769 ms
1773 ms
tag.js
940 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-Y3tco5q6.ttf
28 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-Y3tco5q6.ttf
82 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-Y3tco5q6.ttf
106 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-Y3tco5q6.ttf
106 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-Y3tco5q6.ttf
111 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-Y3tco5q6.ttf
110 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-Y3tco5q6.ttf
110 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-Y3tco5q6.ttf
109 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-Y3tco5q6.ttf
109 ms
KFOmCnqEu92Fr1Me5WZNCzc.ttf
177 ms
KFOlCnqEu92Fr1MmEU9vAx0_IsE.ttf
111 ms
KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf
177 ms
KFOkCnqEu92Fr1MmgWxPKTU1Kg.ttf
176 ms
KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf
110 ms
KFOlCnqEu92Fr1MmYUtvAx0_IsE.ttf
176 ms
KFOkCnqEu92Fr1Mu52xPKTU1Kg.ttf
178 ms
KFOjCnqEu92Fr1Mu51S7ABc9AMP6lQ.ttf
178 ms
KFOjCnqEu92Fr1Mu51TjARc9AMP6lQ.ttf
179 ms
KFOiCnqEu92Fr1Mu51QrIzcXKMny.ttf
180 ms
KFOjCnqEu92Fr1Mu51TzBhc9AMP6lQ.ttf
179 ms
KFOjCnqEu92Fr1Mu51TLBBc9AMP6lQ.ttf
178 ms
1767 ms
1356 ms
1296 ms
1295 ms
1289 ms
1276 ms
1273 ms
1211 ms
1264 ms
1252 ms
1205 ms
1183 ms
1102 ms
1126 ms
1192 ms
advert.gif
634 ms
1155 ms
1189 ms
1178 ms
1140 ms
1106 ms
3060 ms
1194 ms
1180 ms
1085 ms
1074 ms
1128 ms
1159 ms
1208 ms
1115 ms
1057 ms
1127 ms
1170 ms
1161 ms
1125 ms
sync_cookie_image_decide
146 ms
1071 ms
1146 ms
1194 ms
1188 ms
1095 ms
1112 ms
1175 ms
1199 ms
1177 ms
1142 ms
1
148 ms
1099 ms
1223 ms
1205 ms
1228 ms
1205 ms
1168 ms
1248 ms
1220 ms
1229 ms
1242 ms
1199 ms
1298 ms
1229 ms
1223 ms
1219 ms
1170 ms
1307 ms
1225 ms
1209 ms
1207 ms
1197 ms
1265 ms
1246 ms
rubook.org 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.
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
rubook.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
rubook.org SEO score
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
![]()
EN
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rubook.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Russian language. Our system also found out that Rubook.org 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.
rubook.org
Open Graph description is not detected on the main page of Rubook. 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: