Tools & Wizards About Us
dwz.sh screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

dwz.sh

Ads.so - The URL shortener service that pays you! Earn money for every visitor to your links.

Page Load Speed

2.6 sec in total

First Response

387 ms

Resources Loaded

1.8 sec

Page Rendered

351 ms

dwz.sh screenshot

About Website

Click here to check amazing Dwz content for Russia. Otherwise, check out these important facts you probably never knew about dwz.sh

Earn money for each visitor to your shortened links with ads.so! Use a URL shortener service that pays.

Visit dwz.sh

Key Findings

We analyzed Dwz.sh page load time and found that the first response time was 387 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

dwz.sh performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

ads.so

387 ms

css

23 ms

styles.min.css

149 ms

ads.js

192 ms

script.min.js

281 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dwz.sh, 13% (4 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to S10.histats.com. The less responsive or slowest element that took the longest time to load (454 ms) relates to the external source Ads.so.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.8 kB (11%)

Content Size

349.1 kB

After Optimization

309.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dwz.sh main page is 349.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 178.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 16.3 kB

  • Original 20.9 kB
  • After minification 16.4 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 4.5 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 16.3 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 7.6 kB

  • Original 178.0 kB
  • After minification 170.4 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. Dwz images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 9.0 kB

  • Original 108.1 kB
  • After minification 108.1 kB
  • After compression 99.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

-16%

Potential reduce by 6.9 kB

  • Original 42.2 kB
  • After minification 42.2 kB
  • After compression 35.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. Dwz.sh needs all CSS files to be minified and compressed as it can save up to 6.9 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (38%)

Requests Now

24

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ads.so

ads.so

387 ms

css

css

23 ms

styles.min.css

styles.min.css

149 ms

ads.js

ads.js

192 ms

script.min.js

script.min.js

281 ms

api.js

api.js

40 ms

logo2.png

logo2.png

207 ms

right-arrow.png

right-arrow.png

189 ms

Payment-Methods.png

Payment-Methods.png

189 ms

header.jpg

header.jpg

137 ms

cloud.png

cloud.png

142 ms

spritesheet.png

spritesheet.png

140 ms

chart.png

chart.png

136 ms

world-map.png

world-map.png

175 ms

footer.jpg

footer.jpg

236 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

9 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

15 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

20 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

20 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

454 ms

js15_as.js

js15_as.js

32 ms

0.php

0.php

85 ms

cc_511.js

cc_511.js

35 ms

206 ms

214 ms

afwu.js

afwu.js

36 ms

401 ms

t.dhj

t.dhj

21 ms

t_.htm

t_.htm

6 ms

lt.min.js

lt.min.js

20 ms

Accessibility Review

dwz.sh accessibility score

80

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Best Practices

dwz.sh best practices score

67

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

Browser errors were logged to the console

SEO Factors

dwz.sh SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dwz.sh can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Dwz.sh 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

dwz.sh

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