Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

blu.fm

blu – Berlin - männer*

Page Load Speed

2.6 sec in total

First Response

237 ms

Resources Loaded

2.1 sec

Page Rendered

272 ms

blu.fm screenshot

About Website

Visit blu.fm now to see the best up-to-date Blu content for Germany and also check out these interesting facts you probably never knew about blu.fm

blu ist das queere Lifestylemagazin für Berlin. Hier findest du spannende Artikel zu Themen wie Liebe, Sex, Kultur, Gesundheit und Politik. Ob du nach Tipps für das Nachtleben, Interviews mit prominen...

Visit blu.fm

Key Findings

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

blu.fm performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

65/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

blu

237 ms

gtm.js

62 ms

theme-openly.da28412e297d78a7c21271c8dc238c8f.css

28 ms

screen.css

24 ms

mp.12e0ba2a5495e39c61a24db3b5dc4d7c.js

37 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Blu.fm, 23% (11 requests) were made to D3t13abgv0q40.cloudfront.net and 10% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (711 ms) relates to the external source Maenner.media.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.5 kB (9%)

Content Size

951.2 kB

After Optimization

865.7 kB

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

HTML Optimization

-81%

Potential reduce by 59.4 kB

  • Original 73.7 kB
  • After minification 69.9 kB
  • After compression 14.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 59.4 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 25.5 kB

  • Original 710.5 kB
  • After minification 685.0 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. Blu images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 367 B

  • Original 143.6 kB
  • After minification 143.6 kB
  • After compression 143.2 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

-1%

Potential reduce by 209 B

  • Original 23.4 kB
  • After minification 23.4 kB
  • After compression 23.2 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. Blu.fm has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

42

After Optimization

28

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

Accessibility Review

blu.fm accessibility score

88

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

blu.fm best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

blu.fm SEO score

97

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blu.fm can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Blu.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 data is detected on the main page of Blu. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: