3.8 sec in total
464 ms
2.9 sec
416 ms
Welcome to dwg.ru homepage info - get ready to check DWG best content for Russia right away, or after learning these important things about dwg.ru
Инженерам, проектировщикам, конструкторам. Программы и блоки для AutoCAD. Чертежи, нормативная документация, доска объявления. Технологии и системы проектирования
Visit dwg.ruWe analyzed Dwg.ru page load time and found that the first response time was 464 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
dwg.ru performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value13.8 s
0/100
25%
Value10.6 s
7/100
10%
Value8,820 ms
0/100
30%
Value0.531
14/100
15%
Value17.1 s
4/100
10%
464 ms
279 ms
676 ms
433 ms
282 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 43% of them (40 requests) were addressed to the original Dwg.ru, 11% (10 requests) were made to Vk.com and 6% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Dwg.ru.
Page size can be reduced by 375.5 kB (30%)
1.3 MB
894.6 kB
In fact, the total size of Dwg.ru main page is 1.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. 55% of websites need less resources to load. Images take 710.2 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.0 kB or 76% of the original size.
Potential reduce by 11.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. DWG images are well optimized though.
Potential reduce by 256.2 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 256.2 kB or 61% of the original size.
Potential reduce by 70.3 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. Dwg.ru needs all CSS files to be minified and compressed as it can save up to 70.3 kB or 81% of the original size.
Number of requests can be reduced by 43 (50%)
86
43
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DWG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
dwg.ru
464 ms
jquery-ui.css
279 ms
jquery.min.js
676 ms
main.css
433 ms
form.css
282 ms
2743.js
283 ms
openapi.js
374 ms
brand
33 ms
adsbygoogle.js
14 ms
jquery-ui.min.js
953 ms
brand
60 ms
okno.gif
503 ms
1a.gif
141 ms
cr_lv1.gif
150 ms
spacer.gif
140 ms
penoplex_800_1.gif
140 ms
cr_l1.gif
310 ms
cr.gif
309 ms
cr_l.gif
308 ms
menu_hidden1.gif
311 ms
vetcad.gif
309 ms
dc13794_1.jpg
400 ms
dc13793_1.gif
405 ms
lm1623_1.jpg
412 ms
lm1613_1.jpg
409 ms
lm1617_1.jpg
550 ms
lm1619_1.jpg
550 ms
dc13785_1.jpg
558 ms
11523_1457014788.jpg
558 ms
31606_1457528680.jpg
694 ms
116220_1446206532.jpg
557 ms
bsk4782_1.jpg
693 ms
bsk4781_1.png
850 ms
bsk4780_1.jpg
694 ms
bsk4779_1.jpg
692 ms
antiq_h.jpg
697 ms
ksb_300_1.gif
830 ms
ascon_150_4.gif
1103 ms
antiq.png
967 ms
banner.gif
832 ms
aci.js
195 ms
upload.gif
282 ms
widget_community.php
391 ms
hit;AllDwg
278 ms
cr_lv.gif
822 ms
google_custom_search_watermark.gif
151 ms
views.png
900 ms
comments.png
904 ms
star_empty.png
918 ms
ca-pub-1987857910490103.js
54 ms
zrt_lookup.html
111 ms
show_ads_impl.js
59 ms
context.js
235 ms
ads
261 ms
osd.js
21 ms
106 ms
195 ms
177404.js
598 ms
ui-bg_flat_75_ffffff_40x100.png
687 ms
ui-icons_222222_256x240.png
802 ms
hit;AllDwg
128 ms
context_static_r1082.js
345 ms
276 ms
loader_nav19241_3.js
128 ms
lite.css
253 ms
lite.js
493 ms
lang3_0.js
251 ms
widget_community.css
256 ms
xdm.js
258 ms
al_community.js
255 ms
979051738990776190
78 ms
abg.js
44 ms
m_js_controller.js
43 ms
googlelogo_color_112x36dp.png
40 ms
s
30 ms
x_button_blue2.png
10 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
22 ms
match
227 ms
watch.js
4 ms
138863
250 ms
showad_full.js
269 ms
e_861f7136.jpg
411 ms
w_logo.png
120 ms
show_ads.js
5 ms
ads
241 ms
1x1.gif
199 ms
133288351503936442
32 ms
redir.html
74 ms
push
71 ms
adi
336 ms
iframe.html
28 ms
sync
53 ms
bidder.html
2 ms
dwg.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
dwg.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
Page has valid source maps
dwg.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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dwg.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 Dwg.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.
dwg.ru
Open Graph description is not detected on the main page of DWG. 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: