Tools & Wizards About Us
iwasaki-bei.com screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

iwasaki-bei.com

IWASAKI Be-I Replica foods Tokyo, Japan – Iwasaki Be-I, which marks its 86th anniversary this yeear, is the leading company in the field of replica fo...

Page Load Speed

5.9 sec in total

First Response

1.4 sec

Resources Loaded

4.3 sec

Page Rendered

310 ms

iwasaki-bei.com screenshot

About Website

Welcome to iwasaki-bei.com homepage info - get ready to check IWASAKI Be I best content right away, or after learning these important things about iwasaki-bei.com

Iwasaki Be-I, which marks its 86th anniversary this yeear, is the leading company in the field of replica foods with the highest market share in the industry.

Visit iwasaki-bei.com

Key Findings

We analyzed Iwasaki-bei.com page load time and found that the first response time was 1.4 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

iwasaki-bei.com performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.698

7/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

www.iwasaki-bei.com

1357 ms

js

80 ms

wp-emoji-release.min.js

302 ms

style.min.css

467 ms

notosansjapanese.css

34 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 69% of them (38 requests) were addressed to the original Iwasaki-bei.com, 16% (9 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Iwasaki-bei.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (31%)

Content Size

4.4 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iwasaki-bei.com main page is 4.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 28.7 kB

  • Original 35.2 kB
  • After minification 29.9 kB
  • After compression 6.5 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.3 kB, which is 15% 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 28.7 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 20.1 kB

  • Original 2.8 MB
  • After minification 2.7 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. IWASAKI Be I images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 413.4 kB

  • Original 590.6 kB
  • After minification 543.0 kB
  • After compression 177.2 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 413.4 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 894.7 kB

  • Original 1.0 MB
  • After minification 903.4 kB
  • After compression 146.6 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. Iwasaki-bei.com needs all CSS files to be minified and compressed as it can save up to 894.7 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.iwasaki-bei.com

www.iwasaki-bei.com

1357 ms

js

js

80 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

302 ms

style.min.css

style.min.css

467 ms

notosansjapanese.css

notosansjapanese.css

34 ms

css

css

46 ms

bootstrap.min.css

bootstrap.min.css

952 ms

extralayers.css

extralayers.css

677 ms

settings.css

settings.css

860 ms

essentials.css

essentials.css

1546 ms

layout.css

layout.css

1208 ms

header-1.css

header-1.css

630 ms

blue.css

blue.css

795 ms

custom.css

custom.css

844 ms

logo_header.png

logo_header.png

959 ms

js

js

66 ms

analytics.js

analytics.js

20 ms

collect

collect

45 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

1198 ms

scripts.js

scripts.js

1225 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1118 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1305 ms

demo.revolution_slider.js

demo.revolution_slider.js

1232 ms

1x1.png

1x1.png

1274 ms

takeout_bn_01.jpg

takeout_bn_01.jpg

1717 ms

takeout_bn_02.jpg

takeout_bn_02.jpg

1668 ms

takeout_bn_03.jpg

takeout_bn_03.jpg

1668 ms

takeout_bn_04.jpg

takeout_bn_04.jpg

1490 ms

cl-1.png

cl-1.png

1799 ms

cl-2.png

cl-2.png

1746 ms

cl-3.png

cl-3.png

1792 ms

cl-4.png

cl-4.png

2013 ms

cl-5.png

cl-5.png

2013 ms

logo_footer.png

logo_footer.png

1877 ms

collect

collect

26 ms

ga-audiences

ga-audiences

34 ms

world-map.png

world-map.png

482 ms

footer_sprite.png

footer_sprite.png

518 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

67 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

68 ms

NotoSansJP-Regular.woff

NotoSansJP-Regular.woff

209 ms

NotoSansJP-Medium.woff

NotoSansJP-Medium.woff

209 ms

NotoSansJP-DemiLight.woff

NotoSansJP-DemiLight.woff

221 ms

NotoSansJP-Light.woff

NotoSansJP-Light.woff

218 ms

NotoSansJP-Thin.woff

NotoSansJP-Thin.woff

238 ms

NotoSansJP-Bold.woff

NotoSansJP-Bold.woff

219 ms

NotoSansJP-Black.woff

NotoSansJP-Black.woff

236 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

467 ms

bootstrap.min.js

bootstrap.min.js

448 ms

smoothscroll.js

smoothscroll.js

482 ms

loader.gif

loader.gif

451 ms

revicons.woff

revicons.woff

469 ms

slider_takeout.jpg

slider_takeout.jpg

522 ms

owl.carousel.min.js

owl.carousel.min.js

175 ms

jquery.mixitup.min.js

jquery.mixitup.min.js

170 ms

Accessibility Review

iwasaki-bei.com accessibility score

47

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

iwasaki-bei.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

iwasaki-bei.com SEO score

93

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iwasaki-bei.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Iwasaki-bei.com 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

iwasaki-bei.com

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