Tools & Wizards About Us
pogodaspb.info screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

pogodaspb.info

Погода в г Санкт-Петербурге в данный момент. Долгосрочный прогноз погоды в Питере (СПб)

Page Load Speed

4.8 sec in total

First Response

440 ms

Resources Loaded

4.2 sec

Page Rendered

158 ms

pogodaspb.info screenshot

About Website

Welcome to pogodaspb.info homepage info - get ready to check Pogodaspb best content for Russia right away, or after learning these important things about pogodaspb.info

погода, погода в санкт-петербурге, прогноз погоды

Visit pogodaspb.info

Key Findings

We analyzed Pogodaspb.info page load time and found that the first response time was 440 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

pogodaspb.info performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value4,360 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value32.1 s

0/100

10%

Network Requests Diagram

pogodaspb.info

440 ms

pogodaspb.info

626 ms

style.css

143 ms

jquery-1.6.4.min.js

429 ms

jFav_v1.0.js

414 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 19% of them (15 requests) were addressed to the original Pogodaspb.info, 55% (42 requests) were made to St6-21.vk.com and 10% (8 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source St6-21.vk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 520.1 kB (18%)

Content Size

2.9 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pogodaspb.info main page is 2.9 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. 60% of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 112.8 kB

  • Original 136.8 kB
  • After minification 129.1 kB
  • After compression 24.0 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. 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 112.8 kB or 82% of the original size.

Image Optimization

-23%

Potential reduce by 20.7 kB

  • Original 90.4 kB
  • After minification 69.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. Obviously, Pogodaspb needs image optimization as it can save up to 20.7 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 283.8 kB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 1.7 MB

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 283.8 kB or 14% of the original size.

CSS Optimization

-16%

Potential reduce by 102.7 kB

  • Original 658.5 kB
  • After minification 658.5 kB
  • After compression 555.8 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. Pogodaspb.info needs all CSS files to be minified and compressed as it can save up to 102.7 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (81%)

Requests Now

73

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pogodaspb.info

pogodaspb.info

440 ms

pogodaspb.info

pogodaspb.info

626 ms

style.css

style.css

143 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

429 ms

jFav_v1.0.js

jFav_v1.0.js

414 ms

script.js

script.js

424 ms

openapi.js

openapi.js

579 ms

context.js

context.js

1046 ms

share.js

share.js

671 ms

openapi.js

openapi.js

627 ms

openapi.a2ed73393cad04481c1dfb3f7794921f.js

openapi.a2ed73393cad04481c1dfb3f7794921f.js

232 ms

openapi.a2ed73393cad04481c1dfb3f7794921f.js

openapi.a2ed73393cad04481c1dfb3f7794921f.js

251 ms

advertisement_banner.png

advertisement_banner.png

424 ms

16.png

16.png

138 ms

n16.png

n16.png

142 ms

6.png

6.png

142 ms

11.png

11.png

275 ms

7.png

7.png

284 ms

n6.png

n6.png

283 ms

all.js

all.js

17 ms

logo.png

logo.png

416 ms

mobil_version.png

mobil_version.png

399 ms

aci.js

aci.js

515 ms

all.js

all.js

6 ms

al_widget_poll.php

al_widget_poll.php

178 ms

upload.gif

upload.gif

209 ms

40 ms

tag.js

tag.js

852 ms

hit

hit

636 ms

widget_like.php

widget_like.php

241 ms

loader_nav210115120713_3.js

loader_nav210115120713_3.js

334 ms

fonts_cnt.c7a76efe.css

fonts_cnt.c7a76efe.css

909 ms

lite.ca486089.css

lite.ca486089.css

612 ms

lang3_2.js

lang3_2.js

568 ms

polyfills.097fc8eb.js

polyfills.097fc8eb.js

582 ms

react.6a15a5cc.js

react.6a15a5cc.js

700 ms

vkui.a2e1063b.js

vkui.a2e1063b.js

857 ms

vkcom-kit.51544c36.css

vkcom-kit.51544c36.css

709 ms

vkcom-kit.1be21eee.js

vkcom-kit.1be21eee.js

946 ms

vkcom-kit-icons.76c15529.js

vkcom-kit-icons.76c15529.js

855 ms

state-management.d517d148.js

state-management.d517d148.js

855 ms

architecture-mobx.906cf75b.js

architecture-mobx.906cf75b.js

856 ms

audioplayer-lib.93b52d88.css

audioplayer-lib.93b52d88.css

879 ms

audioplayer-lib.8f87c867.js

audioplayer-lib.8f87c867.js

998 ms

palette.c3e0dc74.css

palette.c3e0dc74.css

931 ms

palette.af6605eb.js

palette.af6605eb.js

938 ms

common.7a6628b8.js

common.7a6628b8.js

1601 ms

af475d37.163909ea.js

af475d37.163909ea.js

985 ms

39820787.e54fad24.js

39820787.e54fad24.js

1012 ms

782f47a3.985754ca.js

782f47a3.985754ca.js

1029 ms

aee1802d.f8b0495c.js

aee1802d.f8b0495c.js

1036 ms

e78e0200.34061364.js

e78e0200.34061364.js

1068 ms

b691fd56.8c978f39.js

b691fd56.8c978f39.js

1166 ms

c32d0af5.1bdf9fea.js

c32d0af5.1bdf9fea.js

1118 ms

429e74a8.e7592281.js

429e74a8.e7592281.js

1124 ms

9a477bd9.732524e3.js

9a477bd9.732524e3.js

1124 ms

73310976.d046100f.js

73310976.d046100f.js

1250 ms

page.160b43dd.css

page.160b43dd.css

1207 ms

page.66bf6e15.js

page.66bf6e15.js

1218 ms

page.59a58092.css

page.59a58092.css

1393 ms

post.93892e76.css

post.93892e76.css

1255 ms

vkui.43318ab6.css

vkui.43318ab6.css

1383 ms

xdm.js

xdm.js

1301 ms

widget_poll.2ebeffc4.css

widget_poll.2ebeffc4.css

1329 ms

react.84cfd9aa.js

react.84cfd9aa.js

1363 ms

vkui.7bcdeecd.js

vkui.7bcdeecd.js

1552 ms

c3d11fba.296f7859.js

c3d11fba.296f7859.js

1417 ms

0fc69f32.fefb81c0.js

0fc69f32.fefb81c0.js

1460 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

235 ms

base.474fcd2c.css

base.474fcd2c.css

905 ms

widgets.d2d14ebe.css

widgets.d2d14ebe.css

851 ms

poll.77c8439b.js

poll.77c8439b.js

817 ms

al_like.js

al_like.js

840 ms

advert.gif

advert.gif

681 ms

sync_cookie_image_decide

sync_cookie_image_decide

143 ms

like_widget.png

like_widget.png

100 ms

upload.gif

upload.gif

99 ms

Accessibility Review

pogodaspb.info accessibility score

84

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

pogodaspb.info 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

pogodaspb.info SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

pogodaspb.info

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