Tools & Wizards About Us
omsk-meteo.ru screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

omsk-meteo.ru

Главная - omsk-meteo.ru

Page Load Speed

6.6 sec in total

First Response

1.2 sec

Resources Loaded

5 sec

Page Rendered

335 ms

omsk-meteo.ru screenshot

About Website

Click here to check amazing Omsk Meteo content for Russia. Otherwise, check out these important facts you probably never knew about omsk-meteo.ru

Федеральное государственное бюджетное учреждение «Обь-Иртышское управление по гидрометеорологии и мониторингу окружающей среды» (ФГБУ «Обь-Иртышское УГМС»)

Visit omsk-meteo.ru

Key Findings

We analyzed Omsk-meteo.ru page load time and found that the first response time was 1.2 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

omsk-meteo.ru performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value9.4 s

30/100

10%

Network Requests Diagram

1243 ms

style.css

343 ms

content.css

344 ms

nivo-slider.min.css

344 ms

default.css

344 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that all of those requests were addressed to Omsk-meteo.ru and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Omsk-meteo.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (31%)

Content Size

3.2 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Omsk-meteo.ru main page is 3.2 MB. 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. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 303.8 kB

  • Original 335.0 kB
  • After minification 176.8 kB
  • After compression 31.2 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 158.2 kB, which is 47% 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 303.8 kB or 91% of the original size.

Image Optimization

-8%

Potential reduce by 176.0 kB

  • Original 2.3 MB
  • After minification 2.1 MB

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. Omsk Meteo images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 255.4 kB

  • Original 342.9 kB
  • After minification 305.7 kB
  • After compression 87.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 255.4 kB or 74% of the original size.

CSS Optimization

-91%

Potential reduce by 267.6 kB

  • Original 294.5 kB
  • After minification 205.2 kB
  • After compression 26.9 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. Omsk-meteo.ru needs all CSS files to be minified and compressed as it can save up to 267.6 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (33%)

Requests Now

91

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1243 ms

style.css

style.css

343 ms

content.css

content.css

344 ms

nivo-slider.min.css

nivo-slider.min.css

344 ms

default.css

default.css

344 ms

chosen.css

chosen.css

344 ms

finder.css

finder.css

516 ms

jquery.min.js

jquery.min.js

892 ms

jquery-noconflict.js

jquery-noconflict.js

517 ms

jquery-migrate.min.js

jquery-migrate.min.js

516 ms

caption.js

caption.js

517 ms

bootstrap.min.js

bootstrap.min.js

851 ms

core.js

core.js

686 ms

keepalive.js

keepalive.js

687 ms

jquery.nivo.slider.min.js

jquery.nivo.slider.min.js

688 ms

chosen.jquery.min.js

chosen.jquery.min.js

1022 ms

jquery.autocomplete.min.js

jquery.autocomplete.min.js

857 ms

template.css

template.css

1366 ms

jquery-ui.css

jquery-ui.css

1001 ms

default.css

default.css

1017 ms

jquery-noconflict.js

jquery-noconflict.js

1027 ms

mobilyblocks.js

mobilyblocks.js

1056 ms

funcs.js

funcs.js

1173 ms

formAjax.js

formAjax.js

1183 ms

progn_formAjax.js

progn_formAjax.js

1190 ms

formAjax.js

formAjax.js

1191 ms

aw_days_formAjax.js

aw_days_formAjax.js

1222 ms

aw_month_formAjax.js

aw_month_formAjax.js

1340 ms

aw_nmu_formAjax.js

aw_nmu_formAjax.js

1351 ms

pw_month_formAjax.js

pw_month_formAjax.js

1357 ms

rm_month_formAjax.js

rm_month_formAjax.js

1361 ms

opyav_map_styles.css

opyav_map_styles.css

757 ms

opyav_map_funcs.js

opyav_map_funcs.js

682 ms

ros190_7.jpg

ros190_7.jpg

172 ms

logo3.png

logo3.png

177 ms

N39.png

N39.png

174 ms

kn1.png

kn1.png

171 ms

kn4.png

kn4.png

174 ms

slogon11.png

slogon11.png

272 ms

home.png

home.png

338 ms

myvmeste8.png

myvmeste8.png

509 ms

docinf7.png

docinf7.png

348 ms

75_fin2.png

75_fin2.png

354 ms

koncurs1.png

koncurs1.png

1031 ms

go_up.png

go_up.png

441 ms

go_bottom.png

go_bottom.png

507 ms

w6.png

w6.png

516 ms

0.png

0.png

861 ms

Z5.png

Z5.png

610 ms

Z6.png

Z6.png

675 ms

Z8.png

Z8.png

676 ms

Z9.png

Z9.png

683 ms

Z10.png

Z10.png

778 ms

cn1.png

cn1.png

1010 ms

z3c.png

z3c.png

847 ms

z2c.png

z2c.png

852 ms

z1c.png

z1c.png

946 ms

z3v.png

z3v.png

1016 ms

z2v.png

z2v.png

1019 ms

z1v.png

z1v.png

1027 ms

z3z.png

z3z.png

1114 ms

z2z.png

z2z.png

1177 ms

z1z.png

z1z.png

1184 ms

z3s.png

z3s.png

1187 ms

z2s.png

z2s.png

1195 ms

z1s.png

z1s.png

1196 ms

z3y.png

z3y.png

1266 ms

z2y.png

z2y.png

1320 ms

AjaxInformer.php

AjaxInformer.php

1513 ms

z1y.png

z1y.png

1191 ms

prn5.png

prn5.png

1204 ms

prn4.png

prn4.png

1207 ms

prn3.png

prn3.png

1287 ms

prn2.png

prn2.png

1346 ms

prn1.png

prn1.png

1261 ms

prn7.png

prn7.png

1209 ms

prn6.png

prn6.png

1203 ms

prn10.png

prn10.png

1280 ms

omsk_new.png

omsk_new.png

1249 ms

tumen_new.png

tumen_new.png

1194 ms

xmao_new.png

xmao_new.png

1208 ms

yanao_new.png

yanao_new.png

1203 ms

loading.gif

loading.gif

1190 ms

%D0%9F%D0%BE%D0%B7%D0%B5%D0%BC%D0%BD%D1%8B%D0%B9%20%D1%82%D1%83%D0%BC%D0%B0%D0%BD.png

%D0%9F%D0%BE%D0%B7%D0%B5%D0%BC%D0%BD%D1%8B%D0%B9%20%D1%82%D1%83%D0%BC%D0%B0%D0%BD.png

169 ms

%D0%9F%D0%B5%D1%80%D0%B5%D0%BC%D0%B5%D0%BD%D0%BD%D0%B0%D1%8F%20%D0%BE%D0%B1%D0%BB%D0%B0%D1%87%D0%BD%D0%BE%D1%81%D1%82%D1%8C.png

%D0%9F%D0%B5%D1%80%D0%B5%D0%BC%D0%B5%D0%BD%D0%BD%D0%B0%D1%8F%20%D0%BE%D0%B1%D0%BB%D0%B0%D1%87%D0%BD%D0%BE%D1%81%D1%82%D1%8C.png

222 ms

%D0%9E%D0%B1%D0%BB%D0%B0%D1%87%D0%BD%D0%BE.png

%D0%9E%D0%B1%D0%BB%D0%B0%D1%87%D0%BD%D0%BE.png

232 ms

%D0%9D%D0%B5%D0%BE%D0%BF%D1%80%D0%B5%D0%B4%D0%B5%D0%BB%D0%B5%D0%BD%D0%BE.png

%D0%9D%D0%B5%D0%BE%D0%BF%D1%80%D0%B5%D0%B4%D0%B5%D0%BB%D0%B5%D0%BD%D0%BE.png

247 ms

2_1.png

2_1.png

255 ms

2_1.png

2_1.png

334 ms

2_1.png

2_1.png

503 ms

2_1.png

2_1.png

555 ms

arrows.png

arrows.png

170 ms

Accessibility Review

omsk-meteo.ru accessibility score

83

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

omsk-meteo.ru 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

omsk-meteo.ru SEO score

77

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

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 Omsk-meteo.ru 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 Omsk-meteo.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

omsk-meteo.ru

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