Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 0

    Best Practices

  • 92

    SEO

    Google-friendlier than
    74% of websites

Page Load Speed

1.9 sec in total

First Response

511 ms

Resources Loaded

1.4 sec

Page Rendered

0 ms

dwg.by screenshot

About Website

Welcome to dwg.by homepage info - get ready to check Dwg best content for Belarus right away, or after learning these important things about dwg.by

Visit dwg.by

Key Findings

We analyzed Dwg.by page load time and found that the first response time was 511 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

dwg.by performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value5,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

dwg.by

511 ms

842 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Dwg.by, 50% (1 request) were made to Gdeotziv.ru. The less responsive or slowest element that took the longest time to load (842 ms) relates to the external source Gdeotziv.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 281.8 kB (33%)

Content Size

842.4 kB

After Optimization

560.6 kB

In fact, the total size of Dwg.by main page is 842.4 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 455.1 kB which makes up the majority of the site volume.

HTML Optimization

-26%

Potential reduce by 68 B

  • Original 260 B
  • After minification 260 B
  • After compression 192 B

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 68 B or 26% of the original size.

Image Optimization

-5%

Potential reduce by 23.5 kB

  • Original 455.1 kB
  • After minification 431.6 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.

JavaScript Optimization

-64%

Potential reduce by 203.2 kB

  • Original 316.7 kB
  • After minification 307.5 kB
  • After compression 113.5 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 203.2 kB or 64% of the original size.

CSS Optimization

-78%

Potential reduce by 55.0 kB

  • Original 70.4 kB
  • After minification 55.9 kB
  • After compression 15.4 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.by needs all CSS files to be minified and compressed as it can save up to 55.0 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

dwg.by accessibility score

92

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

Links do not have a discernible name

SEO Factors

dwg.by SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dwg.by 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.by main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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: