Tools & Wizards About Us
202.fm screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

202.fm

202.FM

Page Load Speed

1 sec in total

First Response

197 ms

Resources Loaded

568 ms

Page Rendered

238 ms

202.fm screenshot

About Website

Click here to check amazing 202 content. Otherwise, check out these important facts you probably never knew about 202.fm

Visit 202.fm

Key Findings

We analyzed 202.fm page load time and found that the first response time was 197 ms and then it took 806 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

202.fm performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

202.fm

197 ms

req

67 ms

mp11_68x56_ani.gif

123 ms

202.fm

39 ms

202_header.jpg

104 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 20% of them (12 requests) were addressed to the original 202.fm, 15% (9 requests) were made to Media.fastclick.net and 5% (3 requests) were made to Adfarm.mediaplex.com. The less responsive or slowest element that took the longest time to load (197 ms) belongs to the original domain 202.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.3 kB (35%)

Content Size

389.8 kB

After Optimization

252.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of 202.fm main page is 389.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 293.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 28.6 kB

  • Original 33.8 kB
  • After minification 26.3 kB
  • After compression 5.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 7.6 kB, which is 22% 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.6 kB or 85% of the original size.

Image Optimization

-22%

Potential reduce by 64.7 kB

  • Original 293.0 kB
  • After minification 228.3 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, 202 needs image optimization as it can save up to 64.7 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 44.0 kB

  • Original 62.9 kB
  • After minification 51.2 kB
  • After compression 18.9 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 44.0 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (46%)

Requests Now

54

After Optimization

29

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

202.fm

202.fm

197 ms

req

req

67 ms

mp11_68x56_ani.gif

mp11_68x56_ani.gif

123 ms

202.fm

202.fm

39 ms

202_header.jpg

202_header.jpg

104 ms

1px.gif

1px.gif

71 ms

bg.jpg

bg.jpg

106 ms

pagenav_bg.jpg

pagenav_bg.jpg

106 ms

pagenav_bg_items.jpg

pagenav_bg_items.jpg

73 ms

pagenav_bg_green.jpg

pagenav_bg_green.jpg

106 ms

2013-10-09T221458Z_2_CBRE9981PRS00_RTROPTP_2_BRAZIL.JPG

2013-10-09T221458Z_2_CBRE9981PRS00_RTROPTP_2_BRAZIL.JPG

12 ms

2013-10-10T152805Z_1_CBRE99916YW00_RTROPTP_2_MUSIC-AMA-NOMINATIONS.JPG

2013-10-10T152805Z_1_CBRE99916YW00_RTROPTP_2_MUSIC-AMA-NOMINATIONS.JPG

12 ms

2013-10-09T223914Z_1_CBRE9981QXL00_RTROPTP_2_USA.JPG

2013-10-09T223914Z_1_CBRE9981QXL00_RTROPTP_2_USA.JPG

12 ms

req

req

49 ms

req

req

53 ms

bot.jpg

bot.jpg

131 ms

2013-10-08T114924Z_1_CBRE9970WUQ00_RTROPTP_2_ARTS-MUSIC-PARKER.JPG

2013-10-08T114924Z_1_CBRE9970WUQ00_RTROPTP_2_ARTS-MUSIC-PARKER.JPG

10 ms

300x250_202.fm.html

300x250_202.fm.html

52 ms

728x90_202live.com-Radio1.html

728x90_202live.com-Radio1.html

79 ms

160x600_202online.com-Radio2.html

160x600_202online.com-Radio2.html

85 ms

pubcode.min.js

pubcode.min.js

7 ms

get.media

get.media

9 ms

cookie_sync

cookie_sync

8 ms

get.media

get.media

10 ms

pubcode.min.js

pubcode.min.js

4 ms

29998-221304-53593-1

29998-221304-53593-1

34 ms

get.media

get.media

26 ms

cookie_sync

cookie_sync

19 ms

get.media

get.media

28 ms

cookie_sync

cookie_sync

21 ms

pubcode.min.js

pubcode.min.js

14 ms

get.media

get.media

20 ms

cookie_sync

cookie_sync

8 ms

match

match

21 ms

29998-221304-53593-2

29998-221304-53593-2

10 ms

PayPal_COOP1_300x250.jpg

PayPal_COOP1_300x250.jpg

80 ms

15 ms

31 ms

PayPal_COOP4_728x90.jpg

PayPal_COOP4_728x90.jpg

71 ms

29998-221304-53593-0

29998-221304-53593-0

33 ms

optinrt_0.js

optinrt_0.js

35 ms

163 ms

4 ms

PayPal_COOP1_160x600.jpg

PayPal_COOP1_160x600.jpg

48 ms

pixel

pixel

50 ms

sync

sync

34 ms

ad

ad

90 ms

rum

rum

35 ms

Pug

Pug

55 ms

rtset

rtset

60 ms

u.php

u.php

102 ms

adsct

adsct

121 ms

10858-64082-1039-0

10858-64082-1039-0

12 ms

rum

rum

24 ms

mapuser

mapuser

26 ms

tap.php

tap.php

20 ms

pixel

pixel

23 ms

sd

sd

26 ms

lr.gif

lr.gif

5 ms

pixel.gif

pixel.gif

9 ms

Accessibility Review

202.fm accessibility score

68

Accessibility Issues

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 [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

Best Practices

202.fm best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

202.fm SEO score

62

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 202.fm can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 202.fm main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

202.fm

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