24.6 sec in total
537 ms
23.7 sec
314 ms
Click here to check amazing DURAY content for Russia. Otherwise, check out these important facts you probably never knew about duray.ru
Светодиодные светильники для офисных и производственных помещений общественных и муниципальных учреждений: производство, продажа, сервис, гарантийное обслуживание.
Visit duray.ruWe analyzed Duray.ru page load time and found that the first response time was 537 ms and then it took 24 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
duray.ru performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value17.8 s
0/100
25%
Value25.0 s
0/100
10%
Value2,800 ms
3/100
30%
Value0.813
4/100
15%
Value17.8 s
4/100
10%
537 ms
1475 ms
135 ms
17 ms
19 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 68% of them (79 requests) were addressed to the original Duray.ru, 11% (13 requests) were made to Api-maps.yandex.ru and 10% (12 requests) were made to Core-renderer-tiles.maps.yandex.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Bitrix.duray.ru.
Page size can be reduced by 852.9 kB (24%)
3.5 MB
2.6 MB
In fact, the total size of Duray.ru main page is 3.5 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. 75% 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. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 575.9 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 575.9 kB or 85% of the original size.
Potential reduce by 254.8 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. DURAY images are well optimized though.
Potential reduce by 3.8 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 3.8 kB or 14% of the original size.
Potential reduce by 18.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. Duray.ru needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 38% of the original size.
Number of requests can be reduced by 38 (37%)
103
65
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DURAY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
duray.ru
537 ms
duray.ru
1475 ms
stylesheet.css
135 ms
jquery-latest.js
17 ms
jquery-migrate-1.0.0.js
19 ms
jquery.lightbox.css
267 ms
reset.css
399 ms
font.css
400 ms
colorbox.css
402 ms
colorbox.js
402 ms
jquery.fancybox.pack.js
404 ms
jquery.carouFredSel.min.js
536 ms
jquery.lightbox.js
532 ms
lib.js
533 ms
present.js
532 ms
561 ms
jquery.bxslider.min.js
534 ms
jquery.bxslider.css
540 ms
jquery.fancybox.css
665 ms
owl.carousel.css
664 ms
carousel.js
810 ms
core.min.css
667 ms
page_3c28dc53fa10bd95fb248bc76825f661_v1.css
678 ms
template_bd261081e07bbf12d3ef086b254a0c3c_v1.css
815 ms
core.min.js
966 ms
kernel_main_v1.js
936 ms
callibri.js
1247 ms
template_becef9f4b61d9de6f403bc3a99df5ebf_v1.js
941 ms
page_c88acbce9c982335d9b6bc639a5efd6f_v1.js
824 ms
jquery.form.min.js
942 ms
slidebars.min.css
948 ms
slidebars.min.js
958 ms
238 ms
map.js
249 ms
combine.js
729 ms
combine.js
996 ms
ba.js
367 ms
analytics.js
60 ms
phone.png
206 ms
email.png
201 ms
menu_icon.png
205 ms
logo_orange.svg
203 ms
1f62efc1df141fb13b6ce5ba97f2de69.png
275 ms
324f751db4985d8405f59d0b7119d51d.png
275 ms
61a93ec739af78228f3ef15d03cf81ea.jpg
532 ms
e9c1a9d5439592a385baa86dfb3074db.jpg
269 ms
3c5c8275ca6919d8abe6d325e4f9b782.png
536 ms
cross_blue.png
273 ms
youtube-soc.svg
411 ms
telegram-soc.png
413 ms
vk-soc.svg
415 ms
070824dfc961bedc9668ad4b9f9ab00a.png
501 ms
03b57e5d68a06544fd36c2d5d06ebeb3.png
494 ms
0bcc618c0e737509effac98ea08e6f29.jpg
640 ms
c806e930f317de6ccfe52f434fe26183.jpg
499 ms
e83a69b95fa9069c1dbd1d9074b1689d.jpg
638 ms
40f415cabd34e3a5b33d29be9c553538.png
758 ms
b3d3d81bb432011ff13d36e83f69475c.jpg
638 ms
8ce1f38e177f01bf5e59ed4c87106c41.png
639 ms
52a52217debf0b6b0ce89ececffcf090.jpg
640 ms
de6a3a58f75479bc3f81a96fb22143d2.jpg
758 ms
ubuntu-c.ttf
954 ms
ubuntu-r.ttf
1134 ms
collect
123 ms
975507b1b341f1edba8b74072be7d78c.png
1102 ms
5d2f7464a1bff352afef6f3476afbd7a.jpg
737 ms
33a497e2a43c52fc3dffcb40be9a7f60.jpg
878 ms
17829b964429ad53a96d4ca4b9adbeed.jpg
879 ms
fd071b6bb103a9d53c6700d6f766689e.jpg
880 ms
cb912a570236262b81382dd0e3d09891.jpg
1100 ms
acd8771552de93314d97ae970c1d9ce1.jpg
1100 ms
5084cd64800163aa25f697c858927173.jpg
1101 ms
b91420a95235d5adb502114592c673d9.jpg
1102 ms
7e35827d7975d941cfeab560b2433a9a.jpg
1161 ms
80aa54fbd03d0d046e87bd3f091275cb.jpg
1162 ms
watch.js
111 ms
call.tracker.js
20363 ms
loader_1_t7mlvn.js
20364 ms
js
76 ms
457275f5ca8acaf6c7515f7dd1ba5942.jpg
1038 ms
c1debe841c9d751f7b593a83b11306c4.jpg
1037 ms
89b8d142617a59fa608e160e71c5fd48.jpg
1036 ms
fa31b366cb20108376bbd4f3c06d74a4.jpg
1035 ms
c891e619fd9686c3b67c964c75e05529.jpg
1070 ms
2d331a6a414739c35d43a808f9aa734d.jpg
1067 ms
fbc98cf9766d49e6dc16f70a1edee3ab.jpg
1070 ms
1ca4d4f9214a161366b2a1c33265a1f9.jpg
1073 ms
bx_stat
191 ms
d77b71486982de00324c5bdda569bd8a.jpg
943 ms
2e9c152288aa39aab766fc93949eaf96.jpg
941 ms
fotorama.png
1056 ms
d17a694050cad4c6731519a23dcd8cb9.png
1167 ms
baa620771a17ec1713197a8f1914dea0.jpg
1165 ms
d9ffec5f1c34e14c200ee30b13e08e0d.jpg
1164 ms
number
859 ms
util_cursor_storage_grab.cur
276 ms
util_cursor_storage_grabbing.cur
225 ms
util_cursor_storage_help.cur
284 ms
util_cursor_storage_zoom_in.cur
286 ms
tiles
892 ms
tiles
1057 ms
tiles
1277 ms
tiles
1358 ms
combine.js
182 ms
147 ms
tiles
1377 ms
tiles
1358 ms
tiles
1488 ms
tiles
1424 ms
tiles
1456 ms
combine.js
444 ms
tiles
1500 ms
tiles
1544 ms
tiles
1551 ms
166 ms
duray_placemark4.png
164 ms
duray.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
button, link, and menuitem elements 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
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.
duray.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
duray.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 Duray.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 Duray.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.
duray.ru
Open Graph description is not detected on the main page of DURAY. 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: