Tools & Wizards About Us
fnana.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fnana.jp

無効なURLです

Page Load Speed

4.1 sec in total

First Response

656 ms

Resources Loaded

3.2 sec

Page Rendered

232 ms

fnana.jp screenshot

About Website

Click here to check amazing Fnana content for Japan. Otherwise, check out these important facts you probably never knew about fnana.jp

株式会社えふななでは、LKO対策などwebプロモーションを中心とした事業を展開しております。

Visit fnana.jp

Key Findings

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

Performance Metrics

fnana.jp performance score

0

Network Requests Diagram

fnana.jp

656 ms

default.css

198 ms

top.css

342 ms

meanmenu.css

347 ms

css

32 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 83% of them (25 requests) were addressed to the original Fnana.jp, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Fnana.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.8 kB (15%)

Content Size

654.6 kB

After Optimization

558.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 6.9 kB

  • Original 9.3 kB
  • After minification 8.2 kB
  • After compression 2.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 1.1 kB, which is 11% 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 6.9 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 66.5 kB

  • Original 598.9 kB
  • After minification 532.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. Obviously, Fnana needs image optimization as it can save up to 66.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-43%

Potential reduce by 16.7 kB

  • Original 38.8 kB
  • After minification 30.3 kB
  • After compression 22.1 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 16.7 kB or 43% of the original size.

CSS Optimization

-74%

Potential reduce by 5.6 kB

  • Original 7.6 kB
  • After minification 5.3 kB
  • After compression 2.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. Fnana.jp needs all CSS files to be minified and compressed as it can save up to 5.6 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (32%)

Requests Now

28

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fnana.jp

fnana.jp

656 ms

default.css

default.css

198 ms

top.css

top.css

342 ms

meanmenu.css

meanmenu.css

347 ms

css

css

32 ms

jquery.min.js

jquery.min.js

33 ms

set.js

set.js

366 ms

jquery.masonry.min.js

jquery.masonry.min.js

366 ms

modernizr-transitions.js

modernizr-transitions.js

366 ms

jquery.meanmenu.js

jquery.meanmenu.js

364 ms

top.js

top.js

508 ms

logo_off.png

logo_off.png

196 ms

item01_on.png

item01_on.png

384 ms

item02_off.png

item02_off.png

194 ms

item03_off.png

item03_off.png

198 ms

item04_off.png

item04_off.png

1041 ms

item05_off.png

item05_off.png

209 ms

item06_off.png

item06_off.png

697 ms

item07_off.png

item07_off.png

817 ms

item08_off.png

item08_off.png

371 ms

item09_off.png

item09_off.png

869 ms

item10_off.png

item10_off.png

2060 ms

item11_off.png

item11_off.png

559 ms

item12_off.png

item12_off.png

735 ms

item13_off.png

item13_off.png

865 ms

item14_off.png

item14_off.png

909 ms

item15_off.png

item15_off.png

976 ms

ga.js

ga.js

9 ms

sKd0EMYPAh5PYCRKSryvWz8E0i7KZn-EPnyo3HZu7kw.woff

sKd0EMYPAh5PYCRKSryvWz8E0i7KZn-EPnyo3HZu7kw.woff

29 ms

__utm.gif

__utm.gif

16 ms

SEO Factors

fnana.jp SEO score

0

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

fnana.jp

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