Tools & Wizards About Us
fukigen.jp screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fukigen.jp

Unhappy⁈〜不機嫌な心を癒してくれる事〜 |

Page Load Speed

3.9 sec in total

First Response

1.3 sec

Resources Loaded

2.6 sec

Page Rendered

70 ms

fukigen.jp screenshot

About Website

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

Visit fukigen.jp

Key Findings

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

Performance Metrics

fukigen.jp performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

fukigen.jp

1264 ms

swiper.css

174 ms

style.min.css

520 ms

swell-icons.css

346 ms

main.css

515 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 95% of them (21 requests) were addressed to the original Fukigen.jp, 5% (1 request) were made to Fastly.picsum.photos. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fukigen.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.8 kB (14%)

Content Size

382.0 kB

After Optimization

328.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fukigen.jp main page is 382.0 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. 30% of websites need less resources to load. Images take 209.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 29.3 kB

  • Original 38.4 kB
  • After minification 37.8 kB
  • After compression 9.1 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 29.3 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 209.3 kB
  • After minification 209.3 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. Fukigen images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 9.1 kB

  • Original 58.0 kB
  • After minification 58.0 kB
  • After compression 48.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 9.1 kB or 16% of the original size.

CSS Optimization

-20%

Potential reduce by 15.4 kB

  • Original 76.4 kB
  • After minification 76.1 kB
  • After compression 61.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. Fukigen.jp needs all CSS files to be minified and compressed as it can save up to 15.4 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (85%)

Requests Now

20

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fukigen.jp

fukigen.jp

1264 ms

swiper.css

swiper.css

174 ms

style.min.css

style.min.css

520 ms

swell-icons.css

swell-icons.css

346 ms

main.css

main.css

515 ms

blocks.css

blocks.css

348 ms

footer.css

footer.css

353 ms

main-visual--single.css

main-visual--single.css

352 ms

post-slider.css

post-slider.css

615 ms

home.css

home.css

616 ms

style.css

style.css

615 ms

front.css

front.css

612 ms

style.css

style.css

685 ms

main.min.js

main.min.js

684 ms

set_mv.min.js

set_mv.min.js

789 ms

swiper.min.js

swiper.min.js

1128 ms

set_post_slider.min.js

set_post_slider.min.js

790 ms

lazysizes.min.js

lazysizes.min.js

786 ms

set_fix_header.min.js

set_fix_header.min.js

855 ms

icomoon.ttf

icomoon.ttf

173 ms

1200.jpg

1200.jpg

24 ms

print.css

print.css

174 ms

Accessibility Review

fukigen.jp accessibility score

93

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

Form elements do not have associated labels

Best Practices

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

SEO Factors

fukigen.jp SEO score

93

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

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

fukigen.jp

Open Graph description is not detected on the main page of Fukigen. 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: