Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

fum2.jp

フムフム | コラム、ニュース、ハウツー、関連記事!

Page Load Speed

6.9 sec in total

First Response

1.6 sec

Resources Loaded

4.7 sec

Page Rendered

576 ms

fum2.jp screenshot

About Website

Welcome to fum2.jp homepage info - get ready to check Fum 2 best content for Japan right away, or after learning these important things about fum2.jp

フムフム は、ちょっとしたスキマ時間で、さまざまなHowTo(ハウツー)を紹介するコラムやニュースを無料で読めるウェブサイトです。関連記事を掲載した電子書籍も紹介!

Visit fum2.jp

Key Findings

We analyzed Fum2.jp page load time and found that the first response time was 1.6 sec and then it took 5.3 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

fum2.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

fum2.jp

1614 ms

cssreset-min.css

12 ms

bootstrap.css

1546 ms

bootstrap_add.css

540 ms

style.css

939 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 59% of them (61 requests) were addressed to the original Fum2.jp, 8% (8 requests) were made to Tpc.googlesyndication.com and 6% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Fum2.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 449.7 kB (49%)

Content Size

912.3 kB

After Optimization

462.7 kB

In fact, the total size of Fum2.jp main page is 912.3 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. 55% of websites need less resources to load. Javascripts take 420.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.3 kB

  • Original 44.7 kB
  • After minification 39.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 5.7 kB, which is 13% 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 35.3 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 24.7 kB

  • Original 279.7 kB
  • After minification 255.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. Fum 2 images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 245.2 kB

  • Original 420.5 kB
  • After minification 392.9 kB
  • After compression 175.3 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 245.2 kB or 58% of the original size.

CSS Optimization

-86%

Potential reduce by 144.5 kB

  • Original 167.5 kB
  • After minification 125.6 kB
  • After compression 23.0 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. Fum2.jp needs all CSS files to be minified and compressed as it can save up to 144.5 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

100

After Optimization

64

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

Accessibility Review

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

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

Links do not have a discernible name

Best Practices

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

SEO Factors

fum2.jp SEO score

98

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fum2.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 Fum2.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

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