Tools & Wizards About Us
181.fm screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

181.fm

181.FM - Your Lifestyle... Your Music! ~ Free Internet Radio ~

Page Load Speed

925 ms in total

First Response

79 ms

Resources Loaded

609 ms

Page Rendered

237 ms

181.fm screenshot

About Website

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

181.FM Internet Radio - The Best Choice for Radio. Your Lifestyle, Your Music -

Visit 181.fm

Key Findings

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

181.fm performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value1.5 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)

Value2.0 s

99/100

10%

Network Requests Diagram

181.fm

79 ms

www.181.fm

89 ms

stylesheet.css

37 ms

counter.js

6 ms

req

29 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 36% of them (15 requests) were addressed to the original 181.fm, 14% (6 requests) were made to Media.fastclick.net and 5% (2 requests) were made to Fmsads.com. The less responsive or slowest element that took the longest time to load (195 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (71%)

Content Size

1.9 MB

After Optimization

567.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 181.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. 25% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 57.2 kB

  • Original 65.6 kB
  • After minification 42.5 kB
  • After compression 8.3 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 23.1 kB, which is 35% 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 57.2 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 7.7 kB

  • Original 161.0 kB
  • After minification 153.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. 181 images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 367.8 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 1.1 MB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 192.4 kB

  • Original 230.2 kB
  • After minification 200.1 kB
  • After compression 37.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. 181.fm needs all CSS files to be minified and compressed as it can save up to 192.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (49%)

Requests Now

35

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

181.fm

181.fm

79 ms

www.181.fm

www.181.fm

89 ms

stylesheet.css

stylesheet.css

37 ms

counter.js

counter.js

6 ms

req

req

29 ms

minibanner05.gif

minibanner05.gif

67 ms

req

req

17 ms

ga.js

ga.js

28 ms

bg.jpg

bg.jpg

59 ms

headerbg.png

headerbg.png

102 ms

spacer.gif

spacer.gif

73 ms

menu_bg.jpg

menu_bg.jpg

72 ms

body_inside_bg.jpg

body_inside_bg.jpg

76 ms

left_title_bg.jpg

left_title_bg.jpg

77 ms

menu_left_bg.gif

menu_left_bg.gif

76 ms

btn_donate_LG.gif

btn_donate_LG.gif

131 ms

181fm-125x125.gif

181fm-125x125.gif

169 ms

featured_top_bg.jpg

featured_top_bg.jpg

130 ms

blue_bg.jpg

blue_bg.jpg

131 ms

orange_arrow.gif

orange_arrow.gif

130 ms

728x90_202online.com-INT.html

728x90_202online.com-INT.html

183 ms

300x250_202.fm-INT.html

300x250_202.fm-INT.html

183 ms

t.php

t.php

76 ms

__utm.gif

__utm.gif

12 ms

www.conduit.com

www.conduit.com

25 ms

like.php

like.php

195 ms

pubcode.min.js

pubcode.min.js

9 ms

pubcode.min.js

pubcode.min.js

11 ms

get.media

get.media

19 ms

cookie_sync

cookie_sync

26 ms

get.media

get.media

25 ms

cookie_sync

cookie_sync

24 ms

get.media

get.media

14 ms

get.media

get.media

35 ms

27722-220960-53593-3

27722-220960-53593-3

38 ms

-1cfYrhulAt.js

-1cfYrhulAt.js

27 ms

27722-220960-53593-1

27722-220960-53593-1

17 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

24 ms

IAB-Ad-728x90-Quick.jpg

IAB-Ad-728x90-Quick.jpg

83 ms

6 ms

5 ms

IAB-Ad-300x250-Quick.jpg

IAB-Ad-300x250-Quick.jpg

90 ms

Accessibility Review

181.fm accessibility score

64

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

High

Links do not have a discernible name

Best Practices

181.fm best practices score

58

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

181.fm SEO score

67

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

    EN

  • Encoding

    ISO-8859-1

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

181.fm

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