Tools & Wizards About Us
fm807.jp screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

fm807.jp

エフエム徳島 80.7MHz

Page Load Speed

20.9 sec in total

First Response

656 ms

Resources Loaded

19.7 sec

Page Rendered

562 ms

fm807.jp screenshot

About Website

Visit fm807.jp now to see the best up-to-date Fm 80 7 content for Japan and also check out these interesting facts you probably never knew about fm807.jp

徳島県のＦＭラジオ局 エフエム徳島　80.7Mhz

Visit fm807.jp

Key Findings

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

Performance Metrics

fm807.jp performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value30.6 s

0/100

25%

SI (Speed Index)

Value24.2 s

0/100

10%

TBT (Total Blocking Time)

Value7,120 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.733

6/100

15%

TTI (Time to Interactive)

Value39.3 s

0/100

10%

Network Requests Diagram

fm807.jp

656 ms

fm807.jp

1651 ms

js

92 ms

base.css

703 ms

top_style.css

842 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 76% of them (84 requests) were addressed to the original Fm807.jp, 16% (18 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (11.9 sec) belongs to the original domain Fm807.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.1 kB (4%)

Content Size

6.2 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fm807.jp main page is 6.2 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. 75% 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 5.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 92.4 kB

  • Original 107.4 kB
  • After minification 65.5 kB
  • After compression 14.9 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 41.8 kB, which is 39% 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 92.4 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 54.4 kB

  • Original 5.9 MB
  • After minification 5.9 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 80 7 images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 91.9 kB

  • Original 170.7 kB
  • After minification 157.6 kB
  • After compression 78.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 91.9 kB or 54% of the original size.

CSS Optimization

-85%

Potential reduce by 23.4 kB

  • Original 27.5 kB
  • After minification 14.5 kB
  • After compression 4.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. Fm807.jp needs all CSS files to be minified and compressed as it can save up to 23.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (29%)

Requests Now

108

After Optimization

77

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fm807.jp

fm807.jp

656 ms

fm807.jp

fm807.jp

1651 ms

js

js

92 ms

base.css

base.css

703 ms

top_style.css

top_style.css

842 ms

nivo-slider.css

nivo-slider.css

521 ms

jquery.min.js

jquery.min.js

49 ms

4372aa0aaa.js

4372aa0aaa.js

118 ms

jquery.js

jquery.js

1381 ms

script.js

script.js

528 ms

jquery.smoothscroll.js

jquery.smoothscroll.js

995 ms

jquery.scrollshow.js

jquery.scrollshow.js

1022 ms

jquery.rollover.js

jquery.rollover.js

1036 ms

jquery.slideshow.js

jquery.slideshow.js

1525 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

1522 ms

menu.js

menu.js

1487 ms

top.js

top.js

1523 ms

now.js

now.js

1519 ms

sdk.js

sdk.js

30 ms

widgets.js

widgets.js

18 ms

fm_logo.png

fm_logo.png

487 ms

radiko_logo_data.png

radiko_logo_data.png

650 ms

mimimail.png

mimimail.png

832 ms

mimionbox.png

mimionbox.png

1062 ms

2024.jpg

2024.jpg

1783 ms

2024.jpg

2024.jpg

1259 ms

2023.jpg

2023.jpg

2158 ms

2024top.jpg

2024top.jpg

2062 ms

bnr01.jpg

bnr01.jpg

1866 ms

ehagaki2024_01.png

ehagaki2024_01.png

2307 ms

CMC2024.jpg

CMC2024.jpg

3582 ms

topbnr202403.jpg

topbnr202403.jpg

3151 ms

scenario2024.jpg

scenario2024.jpg

3123 ms

inochi_1.jpg

inochi_1.jpg

3122 ms

j_ba_2023.jpg

j_ba_2023.jpg

3021 ms

music_cross_aid.png

music_cross_aid.png

3163 ms

360_74_b.jpg

360_74_b.jpg

4277 ms

bnr_bouhan2024.jpg

bnr_bouhan2024.jpg

5000 ms

brillante-bn145-30.jpg

brillante-bn145-30.jpg

4385 ms

tokushima.jpg

tokushima.jpg

4413 ms

hellosmile.gif

hellosmile.gif

4502 ms

navikuru2023.png

navikuru2023.png

4731 ms

equake.png

equake.png

4944 ms

200_50.jpg

200_50.jpg

5209 ms

topbnr1.jpg

topbnr1.jpg

6592 ms

topbnr.jpg

topbnr.jpg

6327 ms

topbnr.jpg

topbnr.jpg

6769 ms

sakubun2024_topbnr.jpg

sakubun2024_topbnr.jpg

7228 ms

topbnr.jpg

topbnr.jpg

6978 ms

topbnr.jpg

topbnr.jpg

7690 ms

topbnr.jpg

topbnr.jpg

8476 ms

2023fb.jpg

2023fb.jpg

8899 ms

hatsukoi.gif

hatsukoi.gif

8772 ms

locomeru.jpg

locomeru.jpg

8096 ms

top.png

top.png

9120 ms

top.jpg

top.jpg

9357 ms

sdk.js

sdk.js

101 ms

49 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

32 ms

settings

settings

100 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

4 ms

fm807

fm807

1095 ms

top.jpg

top.jpg

8985 ms

top.jpg

top.jpg

9265 ms

top.jpg

top.jpg

9223 ms

top.jpg

top.jpg

9049 ms

top.jpg

top.jpg

9209 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

10 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

12 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

18 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

19 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

18 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

18 ms

_buildManifest.js

_buildManifest.js

18 ms

_ssgManifest.js

_ssgManifest.js

18 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

13 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

12 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

4 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

10 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

10 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

25 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

8 ms

sakubun2024_top.jpg

sakubun2024_top.jpg

8787 ms

top.jpg

top.jpg

8781 ms

top.jpg

top.jpg

9042 ms

top.jpg

top.jpg

8928 ms

shinseikousan.jpg

shinseikousan.jpg

8631 ms

sinyu_r06-04.jpg

sinyu_r06-04.jpg

10147 ms

azumashikoku.jpg

azumashikoku.jpg

8273 ms

nextone.gif

nextone.gif

8529 ms

ooishijidousya.gif

ooishijidousya.gif

8601 ms

tsukinomiya_golf.gif

tsukinomiya_golf.gif

8625 ms

rokin.gif

rokin.gif

8185 ms

ceremony_kokoro.jpg

ceremony_kokoro.jpg

7832 ms

dreamjack2.jpg

dreamjack2.jpg

7949 ms

craftbase_banner.gif

craftbase_banner.gif

11923 ms

202101_tokushima-nissan_001.gif

202101_tokushima-nissan_001.gif

7927 ms

miyazaki.jpg

miyazaki.jpg

8046 ms

ashu.png

ashu.png

7657 ms

lotas.png

lotas.png

7844 ms

noviltaxi.gif

noviltaxi.gif

8049 ms

comunica.jpg

comunica.jpg

7053 ms

doushin.gif

doushin.gif

6754 ms

morninghome.jpg

morninghome.jpg

6834 ms

lmagic.gif

lmagic.gif

7105 ms

city10.gif

city10.gif

6620 ms

hf-bn.gif

hf-bn.gif

8651 ms

sokoudo.gif

sokoudo.gif

7613 ms

03works.gif

03works.gif

7454 ms

totop.png

totop.png

7245 ms

Accessibility Review

fm807.jp accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fm807.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fm807.jp 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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Fm807.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 Fm807.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

fm807.jp

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