Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fmniigata.com

FM-NIIGATA (エフエムラジオ新潟)

Page Load Speed

7.8 sec in total

First Response

341 ms

Resources Loaded

4.9 sec

Page Rendered

2.5 sec

fmniigata.com screenshot

About Website

Visit fmniigata.com now to see the best up-to-date FM NIIGATA content for Japan and also check out these interesting facts you probably never knew about fmniigata.com

新潟のFMラジオ局 FM-NIIGATA(エフエムラジオ新潟)。オンエア楽曲の検索やラジオ番組の紹介、WEBだけで聴ける音声コンテンツの他、パーソナリティブログ、イベント、プレゼント情報が満載!

Visit fmniigata.com

Key Findings

We analyzed Fmniigata.com page load time and found that the first response time was 341 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 85% of websites can load faster.

Performance Metrics

fmniigata.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

fmniigata.com

341 ms

fmniigata.com

672 ms

www.fmniigata.com

2109 ms

gtm.js

71 ms

user.css

241 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 31% of them (33 requests) were addressed to the original Fmniigata.com, 54% (57 requests) were made to Image.fmniigata.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Fmniigata.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (11%)

Content Size

14.3 MB

After Optimization

12.8 MB

In fact, the total size of Fmniigata.com main page is 14.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. Only a small number of websites need less resources to load. Images take 14.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 139.2 kB

  • Original 161.6 kB
  • After minification 161.6 kB
  • After compression 22.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 139.2 kB or 86% of the original size.

Image Optimization

-10%

Potential reduce by 1.4 MB

  • Original 14.1 MB
  • After minification 12.7 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 NIIGATA images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 3.0 kB

  • Original 24.9 kB
  • After minification 24.9 kB
  • After compression 21.9 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 3.0 kB or 12% of the original size.

CSS Optimization

-0%

Potential reduce by 84 B

  • Original 32.6 kB
  • After minification 32.6 kB
  • After compression 32.5 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. Fmniigata.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (22%)

Requests Now

99

After Optimization

77

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

Accessibility Review

fmniigata.com accessibility score

85

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

<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

Best Practices

fmniigata.com best practices score

92

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

Page has valid source maps

SEO Factors

fmniigata.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Fmniigata.com 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 Fmniigata.com 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 description is not detected on the main page of FM NIIGATA. 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: