6.3 sec in total
579 ms
5.3 sec
368 ms
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.fmWe 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.
piter.fm performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value2.8 s
82/100
25%
Value4.7 s
68/100
10%
Value520 ms
56/100
30%
Value0.696
7/100
15%
Value6.2 s
62/100
10%
579 ms
320 ms
254 ms
270 ms
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 size can be reduced by 669.7 kB (34%)
2.0 MB
1.3 MB
In fact, the total size of Piter.fm main page is 2.0 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.
Potential reduce by 28.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.
Potential reduce by 47.4 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. PITER images are well optimized though.
Potential reduce by 384.6 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 384.6 kB or 69% of the original size.
Potential reduce by 209.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.
Number of requests can be reduced by 38 (59%)
64
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.
piter.fm
579 ms
bootstrap.min.css
320 ms
font-awesome.min.css
254 ms
site.css
270 ms
zvooq.css
179 ms
css
68 ms
css
81 ms
adriver.core.2.js
179 ms
adfox.asyn.code.ver3.js
198 ms
ad_adriver_piter.js
265 ms
jquery.min.js
476 ms
yii.js
223 ms
bootstrap.min.js
367 ms
site.js
308 ms
onair.js
308 ms
jquery.jplayer.min.js
418 ms
player.js
341 ms
analytics.js
80 ms
hit
278 ms
autoUpdate.adriver.js
414 ms
rta.js
72 ms
2303841.gif
1112 ms
logo
277 ms
control-play-top.png
110 ms
control-pause-top.png
111 ms
control-close-top.png
144 ms
logo_spb.png
178 ms
cover_ad.jpg
461 ms
empty.png
248 ms
loader.gif
249 ms
592933.gif
1110 ms
1148128.gif
1109 ms
602124.gif
1109 ms
581808.gif
1110 ms
613550.gif
1139 ms
16a9ce5cbec0c2cb2df73844a0fd3278.jpeg
1452 ms
a9640e49ef9b097dabc6c09175395acb.jpeg
2118 ms
2798618.gif
1292 ms
532e54cf1f130773759f43bffd22e4c3.jpeg
1295 ms
0aaa706e3bac713820b881bb26b63804.jpeg
1451 ms
0000a9bc98bf87714bb34a5a36d7ef6a.jpeg
2292 ms
pkYDSlCHbDnBWPT5PPFFTA.ttf
46 ms
Zd2E9abXLFGSr9G3YK2MsNbQxvdFQproHqwx84HIuqM.ttf
74 ms
collect
20 ms
collect
85 ms
ga-audiences
108 ms
hit
130 ms
old.adriver.js
270 ms
checkFlash.adriver.js
274 ms
functions.adriver.js
408 ms
merle.cgi
283 ms
merle.cgi
284 ms
script.js
362 ms
1.html
356 ms
script.js
360 ms
1.html
356 ms
1.js
552 ms
html.adriver.js
281 ms
pixel.adriver.js
277 ms
pixel
24 ms
adriver-sync
268 ms
AOBBm_RddGWU8zJl3_9N1og
283 ms
adv_980x90_otclick.spb.html
188 ms
adv_240x400_yandex.spb.html
190 ms
pixel
14 ms
code.js
667 ms
context.js
659 ms
sync.cgi
726 ms
sync.cgi
729 ms
sync.cgi
721 ms
sync.cgi
686 ms
sync.cgi
701 ms
context_static_r1082.js
462 ms
token
307 ms
code.js
129 ms
sync.cgi
548 ms
watch.js
4 ms
piter.fm accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<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
Image elements do not have [alt] attributes
Form elements do not have associated labels
piter.fm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
piter.fm SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
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.
piter.fm
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: