Tools & Wizards About Us
181.fm screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

181.fm

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

Page Load Speed

2.1 sec in total

First Response

22 ms

Resources Loaded

1.6 sec

Page Rendered

480 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 22 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

181.fm performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/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.017

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

181.fm

22 ms

www.181.fm

56 ms

stylesheet.css

10 ms

counter.js

34 ms

ga.js

7 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 84% of them (21 requests) were addressed to the original 181.fm, 4% (1 request) were made to Statcounter.com and 4% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain 181.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 185.1 kB (56%)

Content Size

330.9 kB

After Optimization

145.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 181.fm main page is 330.9 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. 20% of websites need less resources to load. Images take 213.5 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 89.1 kB

  • Original 97.3 kB
  • After minification 79.9 kB
  • After compression 8.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 17.4 kB, which is 18% 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 89.1 kB or 92% of the original size.

Image Optimization

-44%

Potential reduce by 95.0 kB

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

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-36%

Potential reduce by 1.1 kB

  • Original 2.9 kB
  • After minification 2.9 kB
  • After compression 1.9 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 1.1 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (36%)

Requests Now

22

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 22 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 and as a result speed up the page load time.

Network Requests Diagram

181.fm

181.fm

22 ms

www.181.fm

www.181.fm

56 ms

stylesheet.css

stylesheet.css

10 ms

counter.js

counter.js

34 ms

ga.js

ga.js

7 ms

bg.jpg

bg.jpg

74 ms

headerbg.png

headerbg.png

77 ms

spacer.gif

spacer.gif

89 ms

menu_bg.jpg

menu_bg.jpg

89 ms

body_inside_bg.jpg

body_inside_bg.jpg

90 ms

left_title_bg.jpg

left_title_bg.jpg

89 ms

menu_left_bg.gif

menu_left_bg.gif

88 ms

181fm-125x125.gif

181fm-125x125.gif

1523 ms

featured_top_bg.jpg

featured_top_bg.jpg

88 ms

googlebadge.png

googlebadge.png

91 ms

applebadge.png

applebadge.png

93 ms

windowsbadge.png

windowsbadge.png

99 ms

facebook.png

facebook.png

110 ms

blue_bg.jpg

blue_bg.jpg

93 ms

orange_arrow.gif

orange_arrow.gif

92 ms

itunes-winamp.png

itunes-winamp.png

99 ms

__utm.gif

__utm.gif

47 ms

t.php

t.php

80 ms

btn_donate_LG.gif

btn_donate_LG.gif

26 ms

181fm-125x125.gif

181fm-125x125.gif

15 ms

Accessibility Review

181.fm accessibility score

60

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.

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: