Tools & Wizards About Us
fumin.jp screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

fumin.jp

株式会社 フミン

Page Load Speed

7.9 sec in total

First Response

526 ms

Resources Loaded

6.9 sec

Page Rendered

483 ms

fumin.jp screenshot

About Website

Welcome to fumin.jp homepage info - get ready to check Fumin best content right away, or after learning these important things about fumin.jp

私たち株式会社フミンは、人と自然にやさしい技術開発に取り組んでおります。福島県福島市。

Visit fumin.jp

Key Findings

We analyzed Fumin.jp page load time and found that the first response time was 526 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

fumin.jp performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

fumin.jp

526 ms

fumin.jp

1430 ms

import.css

532 ms

f_set.js

550 ms

base.css

517 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that all of those requests were addressed to Fumin.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Fumin.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.6 kB (5%)

Content Size

1.3 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 36.1 kB

  • Original 43.3 kB
  • After minification 34.2 kB
  • After compression 7.2 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 9.1 kB, which is 21% 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 36.1 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 16.4 kB

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

JavaScript Optimization

-55%

Potential reduce by 380 B

  • Original 697 B
  • After minification 611 B
  • After compression 317 B

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 380 B or 55% of the original size.

CSS Optimization

-79%

Potential reduce by 10.8 kB

  • Original 13.6 kB
  • After minification 12.3 kB
  • After compression 2.8 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. Fumin.jp needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

41

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fumin.jp

fumin.jp

526 ms

fumin.jp

fumin.jp

1430 ms

import.css

import.css

532 ms

f_set.js

f_set.js

550 ms

base.css

base.css

517 ms

print.css

print.css

194 ms

bg_body_home.jpg

bg_body_home.jpg

174 ms

bg_top_home.jpg

bg_top_home.jpg

1200 ms

navi_1.jpg

navi_1.jpg

351 ms

navi_2.jpg

navi_2.jpg

563 ms

navi_3.jpg

navi_3.jpg

692 ms

navi_4.jpg

navi_4.jpg

745 ms

navi_5.jpg

navi_5.jpg

696 ms

button61.gif

button61.gif

702 ms

button71.gif

button71.gif

948 ms

button7.gif

button7.gif

1032 ms

headnavi_3.jpg

headnavi_3.jpg

867 ms

ya_headnavi.jpg

ya_headnavi.jpg

875 ms

headnavi_1.jpg

headnavi_1.jpg

921 ms

headnavi_2.jpg

headnavi_2.jpg

1039 ms

bg_mainwholebg1.jpg

bg_mainwholebg1.jpg

1049 ms

bg_mainwholebg2.jpg

bg_mainwholebg2.jpg

1098 ms

bg_mainwhole_home.jpg

bg_mainwhole_home.jpg

1330 ms

home_2.jpg

home_2.jpg

1417 ms

home_1.gif

home_1.gif

1420 ms

bn_company_home.jpg

bn_company_home.jpg

1394 ms

bn_movie_home.jpg

bn_movie_home.jpg

1447 ms

home_8.jpg

home_8.jpg

1596 ms

home_3.jpg

home_3.jpg

1502 ms

bg_1.gif

bg_1.gif

1569 ms

nintei_logo.jpg

nintei_logo.jpg

4285 ms

home_4.jpg

home_4.jpg

1760 ms

bn_business_4_home.jpg

bn_business_4_home.jpg

1795 ms

bn_business_1_home.jpg

bn_business_1_home.jpg

1889 ms

sintel.jpg

sintel.jpg

2301 ms

ya_pagetop.jpg

ya_pagetop.jpg

1774 ms

bn_foot_1.jpg

bn_foot_1.jpg

1932 ms

bn_foot_4.jpg

bn_foot_4.jpg

2119 ms

facemark.jpg

facemark.jpg

2190 ms

kankyousyou.jpg

kankyousyou.jpg

2277 ms

image.jpg

image.jpg

2271 ms

bg_footwhole.jpg

bg_footwhole.jpg

2257 ms

bg_foot.jpg

bg_foot.jpg

2196 ms

Accessibility Review

fumin.jp accessibility score

69

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

fumin.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

fumin.jp SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fumin.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fumin.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

fumin.jp

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