7.2 sec in total
516 ms
6.3 sec
424 ms
Click here to check amazing Itime content. Otherwise, check out these important facts you probably never knew about itime.ru
Конструктор договоров: онлайн сервис для создания и ведения любого типа документов. На сайте можно: Создать и настроить юридические документы; Посмотреть шаблоны и образцы заполнения; Получить бесплат...
Visit itime.ruWe analyzed Itime.ru page load time and found that the first response time was 516 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
itime.ru performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value9.0 s
1/100
25%
Value15.1 s
1/100
10%
Value2,720 ms
3/100
30%
Value0
100/100
15%
Value21.9 s
1/100
10%
516 ms
816 ms
175 ms
1109 ms
36 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Itime.ru, 65% (43 requests) were made to Freshdoc.ru and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Freshdoc.ru.
Page size can be reduced by 117.3 kB (11%)
1.1 MB
971.2 kB
In fact, the total size of Itime.ru main page is 1.1 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. 80% 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. Javascripts take 794.4 kB which makes up the majority of the site volume.
Potential reduce by 50.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 10.8 kB, which is 17% 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 50.5 kB or 78% of the original size.
Potential reduce by 20.9 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, Itime needs image optimization as it can save up to 20.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 44.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 1.0 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. Itime.ru has all CSS files already compressed.
Number of requests can be reduced by 29 (48%)
60
31
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Itime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
itime.ru
516 ms
index.php
816 ms
www.quickdoc.ru
175 ms
www.freshdoc.ru
1109 ms
css
36 ms
compiled.min.css.gz
262 ms
compiled.min.css.gz
475 ms
config.js
481 ms
compiled.min.js.gz
977 ms
compiled.min.js.gz
745 ms
page_41f45bade255bd309cd37e23f5369dfd_ca5583ff8251bb052345c071360c808d.css
492 ms
kernel_main.css
494 ms
kernel_main.js
892 ms
css.php
615 ms
js.php
1015 ms
compiled.min.js.gz
2267 ms
cookie-mess.js
743 ms
compiled.min.css.gz
877 ms
qd-logo-freshdoc.png
177 ms
SUB-BAN-2021-022%20(12).svg
178 ms
qd-tiles-slide-1.png
139 ms
qd-tiles-slide-2.png
282 ms
qd-tiles-slide-4.png
177 ms
qd-tiles-slide-5.png
136 ms
qd-tiles-slide-6.png
283 ms
qd-tiles-slide-3.png
283 ms
tag.js
1174 ms
cloud.png
241 ms
sub-menu-arrow.svg
239 ms
Y9VjycNlRf4
223 ms
contracts.png
215 ms
hr.png
722 ms
claims.png
721 ms
nevsky.png
721 ms
bankrotroot.png
721 ms
warrants.png
721 ms
OOO.png
721 ms
AO.png
886 ms
IP.png
1013 ms
accounting.png
880 ms
individuals.png
1012 ms
protection.png
880 ms
auto.png
877 ms
qd-mastercard.png
946 ms
qd-visa.png
947 ms
qd-social-bar.png
946 ms
qd-social-bar-youb.png
947 ms
qd-social-bar-zenb.png
974 ms
ga.js
20 ms
analytics.js
87 ms
login-arrow.svg
843 ms
www-player.css
35 ms
www-embed-player.js
55 ms
base.js
86 ms
collect
411 ms
ad_status.js
265 ms
xk0PjXGe3Weoch_wsJrbTmMShFu5SdJ84GkfFnEjZYE.js
188 ms
embed.js
79 ms
collect
230 ms
js
236 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
154 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
155 ms
id
112 ms
Create
121 ms
ga-audiences
136 ms
GenerateIT
19 ms
itime.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
itime.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
Missing source maps for large first-party JavaScript
itime.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
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 Itime.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 Itime.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.
itime.ru
Open Graph data is detected on the main page of Itime. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: