Tools & Wizards About Us
dikon.ru screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

dikon.ru

Главная - Дикон

Page Load Speed

5.7 sec in total

First Response

551 ms

Resources Loaded

4.7 sec

Page Rendered

405 ms

dikon.ru screenshot

About Website

Welcome to dikon.ru homepage info - get ready to check Dikon best content for Russia right away, or after learning these important things about dikon.ru

Дикон Групп — поставка промышленных комплектующих: газовых пружин, блокируемых газовых пружин, амортизаторов, демпферов, систем регулировки высоты стола, колес и роликов, механизмов трансформации мебе...

Visit dikon.ru

Key Findings

We analyzed Dikon.ru page load time and found that the first response time was 551 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

dikon.ru performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

Network Requests Diagram

dikon.ru

551 ms

dikon.ru

850 ms

font-awesome.css

139 ms

styles.css

549 ms

default.css

414 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 96% of them (75 requests) were addressed to the original Dikon.ru, 3% (2 requests) were made to Mc.yandex.com and 1% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (950 ms) belongs to the original domain Dikon.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.2 kB (8%)

Content Size

492.1 kB

After Optimization

451.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dikon.ru main page is 492.1 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. 45% of websites need less resources to load. Images take 255.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 36.6 kB

  • Original 44.7 kB
  • After minification 40.6 kB
  • After compression 8.1 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 36.6 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 255.0 kB
  • After minification 255.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. Dikon images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 156.3 kB
  • After minification 156.3 kB
  • After compression 154.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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 1.5 kB

  • Original 36.1 kB
  • After minification 36.1 kB
  • After compression 34.7 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. Dikon.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (46%)

Requests Now

71

After Optimization

38

  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dikon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

dikon.ru

dikon.ru

551 ms

dikon.ru

dikon.ru

850 ms

font-awesome.css

font-awesome.css

139 ms

styles.css

styles.css

549 ms

default.css

default.css

414 ms

jquery.jgrowl.min.css

jquery.jgrowl.min.css

416 ms

default.css

default.css

415 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

688 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

563 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

554 ms

owl.carousel.min.js

owl.carousel.min.js

729 ms

common.js

common.js

554 ms

js.js

js.js

682 ms

default.js

default.js

826 ms

jquery.jgrowl.min.js

jquery.jgrowl.min.js

704 ms

message_settings.js

message_settings.js

818 ms

default.js

default.js

823 ms

font-awesome.min.css

font-awesome.min.css

281 ms

jquery.fancybox.css

jquery.fancybox.css

301 ms

owl.carousel.min.css

owl.carousel.min.css

322 ms

owl.theme.default.min.css

owl.theme.default.min.css

411 ms

MuseoSans.css

MuseoSans.css

417 ms

jquery.jgrowl.min.css

jquery.jgrowl.min.css

138 ms

logo.png

logo.png

284 ms

banner1.webp

banner1.webp

284 ms

banner3.webp

banner3.webp

285 ms

banner4.webp

banner4.webp

284 ms

banner6.webp

banner6.webp

283 ms

wheels.da5c6684453b462480597540ed621943.49e24445bd4333648c16154b1110980b.jpg

wheels.da5c6684453b462480597540ed621943.49e24445bd4333648c16154b1110980b.jpg

284 ms

gas_springs_Liftline.da5c6684453b462480597540ed621943.49e24445bd4333648c16154b1110980b.jpg

gas_springs_Liftline.da5c6684453b462480597540ed621943.49e24445bd4333648c16154b1110980b.jpg

285 ms

mechanisms.da5c6684453b462480597540ed621943.49e24445bd4333648c16154b1110980b.jpg

mechanisms.da5c6684453b462480597540ed621943.49e24445bd4333648c16154b1110980b.jpg

285 ms

tabless.da5c6684453b462480597540ed621943.49e24445bd4333648c16154b1110980b.jpg

tabless.da5c6684453b462480597540ed621943.49e24445bd4333648c16154b1110980b.jpg

286 ms

l5.webp

l5.webp

288 ms

l6.webp

l6.webp

406 ms

l7.webp

l7.webp

412 ms

l11.webp

l11.webp

412 ms

l14.webp

l14.webp

413 ms

n26.09fe70282135aee84b664654f25ba52b.webp

n26.09fe70282135aee84b664654f25ba52b.webp

413 ms

bg.jpg

bg.jpg

417 ms

bg_header.jpg

bg_header.jpg

399 ms

icon_b2.png

icon_b2.png

400 ms

icon_b3.png

icon_b3.png

401 ms

icon_address.png

icon_address.png

401 ms

icon_phone.png

icon_phone.png

402 ms

icon_whatsapp.png

icon_whatsapp.png

534 ms

icon_mail.png

icon_mail.png

537 ms

bg_nav.png

bg_nav.png

540 ms

nav_sep.png

nav_sep.png

537 ms

icon_toggle.png

icon_toggle.png

538 ms

icon_search.png

icon_search.png

555 ms

block3.png

block3.png

670 ms

bg_title.png

bg_title.png

672 ms

a_bg.png

a_bg.png

674 ms

l13.png

l13.png

674 ms

a_sep.png

a_sep.png

675 ms

l1.png

l1.png

696 ms

l2.png

l2.png

808 ms

l3.png

l3.png

808 ms

l4.png

l4.png

681 ms

block4.jpg

block4.jpg

685 ms

MuseoSansCyrl-300.woff

MuseoSansCyrl-300.woff

818 ms

fontawesome-webfont.woff%3Fv=4.7.0

fontawesome-webfont.woff%3Fv=4.7.0

717 ms

MuseoSansCyrl-700.woff

MuseoSansCyrl-700.woff

815 ms

MuseoSansCyrl-900.woff

MuseoSansCyrl-900.woff

815 ms

MuseoSansCyrl-100.woff

MuseoSansCyrl-100.woff

950 ms

tag.js

tag.js

840 ms

jquery.form.min.js

jquery.form.min.js

823 ms

advert.gif

advert.gif

673 ms

sync_cookie_image_decide

sync_cookie_image_decide

186 ms

banner1.webp

banner1.webp

139 ms

banner3.webp

banner3.webp

276 ms

banner4.webp

banner4.webp

139 ms

banner6.webp

banner6.webp

277 ms

l5.webp

l5.webp

141 ms

l6.webp

l6.webp

137 ms

l7.webp

l7.webp

257 ms

l11.webp

l11.webp

274 ms

l14.webp

l14.webp

276 ms

Accessibility Review

dikon.ru accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

dikon.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

dikon.ru SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dikon.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 Dikon.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.

Social Sharing Optimization

dikon.ru

Open Graph data is detected on the main page of Dikon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: