5.8 sec in total
418 ms
5.2 sec
153 ms
Click here to check amazing Obit content for Russia. Otherwise, check out these important facts you probably never knew about obit.ru
Компания ОБИТ — оператор ИТ-решений, предлагает комплексные цифровые и телекоммуникационные решения для бизнеса в Москве, Санкт-Петербурге, Казани и еще в 80 городах России. ОБИТ предоставляет ИТ-аутс...
Visit obit.ruWe analyzed Obit.ru page load time and found that the first response time was 418 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
obit.ru performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value10.4 s
0/100
25%
Value7.8 s
24/100
10%
Value1,180 ms
21/100
30%
Value0.089
92/100
15%
Value16.6 s
5/100
10%
418 ms
549 ms
263 ms
269 ms
270 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 59% of them (30 requests) were addressed to the original Obit.ru, 16% (8 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Mc.yandex.ru.
Page size can be reduced by 574.2 kB (60%)
950.1 kB
375.8 kB
In fact, the total size of Obit.ru main page is 950.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. 45% of websites need less resources to load. Javascripts take 722.0 kB which makes up the majority of the site volume.
Potential reduce by 46.0 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 46.0 kB or 68% of the original size.
Potential reduce by 5.2 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. Obit images are well optimized though.
Potential reduce by 475.7 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 475.7 kB or 66% of the original size.
Potential reduce by 47.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. Obit.ru needs all CSS files to be minified and compressed as it can save up to 47.4 kB or 82% of the original size.
Number of requests can be reduced by 25 (64%)
39
14
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Obit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
obit.ru
418 ms
www.obit.ru
549 ms
core.css
263 ms
style.css
269 ms
styles.css
270 ms
template_styles.css
271 ms
core.js
687 ms
core_ajax.js
560 ms
session.js
393 ms
jquery.min.js
28 ms
style.css
800 ms
prettyCheckable.css
402 ms
jquery.fancybox.css
536 ms
uppod_api.js
523 ms
swf.js
672 ms
jquery-1.10.2.min.js
930 ms
jquery-migrate-1.2.1.min.js
545 ms
vendor.js
581 ms
jquery.fancybox.pack.js
826 ms
prettyCheckable.min.js
680 ms
jquery.maskedinput.min.js
693 ms
main.js
708 ms
addthis_widget.js
9 ms
css
26 ms
css
40 ms
marker_dropdown-arrow.png
142 ms
logo.jpg
137 ms
network.jpg
140 ms
wifi.jpg
135 ms
online.jpg
386 ms
gen-manager.jpg
344 ms
send-gen-manager.jpg
345 ms
marker_dialog.png
345 ms
marker_dev-studio-oblako.png
346 ms
analytics.js
22 ms
watch.js
311 ms
RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf
41 ms
MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf
54 ms
k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf
67 ms
nYLRMYzK_pmfzPnjxWqmnw.ttf
78 ms
MLKvhAbswThSVACnSTWCp6CWcynf_cDxXwCLxiixG1c.ttf
80 ms
X_EdMnknKUltk57alVVbV6CWcynf_cDxXwCLxiixG1c.ttf
80 ms
oxrPYIm05JrY_0rFIEQ_oaCWcynf_cDxXwCLxiixG1c.ttf
66 ms
collect
13 ms
collect
63 ms
300lo.json
58 ms
counter.8eb9e83b9fa0d4af1e4f.js
11 ms
sh.7c7179124ea24ac6ba46caac.html
36 ms
watch.js
3145 ms
shares.json
8 ms
obit.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
obit.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
Page has valid source maps
obit.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Obit.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 Obit.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.
obit.ru
Open Graph description is not detected on the main page of Obit. 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: