Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 75

    SEO

    Google-friendlier than
    41% of websites

piter.fm

PITER.FM — Просто слушаем радио и внимательно считаем песни в эфире

Page Load Speed

6.3 sec in total

First Response

579 ms

Resources Loaded

5.3 sec

Page Rendered

368 ms

piter.fm screenshot

About Website

Click here to check amazing PITER content for Russia. Otherwise, check out these important facts you probably never knew about piter.fm

PITER.FM — Радиостанции Санкт-Петербурга в FM-диапазоне. Слушать радио онлайн в любое удобное время.

Visit piter.fm

Key Findings

We analyzed Piter.fm page load time and found that the first response time was 579 ms and then it took 5.7 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

piter.fm performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.696

7/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

piter.fm

579 ms

bootstrap.min.css

320 ms

font-awesome.min.css

254 ms

site.css

270 ms

zvooq.css

179 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 31% of them (24 requests) were addressed to the original Piter.fm, 16% (12 requests) were made to T1.moskva.fm and 9% (7 requests) were made to Content.adriver.ru. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source T1.moskva.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 636.4 kB (33%)

Content Size

1.9 MB

After Optimization

1.3 MB

In fact, the total size of Piter.fm main page is 1.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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 28.2 kB

  • Original 34.4 kB
  • After minification 25.6 kB
  • After compression 6.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 8.8 kB, which is 26% 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 28.2 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 47.4 kB

  • Original 1.1 MB
  • After minification 1.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. PITER images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 351.2 kB

  • Original 519.8 kB
  • After minification 477.1 kB
  • After compression 168.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 351.2 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 209.6 kB

  • Original 248.2 kB
  • After minification 227.0 kB
  • After compression 38.6 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. Piter.fm needs all CSS files to be minified and compressed as it can save up to 209.6 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

26

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

Accessibility Review

piter.fm accessibility score

63

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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 valid value for its [lang] attribute.

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

Form elements do not have associated labels

Best Practices

piter.fm best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

piter.fm SEO score

75

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 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 Piter.fm 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 Piter.fm 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

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