4 sec in total
565 ms
3 sec
454 ms
Click here to check amazing Document content for Russia. Otherwise, check out these important facts you probably never knew about document.ru
Бюро переводов «Документ.ру», одно из динамично развивающихся агентств переводов в Москве и Московской области. Наше бюро выполнит юридический перевод, технический перевод текстов, окажет услуги устно...
Visit document.ruWe analyzed Document.ru page load time and found that the first response time was 565 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
document.ru performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value6.0 s
13/100
25%
Value7.3 s
29/100
10%
Value580 ms
51/100
30%
Value0.011
100/100
15%
Value6.4 s
59/100
10%
565 ms
732 ms
10 ms
323 ms
186 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 70% of them (39 requests) were addressed to the original Document.ru, 9% (5 requests) were made to Google-analytics.com and 4% (2 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (848 ms) belongs to the original domain Document.ru.
Page size can be reduced by 263.3 kB (64%)
408.5 kB
145.3 kB
In fact, the total size of Document.ru main page is 408.5 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. 25% of websites need less resources to load. Javascripts take 322.7 kB which makes up the majority of the site volume.
Potential reduce by 23.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 4.1 kB, which is 13% 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 23.5 kB or 77% of the original size.
Potential reduce by 252 B
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. Document images are well optimized though.
Potential reduce by 219.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 219.9 kB or 68% of the original size.
Potential reduce by 19.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. Document.ru needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 82% of the original size.
Number of requests can be reduced by 31 (70%)
44
13
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Document. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
document.ru
565 ms
www.document.ru
732 ms
watch.js
10 ms
267704199.js
323 ms
general.css
186 ms
content.css
654 ms
dhtmlgoodies_calendar.css
659 ms
swfobject.js
667 ms
dhtmlgoodies_calendar.js
651 ms
linkedselect.js
667 ms
script.js
664 ms
swfobject_modified.js
848 ms
top100.jcn
838 ms
urchin.js
85 ms
tracker.js
842 ms
typograph.css
202 ms
analytics.js
111 ms
get_flash_player.gif
105 ms
w7.gif
333 ms
top_corner_left.gif
201 ms
empty.gif
202 ms
horizontal_ruler.gif
197 ms
top_space_center.gif
201 ms
second_corner_left.gif
198 ms
second.gif
199 ms
second_space_center.gif
342 ms
vertical_ruler.gif
348 ms
left.gif
350 ms
doc_logo.jpg
351 ms
tel.jpg
346 ms
map.jpg
352 ms
mail.jpg
477 ms
1.png
498 ms
2.png
497 ms
3.png
494 ms
marker.gif
490 ms
img_1.jpg
493 ms
mp_notary.jpg
604 ms
mp_apostille.jpg
629 ms
mp_interpretation.jpg
641 ms
main_between.gif
640 ms
list_dots.gif
648 ms
main_space_left_two.gif
646 ms
main_space.gif
776 ms
main_space_center.gif
802 ms
bottom_dots.gif
809 ms
search.gif
810 ms
top100.scn
194 ms
collect
79 ms
hit
316 ms
__utm.gif
125 ms
watch.js
1 ms
collect
124 ms
collect
184 ms
ga-audiences
68 ms
hit
132 ms
document.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
<object> elements do not have alternate text
document.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
document.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
Document uses plugins
RU
EN
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Document.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Document.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.
document.ru
Open Graph description is not detected on the main page of Document. 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: