Tools & Wizards About Us
awd.by screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

awd.by

Фотограф Павел Поташников - фотостудия в Минске профессиональный фотограф. Портфолио фотосессия в Минск. Профессиональная фотосъемка бесплатные фотосе...

Page Load Speed

4.4 sec in total

First Response

380 ms

Resources Loaded

3.6 sec

Page Rendered

398 ms

awd.by screenshot

About Website

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

Профессиональный фотограф в Минске. Качественные фотосесии в Минске. Свадбеный фотограф и фотограф на свадьбу. Студийная и выездная фотосъемка, свадебная, портфолио, портрет, рекламная и предметная в ...

Visit awd.by

Key Findings

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

Performance Metrics

awd.by performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value5,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value22.7 s

1/100

10%

Network Requests Diagram

awd.by

380 ms

www.potashnikov.com

959 ms

openapi.js

417 ms

PJCF3TYSNL.js

361 ms

all.js

303 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Awd.by, 28% (13 requests) were made to Potashnikov.com and 22% (10 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Widget.websta.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 296.2 kB (41%)

Content Size

723.5 kB

After Optimization

427.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Awd.by main page is 723.5 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. 40% of websites need less resources to load. Images take 360.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 31.0 kB

  • Original 39.9 kB
  • After minification 34.9 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 5.0 kB, which is 13% 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 31.0 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 24.5 kB

  • Original 360.8 kB
  • After minification 336.3 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. Awd images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 168.0 kB

  • Original 233.9 kB
  • After minification 176.4 kB
  • After compression 65.8 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 168.0 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 72.6 kB

  • Original 88.8 kB
  • After minification 79.1 kB
  • After compression 16.2 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. Awd.by needs all CSS files to be minified and compressed as it can save up to 72.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (44%)

Requests Now

43

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Awd. 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

awd.by

awd.by

380 ms

www.potashnikov.com

www.potashnikov.com

959 ms

openapi.js

openapi.js

417 ms

PJCF3TYSNL.js

PJCF3TYSNL.js

361 ms

all.js

all.js

303 ms

watch.js

watch.js

1 ms

bg1.gif

bg1.gif

256 ms

1px.gif

1px.gif

256 ms

logo1.jpg

logo1.jpg

508 ms

logo2.jpg

logo2.jpg

507 ms

lineup.gif

lineup.gif

259 ms

home.jpg

home.jpg

632 ms

lineup2.gif

lineup2.gif

375 ms

gav.gif

gav.gif

377 ms

twitter2.png

twitter2.png

378 ms

vimeo2.png

vimeo2.png

498 ms

facebook2.png

facebook2.png

507 ms

insta2.jpg

insta2.jpg

508 ms

log.php

log.php

93 ms

1127 ms

upload.gif

upload.gif

272 ms

widget_like.php

widget_like.php

400 ms

116 ms

ga.js

ga.js

29 ms

xd_arbiter.php

xd_arbiter.php

254 ms

xd_arbiter.php

xd_arbiter.php

464 ms

__utm.gif

__utm.gif

29 ms

xd_arbiter.php

xd_arbiter.php

213 ms

like.php

like.php

158 ms

OZhivdPHVp_.js

OZhivdPHVp_.js

507 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

568 ms

loader_nav19239_3.js

loader_nav19239_3.js

131 ms

lite.css

lite.css

251 ms

lite.js

lite.js

505 ms

lang3_0.js

lang3_0.js

256 ms

widgets.css

widgets.css

273 ms

xdm.js

xdm.js

273 ms

al_like.js

al_like.js

272 ms

like_widget.png

like_widget.png

127 ms

bootstrap2.min.css

bootstrap2.min.css

8 ms

12093709_1363605573665665_1124929266_n.jpg

12093709_1363605573665665_1124929266_n.jpg

438 ms

12934940_471833749679637_1111863309_n.jpg

12934940_471833749679637_1111863309_n.jpg

509 ms

12816861_564526643721953_685234679_n.jpg

12816861_564526643721953_685234679_n.jpg

645 ms

10311236_1531998383762634_407336671_n.jpg

10311236_1531998383762634_407336671_n.jpg

708 ms

12070726_1571992669783264_309463646_n.jpg

12070726_1571992669783264_309463646_n.jpg

709 ms

__utm.gif

__utm.gif

14 ms

Accessibility Review

awd.by accessibility score

69

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

awd.by best practices score

58

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

High

Page has valid source maps

SEO Factors

awd.by SEO score

99

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

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awd.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 Awd.by main page’s claimed encoding is windows-1251. 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

awd.by

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