Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

fukumai.com

福米 - 出産内祝い米(体重米)、結婚式の引き出物にお米ギフト

Page Load Speed

8.2 sec in total

First Response

1.3 sec

Resources Loaded

6.3 sec

Page Rendered

544 ms

fukumai.com screenshot

About Website

Click here to check amazing Fukumai content. Otherwise, check out these important facts you probably never knew about fukumai.com

出産内祝い米(体重米)や結婚式でのご両親への記念品に最高級米を!

Visit fukumai.com

Key Findings

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

Performance Metrics

fukumai.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.9 s

89/100

10%

Network Requests Diagram

fukumai.com

1277 ms

styles.css

2004 ms

navi.css

1847 ms

calendar.css

1848 ms

index.css

2034 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 97% of them (63 requests) were addressed to the original Fukumai.com, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Fukumai.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.1 kB (6%)

Content Size

1.1 MB

After Optimization

1.0 MB

In fact, the total size of Fukumai.com main page is 1.1 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 27.6 kB

  • Original 36.0 kB
  • After minification 35.1 kB
  • After compression 8.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. 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 27.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 381 B

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

JavaScript Optimization

-52%

Potential reduce by 23.8 kB

  • Original 45.5 kB
  • After minification 35.7 kB
  • After compression 21.7 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 23.8 kB or 52% of the original size.

CSS Optimization

-76%

Potential reduce by 10.3 kB

  • Original 13.6 kB
  • After minification 10.6 kB
  • After compression 3.3 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. Fukumai.com needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (13%)

Requests Now

64

After Optimization

56

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

Accessibility Review

fukumai.com accessibility score

94

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.

Best Practices

fukumai.com best practices score

75

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

Serves images with low resolution

SEO Factors

fukumai.com SEO score

79

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fukumai.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 Fukumai.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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