7.4 sec in total
536 ms
6.4 sec
446 ms
Welcome to comdi.ru homepage info - get ready to check COMDI best content right away, or after learning these important things about comdi.ru
Платформа COMDI. Заказать проведение онлайн трансляций — профессиональное проведение трансляций мероприятий под ключ ✅ Выгодные цены ✅ Качество услуг ✅ Профессиональная техническая поддержка
Visit comdi.ruWe analyzed Comdi.ru page load time and found that the first response time was 536 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
comdi.ru performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value7.1 s
5/100
25%
Value15.1 s
1/100
10%
Value6,380 ms
0/100
30%
Value0.252
49/100
15%
Value28.7 s
0/100
10%
536 ms
167 ms
302 ms
469 ms
303 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Comdi.ru, 10% (7 requests) were made to Api-maps.yandex.ru and 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Comdi.com.
Page size can be reduced by 396.3 kB (26%)
1.5 MB
1.1 MB
In fact, the total size of Comdi.ru main page is 1.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. 55% of websites need less resources to load. Images take 935.8 kB which makes up the majority of the site volume.
Potential reduce by 125.6 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 125.6 kB or 65% of the original size.
Potential reduce by 19.5 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. COMDI images are well optimized though.
Potential reduce by 170.1 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 170.1 kB or 62% of the original size.
Potential reduce by 81.1 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. Comdi.ru needs all CSS files to be minified and compressed as it can save up to 81.1 kB or 81% of the original size.
Number of requests can be reduced by 30 (51%)
59
29
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of COMDI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.comdi.com
536 ms
lp3-home.css
167 ms
normalize.css
302 ms
style.css
469 ms
social-likes.css
303 ms
totop.css
321 ms
jquery.min.js
490 ms
286 ms
openapi.js
481 ms
Base64.js
320 ms
SEOhide.js
465 ms
jquery.easing.1.3.js
480 ms
jquery.mousewheel.js
516 ms
jquery.ulslide.js
505 ms
jquery.quovolver.js
602 ms
jquery.roundabout.js
594 ms
jquery.event.drag-2.2.js
607 ms
jquery.event.drop-2.2.js
605 ms
main.js
616 ms
easing.js
623 ms
totop.js
733 ms
814 ms
combine.xml
1346 ms
all.js
217 ms
widgets.js
407 ms
logo.png
216 ms
s1.png
1020 ms
s2.png
2125 ms
s3.png
368 ms
s4.png
3328 ms
tabBook.png
762 ms
partners.png
590 ms
sobakaru.png
565 ms
citroen.png
1643 ms
mslogo.png
1467 ms
footerBook.png
2200 ms
footerBookMiddl.png
1465 ms
facebook-small.png
1563 ms
vkontakte-small.png
1644 ms
youtube-small.png
1700 ms
webinar.png
1813 ms
gtm.js
210 ms
sprite.png
2834 ms
bgMainBanner.jpg
3079 ms
sprite_big.png
2229 ms
play-button.png
2260 ms
CalculateDecor.png
2364 ms
DownloadBook.png
2434 ms
chevinpro-medium.svg
2283 ms
chevinpro-bold.svg
2349 ms
chevinpro-light.svg
2580 ms
dc.js
317 ms
watch.js
12 ms
conversion.js
144 ms
423 ms
xd_arbiter.php
189 ms
xd_arbiter.php
1348 ms
290 ms
j.php
103 ms
v.gif
44 ms
__utm.gif
122 ms
2821 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
171 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
228 ms
4965b66fe115b2f2ed500ece66514d86.cur
401 ms
77492cf358d8b12629399322926c93f2.cur
926 ms
ping
142 ms
comdi.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-*] attributes do not match their roles
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
comdi.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
comdi.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 Comdi.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 Comdi.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.
comdi.ru
Open Graph description is not detected on the main page of COMDI. 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: