9.1 sec in total
515 ms
8.4 sec
188 ms
Visit orf.ru now to see the best up-to-date Orf content for Russia and also check out these interesting facts you probably never knew about orf.ru
Интернет-магазин
Visit orf.ruWe analyzed Orf.ru page load time and found that the first response time was 515 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
orf.ru performance score
name
value
score
weighting
Value11.2 s
0/100
10%
Value17.5 s
0/100
25%
Value11.2 s
5/100
10%
Value1,220 ms
20/100
30%
Value0.387
27/100
15%
Value14.4 s
9/100
10%
515 ms
1203 ms
29 ms
504 ms
2767 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 90% of them (72 requests) were addressed to the original Orf.ru, 4% (3 requests) were made to Mc.yandex.com and 3% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Orf.ru.
Page size can be reduced by 2.7 MB (13%)
21.3 MB
18.6 MB
In fact, the total size of Orf.ru main page is 21.3 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. 75% 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 18.6 MB which makes up the majority of the site volume.
Potential reduce by 146.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 27.3 kB, which is 16% 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 146.2 kB or 87% of the original size.
Potential reduce by 671.6 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. Orf images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 69% of the original size.
Potential reduce by 898.6 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. Orf.ru needs all CSS files to be minified and compressed as it can save up to 898.6 kB or 83% of the original size.
Number of requests can be reduced by 21 (28%)
76
55
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
orf.ru
515 ms
orf.ru
1203 ms
css
29 ms
ui.design-tokens.min.css
504 ms
template_9d7057d9f80296c2b68787beb1c2d980_v1.css
2767 ms
popup.min.css
506 ms
core.min.js
1043 ms
kernel_main_v1.js
978 ms
protobuf.min.js
626 ms
model.min.js
628 ms
core_promise.min.js
631 ms
rest.client.min.js
751 ms
pull.client.min.js
880 ms
core_ls.min.js
757 ms
jquery-2.2.4.min.js
1002 ms
ajax.min.js
883 ms
cphttprequest.min.js
1006 ms
template_7dc8130ed7c747681ec3fa47efc99233_v1.js
2523 ms
ba.js
306 ms
b682375ba44c8e41b90f77711abd418e.png
253 ms
37ad50384ff57efd4a97f576e953c655.png
231 ms
ae014b3404fe37b983ab7e1a91e19cbc.png
231 ms
c77fa419304630eb192786726053b71a.png
233 ms
b95ae7277fd00f68122ca9ba3c7c4378.png
233 ms
a8e5661469eb5854183130784c7901ab.png
232 ms
5dbfebb484d9be01e0123f671fcf48c7.png
255 ms
4a177850b02951545a8c9799d272e14f.png
253 ms
2b310037b9ea14cdb5048e72a5d15f4b.png
254 ms
5a75b8e6d5243088b1acd64a4fc4282f.png
260 ms
295f00aabd04119731ba7ca97c60d1bd.png
279 ms
72abd6c1be6bf0dfa042ef39df89ec28.png
377 ms
c7d63f22d67bae6641ad33bb94988c27.png
377 ms
88b6788448590785d120710eaadb140e.png
378 ms
ec04686dff16efd481c141e457f369b9.png
1891 ms
5fbf9acb97230cff9b69f6bc3490d27c.png
1302 ms
505be1ed12745e2fa4b14c548dfdb2c3.png
557 ms
af42ed437b91e0a765bc0ffdd098f9b9.png
627 ms
adbfd015857f1042663edceafc4aa508.png
501 ms
fd1e4ea07f95af126c4d900281331a68.jpg
1130 ms
eed56671d370296d5e1d9a6443ce959f.jpg
1004 ms
4ccdcf2dcc22c09c44276bf376162fc3.jpg
2929 ms
c298252579a0f7a551ae978c0f4620f8.jpg
1130 ms
c639433fa564dbe7dc75779fcb059090.jpg
1131 ms
abd38c2d8cb366b6b44446fd9be47432.jpg
1383 ms
b68fca811bad60ad7c871d4e401d96a0.jpg
1256 ms
4facc3819612d54417a43c820d5889be.jpg
1257 ms
00ae3dcb029776f98e734ef65465e4b3.jpg
1383 ms
92632af786dd0631564dc9ca9a0977a9.jpg
1385 ms
7538.jpg
4167 ms
7749.jpg
1511 ms
772.jpg
1635 ms
682.jpg
1636 ms
478.jpg
1768 ms
442.jpg
1762 ms
tag.js
778 ms
354.jpg
1764 ms
font
50 ms
fontawesome-webfont.woff
1663 ms
302.jpg
1687 ms
240.jpg
1797 ms
8740.jpg
3553 ms
8473.jpg
1787 ms
8164.jpg
1773 ms
8050.jpg
1896 ms
7988.jpg
1901 ms
7955.jpg
1902 ms
Search_black_sm.svg
2016 ms
Close_mask.svg
2003 ms
bx_stat
185 ms
Phone_black.svg
1905 ms
next.png
2024 ms
Search_big_mask.svg
2029 ms
pl3.gif
1906 ms
01ff13cfbfe9b9a89820d47be9a3e7e6.jpg
1972 ms
8ed8b6ab77a75e6ae0363374ff8875cb.jpg
1906 ms
advert.gif
638 ms
ai.png
1528 ms
social.png
1525 ms
sync_cookie_image_decide
136 ms
1
134 ms
orf.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
orf.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
orf.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
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orf.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 Orf.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.
orf.ru
Open Graph data is detected on the main page of Orf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: