Tools & Wizards About Us
178.ru screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

178.ru

Новости Санкт-Петербурга и Ленинградской области | 178.ру

Page Load Speed

4.3 sec in total

First Response

515 ms

Resources Loaded

3.2 sec

Page Rendered

535 ms

178.ru screenshot

About Website

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

Последние свежие новости Санкт-Петербурга и Ленинградской области за сегодня. Все новости региона на сайте 178.ру

Visit 178.ru

Key Findings

We analyzed 178.ru page load time and found that the first response time was 515 ms 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

178.ru performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value5,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

178.ru

515 ms

178.ru

1089 ms

context.js

1104 ms

js

70 ms

tag.js

871 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original 178.ru, 39% (19 requests) were made to Cdn.iportal.ru and 27% (13 requests) were made to Static.ngs.ru. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Cdn.iportal.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.1 kB (9%)

Content Size

6.8 MB

After Optimization

6.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of 178.ru main page is 6.8 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. 55% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 510.0 kB

  • Original 591.2 kB
  • After minification 581.8 kB
  • After compression 81.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. 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 510.0 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 6.0 MB
  • After minification 6.0 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. 178 images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 90.2 kB

  • Original 231.5 kB
  • After minification 231.5 kB
  • After compression 141.4 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 90.2 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (43%)

Requests Now

42

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

178.ru

178.ru

515 ms

178.ru

178.ru

1089 ms

context.js

context.js

1104 ms

js

js

70 ms

tag.js

tag.js

871 ms

ad-category-recognition.js

ad-category-recognition.js

914 ms

hsm-creative-manager.471.js

hsm-creative-manager.471.js

781 ms

asdk.js

asdk.js

838 ms

cloudy-rain.8d122f6.svg

cloudy-rain.8d122f6.svg

711 ms

940f0936763ac2a3986faad458eb5b360ba14550_1500_1500_c.jpg

940f0936763ac2a3986faad458eb5b360ba14550_1500_1500_c.jpg

1561 ms

fe29c6c6b50c5ee4d1fea00c3e990ea80dd34805_1620_1080_c.jpeg

fe29c6c6b50c5ee4d1fea00c3e990ea80dd34805_1620_1080_c.jpeg

755 ms

46e4703fdb7712327f44f7fa386ce10606515714_2477_1651_c.jpg

46e4703fdb7712327f44f7fa386ce10606515714_2477_1651_c.jpg

962 ms

20c8c06c029b32a0258c18d173706e9c099266a1_900_600_c.jpg

20c8c06c029b32a0258c18d173706e9c099266a1_900_600_c.jpg

808 ms

ddc2a5fcf185db0d64c484d0abcd89cf0929933f_768_512_c.jpg

ddc2a5fcf185db0d64c484d0abcd89cf0929933f_768_512_c.jpg

801 ms

07ad2ec1b6ae813e224941183f236b0f08d2a391_656_437_c.jpg

07ad2ec1b6ae813e224941183f236b0f08d2a391_656_437_c.jpg

821 ms

54ba1b185e2674f5050f229d6f6b87230c74189f_1192_795_c.jpg

54ba1b185e2674f5050f229d6f6b87230c74189f_1192_795_c.jpg

972 ms

a72668fc35f02954cffed1a78807bf4308616f8c_656_437_c.jpg

a72668fc35f02954cffed1a78807bf4308616f8c_656_437_c.jpg

1028 ms

da2e48891663de7cba7b12ed19e5a8700d35157e_940_627_c.jpg

da2e48891663de7cba7b12ed19e5a8700d35157e_940_627_c.jpg

961 ms

8e9087b5dcbaa000252694cc64fecd0601ea6092_931_621_c.jpg

8e9087b5dcbaa000252694cc64fecd0601ea6092_931_621_c.jpg

1048 ms

d5e874e94a5a37c8ceec2502c9df218e0a7c75fa_1200_800_c.jpg

d5e874e94a5a37c8ceec2502c9df218e0a7c75fa_1200_800_c.jpg

1093 ms

95972f84dafccac43c954d5f1cad89a300247fe1_1500_1000_c.jpg

95972f84dafccac43c954d5f1cad89a300247fe1_1500_1000_c.jpg

1149 ms

d98b130e9b06410abc93f82ba314da3e06d0d761_1200_800_c.jpg

d98b130e9b06410abc93f82ba314da3e06d0d761_1200_800_c.jpg

1115 ms

e9ca2d6044672933c839aae3d9ad596a0cdd23cd_1278_852_c.jpg

e9ca2d6044672933c839aae3d9ad596a0cdd23cd_1278_852_c.jpg

1278 ms

42944fa120a490b6c52e444bf4f5dfe8062d14f9_1500_1000_c.jpg

42944fa120a490b6c52e444bf4f5dfe8062d14f9_1500_1000_c.jpg

1423 ms

1e87131d5296715602691e6e0ef06a4b09557ca7_1500_1000_c.jpg

1e87131d5296715602691e6e0ef06a4b09557ca7_1500_1000_c.jpg

1278 ms

88ea715b6a909e7b45cbb31014957b6e0917a42e_1200_800_c.jpg

88ea715b6a909e7b45cbb31014957b6e0917a42e_1200_800_c.jpg

1266 ms

b0daedbe5902f07c19e79958dd586d730d8d4a1f_1200_800_c.jpg

b0daedbe5902f07c19e79958dd586d730d8d4a1f_1200_800_c.jpg

1294 ms

243a390d87e8fd996d75dc97bfc2c84400fa60b6_295_197_c.jpg

243a390d87e8fd996d75dc97bfc2c84400fa60b6_295_197_c.jpg

1375 ms

runtimechunk~app.8a384ad.js

runtimechunk~app.8a384ad.js

546 ms

new-app.6a2458d.js

new-app.6a2458d.js

780 ms

30400.cf1346b.js

30400.cf1346b.js

546 ms

71106.c7a590c.js

71106.c7a590c.js

587 ms

35820.8aabea7.js

35820.8aabea7.js

653 ms

new-home-page.e6061c8.js

new-home-page.e6061c8.js

800 ms

app.5e09b0a.js

app.5e09b0a.js

673 ms

vq_starter.js

vq_starter.js

638 ms

OneSignalSDK.js

OneSignalSDK.js

35 ms

roxot-manager.js

roxot-manager.js

769 ms

hb.js

hb.js

208 ms

sync-urls.js

sync-urls.js

1052 ms

sync-loader.js

sync-loader.js

844 ms

vq_init.js

vq_init.js

243 ms

ui-common.b29e597eefc8bb61eb784dd93999db51.svg

ui-common.b29e597eefc8bb61eb784dd93999db51.svg

72 ms

roboto-v30-latin_cyrillic-regular.woff

roboto-v30-latin_cyrillic-regular.woff

639 ms

roboto-v30-latin_cyrillic-700.woff

roboto-v30-latin_cyrillic-700.woff

401 ms

roboto-slab-v24-latin_cyrillic-regular.woff

roboto-slab-v24-latin_cyrillic-regular.woff

323 ms

roboto-slab-v24-latin_cyrillic-700.woff

roboto-slab-v24-latin_cyrillic-700.woff

147 ms

advert.gif

advert.gif

827 ms

vq_init.css

vq_init.css

121 ms

Accessibility Review

178.ru accessibility score

60

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

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

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.

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

178.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

178.ru SEO score

91

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

    RU

  • Encoding

    UTF-8

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

178.ru

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