Tools & Wizards About Us
db22.ru screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

db22.ru

Деловой Барнаул - Современный портал Барнаула - db22.ru

Page Load Speed

4.8 sec in total

First Response

1 sec

Resources Loaded

3.6 sec

Page Rendered

223 ms

db22.ru screenshot

About Website

Click here to check amazing Db 22 content for Russia. Otherwise, check out these important facts you probably never knew about db22.ru

Деловой Барнаул - это свежие новости, прогноз погоды, поиск и удобное добавление объявлений, а также свежие вакансии и объявления про недвижимость в Барнауле.

Visit db22.ru

Key Findings

We analyzed Db22.ru page load time and found that the first response time was 1 sec and then it took 3.8 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

db22.ru performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

db22.ru

1027 ms

css

24 ms

css

50 ms

global.css

122 ms

global2.css

233 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 62% of them (46 requests) were addressed to the original Db22.ru, 7% (5 requests) were made to Bulgaris.ru and 7% (5 requests) were made to T.me. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Db22.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.3 kB (13%)

Content Size

493.2 kB

After Optimization

426.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Db22.ru main page is 493.2 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 250.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 61.4 kB

  • Original 73.8 kB
  • After minification 59.0 kB
  • After compression 12.4 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 14.8 kB, which is 20% 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 61.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 749 B

  • Original 250.5 kB
  • After minification 249.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. Db 22 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 632 B

  • Original 141.9 kB
  • After minification 141.7 kB
  • After compression 141.2 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

-13%

Potential reduce by 3.5 kB

  • Original 27.1 kB
  • After minification 27.1 kB
  • After compression 23.5 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. Db22.ru needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (25%)

Requests Now

59

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

db22.ru

db22.ru

1027 ms

css

css

24 ms

css

css

50 ms

global.css

global.css

122 ms

global2.css

global2.css

233 ms

client.css

client.css

348 ms

modal.css

modal.css

241 ms

font-awesome.min.css

font-awesome.min.css

47 ms

css

css

48 ms

client.js

client.js

516 ms

main.css

main.css

269 ms

switch.js

switch.js

267 ms

daily_jsonp.js

daily_jsonp.js

33 ms

zp.js

zp.js

680 ms

daily_jsonp.js

daily_jsonp.js

39 ms

tag.js

tag.js

806 ms

blue.gif

blue.gif

121 ms

blue_dark.gif

blue_dark.gif

133 ms

logo.png

logo.png

134 ms

171.jpg

171.jpg

344 ms

ilist_01.gif

ilist_01.gif

129 ms

ilist_02.gif

ilist_02.gif

116 ms

ilist_03.gif

ilist_03.gif

230 ms

ilist_04.gif

ilist_04.gif

239 ms

ilist_05.gif

ilist_05.gif

255 ms

ilist_06.gif

ilist_06.gif

266 ms

ilist_07.gif

ilist_07.gif

267 ms

ilist_08.gif

ilist_08.gif

346 ms

ilist_09.gif

ilist_09.gif

359 ms

ilist_10.gif

ilist_10.gif

383 ms

ilist_11.gif

ilist_11.gif

398 ms

ilist_12.gif

ilist_12.gif

400 ms

ilist_13.gif

ilist_13.gif

458 ms

ilist_14.gif

ilist_14.gif

460 ms

ilist_15.gif

ilist_15.gif

479 ms

ilist_16.gif

ilist_16.gif

510 ms

ilist_17.gif

ilist_17.gif

529 ms

ilist_18.gif

ilist_18.gif

533 ms

ilist_19.gif

ilist_19.gif

573 ms

ilist_20.gif

ilist_20.gif

574 ms

banner-company-490.jpg

banner-company-490.jpg

598 ms

logo-mini.png

logo-mini.png

636 ms

18.jpg

18.jpg

661 ms

b-header-login.png

b-header-login.png

654 ms

aci.js

aci.js

514 ms

b-news-item-sprite.png

b-news-item-sprite.png

651 ms

view.png

view.png

652 ms

comment.png

comment.png

682 ms

170.jpg

170.jpg

854 ms

b-news-gradient.png

b-news-gradient.png

757 ms

169.jpg

169.jpg

894 ms

168.jpg

168.jpg

843 ms

167.jpg

167.jpg

880 ms

json

json

156 ms

BngRUXNadjH0qYEzV7ab-oWlsbCCwRg.ttf

BngRUXNadjH0qYEzV7ab-oWlsbCCwRg.ttf

20 ms

valute-dinamic.png

valute-dinamic.png

770 ms

do_c.gif

do_c.gif

809 ms

telega.html

telega.html

448 ms

watch.js

watch.js

1 ms

version.js

version.js

128 ms

weather

weather

27 ms

+EVAtJ3aXjLc2YThi

+EVAtJ3aXjLc2YThi

399 ms

telega.html

telega.html

213 ms

telega.html

telega.html

244 ms

telega.html

telega.html

133 ms

+EVAtJ3aXjLc2YThi

+EVAtJ3aXjLc2YThi

196 ms

telega.html

telega.html

154 ms

advert.gif

advert.gif

712 ms

+EVAtJ3aXjLc2YThi

+EVAtJ3aXjLc2YThi

247 ms

+EVAtJ3aXjLc2YThi

+EVAtJ3aXjLc2YThi

307 ms

+EVAtJ3aXjLc2YThi

+EVAtJ3aXjLc2YThi

241 ms

sync_cookie_image_decide

sync_cookie_image_decide

156 ms

impression.html

impression.html

130 ms

extra.js

extra.js

256 ms

Accessibility Review

db22.ru accessibility score

80

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

db22.ru 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

db22.ru SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

db22.ru

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