Tools & Wizards About Us
dias.by screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 59

    SEO

    Google-friendlier than
    22% of websites

dias.by

Сервисная программа DiasAutoPlus

Page Load Speed

18.8 sec in total

First Response

789 ms

Resources Loaded

17.7 sec

Page Rendered

288 ms

dias.by screenshot

About Website

Visit dias.by now to see the best up-to-date Dias content for Belarus and also check out these interesting facts you probably never knew about dias.by

Официальный импортер автозапчастей и моторных масел. Продажа автозапчасти оптом в Минске, Беларусь. Оригинальные запчасти и масла БМВ, Мерседес, Мазда. Дизельные форсунки.

Visit dias.by

Key Findings

We analyzed Dias.by page load time and found that the first response time was 789 ms and then it took 18 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

dias.by performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.261

47/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

dias.by

789 ms

style.css

454 ms

selectbox.css

336 ms

jquery-ui-1.10.3.custom.css

466 ms

system.css

379 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 76% of them (34 requests) were addressed to the original Dias.by, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (15.3 sec) relates to the external source Opt.dias.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 543.3 kB (74%)

Content Size

734.9 kB

After Optimization

191.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dias.by main page is 734.9 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. 30% of websites need less resources to load. Javascripts take 522.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.8 kB

  • Original 48.7 kB
  • After minification 48.5 kB
  • After compression 9.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 38.8 kB or 80% of the original size.

Image Optimization

-67%

Potential reduce by 60.9 kB

  • Original 90.5 kB
  • After minification 29.7 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. Obviously, Dias needs image optimization as it can save up to 60.9 kB or 67% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 382.5 kB

  • Original 522.4 kB
  • After minification 465.5 kB
  • After compression 139.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 382.5 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 61.1 kB

  • Original 73.3 kB
  • After minification 61.1 kB
  • After compression 12.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. Dias.by needs all CSS files to be minified and compressed as it can save up to 61.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (59%)

Requests Now

39

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dias.by

dias.by

789 ms

style.css

style.css

454 ms

selectbox.css

selectbox.css

336 ms

jquery-ui-1.10.3.custom.css

jquery-ui-1.10.3.custom.css

466 ms

system.css

system.css

379 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

775 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

1397 ms

jquery.ui.datepicker-ru.js

jquery.ui.datepicker-ru.js

453 ms

jquery.selectbox.js

jquery.selectbox.js

475 ms

dynamic.js

dynamic.js

573 ms

general.js

general.js

573 ms

slides.js

slides.js

654 ms

cycle.js

cycle.js

955 ms

maximage.js

maximage.js

689 ms

jquery.validate.js

jquery.validate.js

1013 ms

messages_ru.js

messages_ru.js

777 ms

conversion.js

conversion.js

146 ms

background.png

background.png

179 ms

analytics.js

analytics.js

43 ms

filtron.gif

filtron.gif

15276 ms

logo.png

logo.png

221 ms

lb_tab_a.gif

lb_tab_a.gif

222 ms

lb_tab_bg.gif

lb_tab_bg.gif

220 ms

plus.gif

plus.gif

220 ms

rb_h2.gif

rb_h2.gif

220 ms

key_icon.png

key_icon.png

274 ms

1370108611_order_icon.png

1370108611_order_icon.png

352 ms

home_icon.png

home_icon.png

508 ms

auto_icon.png

auto_icon.png

509 ms

oil_icon.png

oil_icon.png

349 ms

bmw_icon.png

bmw_icon.png

594 ms

1370109078_slide1.jpg

1370109078_slide1.jpg

1555 ms

1370098471_cat2.jpg

1370098471_cat2.jpg

747 ms

1370098522_cat6.jpg

1370098522_cat6.jpg

606 ms

1425303644_bmw_logo.jpg

1425303644_bmw_logo.jpg

672 ms

collect

collect

73 ms

opacity_bg.png

opacity_bg.png

612 ms

watch.js

watch.js

3 ms

244 ms

collect

collect

201 ms

100 ms

css

css

120 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

162 ms

53FiIA9tShIIWgCiX49s-vesZW2xOQ-xsNqO47m55DA.ttf

53FiIA9tShIIWgCiX49s-vesZW2xOQ-xsNqO47m55DA.ttf

94 ms

uqFpzDRr-oQw71LHgsWhDw.ttf

uqFpzDRr-oQw71LHgsWhDw.ttf

110 ms

Accessibility Review

dias.by accessibility score

81

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.

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

dias.by 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

dias.by SEO score

59

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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 Dias.by 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 Dias.by 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

dias.by

Open Graph description is not detected on the main page of Dias. 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: