4.1 sec in total
486 ms
2.8 sec
773 ms
Click here to check amazing Inostranka content for Russia. Otherwise, check out these important facts you probably never knew about inostranka.ru
Новости журнала "Иностранная литература" - публикации, новые номера, события
Visit inostranka.ruWe analyzed Inostranka.ru page load time and found that the first response time was 486 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
inostranka.ru performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value7.1 s
6/100
25%
Value9.6 s
11/100
10%
Value110 ms
97/100
30%
Value0.229
54/100
15%
Value11.5 s
18/100
10%
486 ms
134 ms
254 ms
256 ms
256 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 98% of them (80 requests) were addressed to the original Inostranka.ru, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Inostranka.ru.
Page size can be reduced by 319.2 kB (19%)
1.7 MB
1.4 MB
In fact, the total size of Inostranka.ru main page is 1.7 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. 35% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 47.1 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 47.1 kB or 80% of the original size.
Potential reduce by 247.7 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, Inostranka needs image optimization as it can save up to 247.7 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 22.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 22.3 kB or 31% of the original size.
Potential reduce by 2.1 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. Inostranka.ru needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 19% of the original size.
Number of requests can be reduced by 50 (63%)
80
30
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inostranka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
inostranka.ru
486 ms
style.css
134 ms
css_browser_selector.js
254 ms
navigation-c9b658bd-ef70-1844-ed1e-082ba0940105.css
256 ms
navigation.css
256 ms
jquery.min.js
378 ms
text-9b1379b4-952d-6b86-0905-c81a79246417.css
258 ms
text.css
264 ms
text.js
386 ms
text-9902c85b-83f1-c3a7-73b1-93d03b26cc37.css
387 ms
text-c9eecd16-e800-fa67-6e4e-bf4d2b83e7e4.css
387 ms
text-963dea6c-8886-5151-a44d-c2f0ce11e5b9.css
387 ms
jquery.jcarousellite.js
394 ms
jquery.simplemodal.js
509 ms
imagegallery.js
514 ms
imagegallery.css
512 ms
imagegallery.locale-ru_RU.js
515 ms
css
24 ms
text-7c8d1f72-360f-de68-deb2-636c8f919dad.css
520 ms
text-b7784614-f550-2619-8406-bce4bda9c2a1.css
524 ms
text-2ed4517b-086c-7ff3-5719-11a6aa731492.css
640 ms
navigation-bf3d3b2e-e990-242e-d6bb-5aad58e7da51.css
642 ms
text-85fab2d3-260f-99b4-9173-320270688eec.css
642 ms
text-be3bb4da-1d54-8008-eaf0-c1df14703e92.css
644 ms
text-c8923655-ebb0-6267-ccc2-f0cdc2f08cbc.css
653 ms
text-d8345245-0129-1b99-31d1-10a874f180b1.css
652 ms
layout.css
770 ms
helpers.js
773 ms
view.js
774 ms
anti_cache.js
854 ms
external-border-none-top-left.png
135 ms
external-border-none-top-right.png
133 ms
external-border-none-top.png
135 ms
external-border-none-top-left2.png
136 ms
external-border-none-top-right2.png
134 ms
external-border-none-left.png
137 ms
external-border-none-left-top.png
263 ms
external-border-none-left-bottom.png
264 ms
external-border-none-right.png
266 ms
external-border-none-right-top.png
265 ms
external-border-none-right-bottom.png
265 ms
external-border-none-bottom-left.png
266 ms
external-border-none-bottom-right.png
394 ms
external-border-none-bottom.png
396 ms
external-border-none-bottom-left2.png
395 ms
external-border-none-bottom-right2.png
398 ms
border-none-top-left.png
397 ms
border-none-top-right.png
396 ms
border-none-top.png
527 ms
border-none-left.png
527 ms
border-none-right.png
525 ms
menu-toggle.png
528 ms
image.psd-1_1.png
765 ms
border-none-bottom-left.png
526 ms
border-none-bottom-right.png
657 ms
border-none-bottom.png
655 ms
IL-2024-04-oblozhka_1.jpg
1426 ms
IL-2024-03-oblozhka.jpg
1142 ms
cb2be92a45e20b1a18919f4fec8f4e14.png
1386 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
11 ms
f47467c2-29a5-5924-b924-62fc5cb5ea03.thumb.jpg
698 ms
c23078cb-97a4-1c13-7766-96eeafc47b34.thumb.jpg
698 ms
1141abf5-d555-3146-8f7a-ca3046b9427a.thumb.jpg
805 ms
00a72065-0248-10f7-42b1-ee747ee8e875.thumb.jpg
825 ms
f1b14c59-a7cd-1d84-7c5f-38f81a57d668.thumb.jpg
827 ms
d62641fb-d244-0d3a-803e-d1e943f636c7.thumb.jpg
936 ms
ed365a0b-5693-61f0-0b93-b68db7648421.thumb.jpg
957 ms
6463079b-ba8b-13cc-1202-93d0bec8da79.thumb.jpg
921 ms
5fac4caa-598f-372a-6364-811684cca450.thumb.jpg
1028 ms
992c2354-e889-3179-e518-16b9b4f26e2c.thumb.jpg
1049 ms
66ff96b3-56ae-c3af-7e6d-126e9a19f44e.thumb.jpg
1048 ms
c53f0fc0-48d7-e25a-b0d9-32f8409f1fd4.thumb.jpg
1140 ms
b4dc3464-8e7e-3532-008b-badef385f900.thumb.jpg
1156 ms
1b4d2d58-730b-76b5-d12b-83131544e723.thumb.jpeg
1050 ms
a7782775-0c9a-4d1c-038b-653593bdcf04.thumb.jpg
1050 ms
e9741cae-a936-d8b4-8368-f51c2c5fed23.thumb.jpg
1142 ms
ba681654-96b7-a0f6-266f-bb827a860fdf.thumb.jpg
1157 ms
f20d8db2-3032-14a3-2fc9-bb083b178382.thumb.jpg
1177 ms
a655b9c0-a282-b56c-f354-f73d23baf91e.thumb.jpg
1179 ms
3024464a-35f7-3a24-b7e9-ba231a771b89.thumb.jpg
1127 ms
3c338f0a-9fab-0742-dd50-4efac60e4e90.thumb.jpg
1140 ms
60c6c908-63be-ef65-fa35-a4fbe782a1a5.thumb.jpg
1157 ms
inostranka.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.
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
inostranka.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
inostranka.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inostranka.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 Inostranka.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.
inostranka.ru
Open Graph description is not detected on the main page of Inostranka. 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: