Tools & Wizards About Us
fmfukuoka.co.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

fmfukuoka.co.jp

FM FUKUOKA (エフエム福岡)

Page Load Speed

5.8 sec in total

First Response

663 ms

Resources Loaded

4.2 sec

Page Rendered

858 ms

fmfukuoka.co.jp screenshot

About Website

Welcome to fmfukuoka.co.jp homepage info - get ready to check FM FUKUOKA best content for Japan right away, or after learning these important things about fmfukuoka.co.jp

福岡で一番人気のラジオ局、FM福岡（FM FUKUOKA）のイベント情報・番組情報などをお届けする公式サイトです。

Visit fmfukuoka.co.jp

Key Findings

We analyzed Fmfukuoka.co.jp page load time and found that the first response time was 663 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

fmfukuoka.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.627

9/100

15%

TTI (Time to Interactive)

Value30.0 s

0/100

10%

Network Requests Diagram

fmfukuoka.co.jp

663 ms

gtm.js

66 ms

bootstrap-4.4.1.css

394 ms

swiper.min.css

375 ms

common.css

377 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 80% of them (61 requests) were addressed to the original Fmfukuoka.co.jp, 7% (5 requests) were made to Google.com and 4% (3 requests) were made to Web-soigner.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Web-soigner.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 427.8 kB (7%)

Content Size

5.8 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fmfukuoka.co.jp main page is 5.8 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. 70% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 35.1 kB

  • Original 45.6 kB
  • After minification 42.7 kB
  • After compression 10.5 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 35.1 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 378.6 kB

  • Original 5.4 MB
  • After minification 5.1 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. FM FUKUOKA images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 7.3 kB

  • Original 284.2 kB
  • After minification 284.2 kB
  • After compression 277.0 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

-14%

Potential reduce by 6.8 kB

  • Original 50.1 kB
  • After minification 50.1 kB
  • After compression 43.3 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. Fmfukuoka.co.jp needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (35%)

Requests Now

75

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FM FUKUOKA. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fmfukuoka.co.jp

fmfukuoka.co.jp

663 ms

gtm.js

gtm.js

66 ms

bootstrap-4.4.1.css

bootstrap-4.4.1.css

394 ms

swiper.min.css

swiper.min.css

375 ms

common.css

common.css

377 ms

top.css

top.css

381 ms

cse.js

cse.js

46 ms

19_2_l.jpg

19_2_l.jpg

2659 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

587 ms

popper.min.js

popper.min.js

527 ms

bootstrap-4.4.1.js

bootstrap-4.4.1.js

749 ms

swiper.min.js

swiper.min.js

762 ms

common.js

common.js

605 ms

logo.svg

logo.svg

607 ms

94_1_l.jpg

94_1_l.jpg

1933 ms

98_1_l.jpg

98_1_l.jpg

1814 ms

92_1_l.jpg

92_1_l.jpg

1702 ms

95_1_l.jpg

95_1_l.jpg

1557 ms

bn-live.jpg

bn-live.jpg

953 ms

bn-live-sp.jpg

bn-live-sp.jpg

954 ms

bn-present.png

bn-present.png

1120 ms

bn-present.png

bn-present.png

1129 ms

bn-books.png

bn-books.png

1308 ms

bn-books.png

bn-books.png

1317 ms

power_play_2.svg

power_play_2.svg

1497 ms

soigner_logo.svg

soigner_logo.svg

1505 ms

bunei.png

bunei.png

1687 ms

01.png

01.png

1695 ms

02.png

02.png

1751 ms

06.png

06.png

1873 ms

horoscoope.jpg

horoscoope.jpg

1885 ms

07.png

07.png

1894 ms

jizake.png

jizake.png

1946 ms

04.png

04.png

2000 ms

kls.jpg

kls.jpg

2062 ms

hakata.jpg

hakata.jpg

2072 ms

80_1_original.gif

80_1_original.gif

2084 ms

77_1_original.jpg

77_1_original.jpg

2123 ms

76_1_original.jpg

76_1_original.jpg

2140 ms

13_1_original.jpg

13_1_original.jpg

2182 ms

cse_element__ja.js

cse_element__ja.js

44 ms

default+ja.css

default+ja.css

99 ms

default.css

default.css

100 ms

js

js

111 ms

analytics.js

analytics.js

43 ms

collect

collect

84 ms

collect

collect

32 ms

63_1_original.jpg

63_1_original.jpg

1886 ms

34_1_original.jpg

34_1_original.jpg

1891 ms

6_1_original.jpg

6_1_original.jpg

1906 ms

10_1_original.jpg

10_1_original.jpg

1808 ms

715_1_m.jpg

715_1_m.jpg

1806 ms

715_2_m.jpg

715_2_m.jpg

1765 ms

glass_w.svg

glass_w.svg

1834 ms

indicator.svg

indicator.svg

1822 ms

guest.svg

guest.svg

1715 ms

now_on_air.jpg

now_on_air.jpg

1754 ms

async-ads.js

async-ads.js

74 ms

branding.png

branding.png

67 ms

clear.png

clear.png

44 ms

_latest_issue_data.php

_latest_issue_data.php

885 ms

website_w.svg

website_w.svg

1580 ms

message_w.svg

message_w.svg

1589 ms

01.png

01.png

1506 ms

prev_white.svg

prev_white.svg

1506 ms

next_gray.svg

next_gray.svg

1351 ms

prev_gray.svg

prev_gray.svg

1405 ms

music.svg

music.svg

1227 ms

bottom_white.svg

bottom_white.svg

1226 ms

arrow_white.svg

arrow_white.svg

1256 ms

news.png

news.png

1139 ms

soigner.jpg

soigner.jpg

1162 ms

external.svg

external.svg

1214 ms

information.jpg

information.jpg

1172 ms

45_2_m.jpg

45_2_m.jpg

1755 ms

page_top.svg

page_top.svg

1100 ms

Accessibility Review

fmfukuoka.co.jp accessibility score

93

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Links do not have a discernible name

Best Practices

fmfukuoka.co.jp 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

Page has valid source maps

SEO Factors

fmfukuoka.co.jp SEO score

75

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 doesn't use 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 Fmfukuoka.co.jp 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 Fmfukuoka.co.jp 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

fmfukuoka.co.jp

Open Graph data is detected on the main page of FM FUKUOKA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: