Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

block.fm

block.fm

Page Load Speed

8.1 sec in total

First Response

670 ms

Resources Loaded

6.8 sec

Page Rendered

581 ms

block.fm screenshot

About Website

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

ダンスミュージック、ヒップホップ、R&B、ポップミュージックなど国内外の音楽情報を中心に、最新のユースカルチャーをラジオと記事で毎日配信。

Visit block.fm

Key Findings

We analyzed Block.fm page load time and found that the first response time was 670 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

block.fm performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value18.0 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value3,080 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.707

7/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

block.fm

670 ms

common.css

519 ms

module.css

371 ms

header_app.css

366 ms

style.css

588 ms

Our browser made a total of 181 requests to load all elements on the main page. We found that 55% of them (100 requests) were addressed to the original Block.fm, 15% (27 requests) were made to Resource.blockfm.com and 6% (11 requests) were made to Api.block.fm. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Block.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (25%)

Content Size

4.3 MB

After Optimization

3.2 MB

In fact, the total size of Block.fm main page is 4.3 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 40.1 kB

  • Original 51.5 kB
  • After minification 51.5 kB
  • After compression 11.4 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 40.1 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 148.8 kB

  • Original 3.1 MB
  • After minification 3.0 MB

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. Block images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 704.8 kB

  • Original 924.5 kB
  • After minification 772.9 kB
  • After compression 219.7 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 704.8 kB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 182.4 kB

  • Original 213.8 kB
  • After minification 172.6 kB
  • After compression 31.4 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. Block.fm needs all CSS files to be minified and compressed as it can save up to 182.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 103 (60%)

Requests Now

171

After Optimization

68

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

Accessibility Review

block.fm accessibility score

73

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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 valid value for its [lang] attribute.

High

[lang] attributes do not have a valid value

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

block.fm best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

block.fm SEO score

90

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

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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