6.5 sec in total
1.4 sec
4.8 sec
235 ms
Click here to check amazing Oc content for Russia. Otherwise, check out these important facts you probably never knew about oc.ru
В компании Оптимальные Коммуникации вы можете купить оборудование для телефонных станций, оптоволоконных АТС российского и зарубежного производства.
Visit oc.ruWe analyzed Oc.ru page load time and found that the first response time was 1.4 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
oc.ru performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value5.2 s
23/100
25%
Value5.9 s
47/100
10%
Value140 ms
96/100
30%
Value0.313
37/100
15%
Value6.1 s
63/100
10%
1423 ms
384 ms
193 ms
251 ms
131 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 63% of them (41 requests) were addressed to the original Oc.ru, 6% (4 requests) were made to Mc.yandex.ru and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Oc.ru.
Page size can be reduced by 294.0 kB (36%)
811.6 kB
517.6 kB
In fact, the total size of Oc.ru main page is 811.6 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. 30% of websites need less resources to load. Images take 536.4 kB which makes up the majority of the site volume.
Potential reduce by 55.6 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 25.4 kB, which is 39% 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 55.6 kB or 85% of the original size.
Potential reduce by 146.0 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, Oc needs image optimization as it can save up to 146.0 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 87.1 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 87.1 kB or 43% of the original size.
Potential reduce by 5.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. Oc.ru needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 75% of the original size.
Number of requests can be reduced by 22 (39%)
56
34
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oc. 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 as a result speed up the page load time.
www.oc.ru
1423 ms
sdh.min.css
384 ms
watch.js
193 ms
analytics.js
251 ms
z1.gif
131 ms
z2.gif
258 ms
z3.gif
2282 ms
z-bg1.gif
2902 ms
z5.gif
2178 ms
z6.gif
3062 ms
z7.gif
385 ms
top34.gif
501 ms
z81.gif
512 ms
z-bg5.gif
631 ms
z9.gif
638 ms
top41.gif
760 ms
top42.gif
767 ms
z-bg4.gif
891 ms
sp.gif
894 ms
bg4.gif
1020 ms
kn.gif
1021 ms
mn-hr.gif
1149 ms
postbox.jpg
1150 ms
ibp.gif
1281 ms
ats_3.gif
1281 ms
vorpost3.gif
1409 ms
menu_telecom.jpg
1548 ms
menu_electro.jpg
1538 ms
menu_cabtv.jpg
1795 ms
hit
256 ms
ga.js
5 ms
analytics.js
6 ms
__utm.gif
13 ms
watch.js
437 ms
collect
14 ms
collect
74 ms
mes5324-mainpage-pic.jpg
1574 ms
picture_mainpage_pic.jpg
1709 ms
picture_mainpage_pic.jpg
1819 ms
mes1124m-mainpage-pic.jpg
1839 ms
mes2124mb-mainpage-pic.jpg
1950 ms
rg-5421-g-wac-mainpage-pic.jpg
1969 ms
sbc-2000-mainpage-pic.jpg
2076 ms
smg-4-mainpage-pic.jpg
2100 ms
slider.min.js
2109 ms
esr-200-mainpage-pic.jpg
2126 ms
left-arrow.png
2154 ms
jquery.min.js
6 ms
shrn.png
1216 ms
analytics.js
253 ms
right-arrow.png
2155 ms
hit
130 ms
online
1059 ms
top100.jcn
368 ms
jquery.min.js
5 ms
online
1058 ms
jQuery1.2.6.js
2470 ms
picture_small_menu.jpg
2081 ms
online.gif
538 ms
online.gif
544 ms
online2.gif
185 ms
online2.gif
138 ms
top100.scn
127 ms
advert.gif
84 ms
1
86 ms
oc.ru accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
oc.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
oc.ru 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
Tap targets are not sized appropriately
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oc.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 Oc.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
oc.ru
Open Graph description is not detected on the main page of Oc. 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: