Report Summary

  • 0

    Performance

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 0

    Best Practices

  • 50

    SEO

    Google-friendlier than
    18% of websites

shinpo.jp

業務用焼肉無煙ロースター販売シェアNo.1メーカーのシンポ株式会社業務用焼肉無煙ロースター販売シェアNo.1メーカーのシンポ株式会社

Page Load Speed

7.9 sec in total

First Response

1 sec

Resources Loaded

5.8 sec

Page Rendered

1.1 sec

shinpo.jp screenshot

About Website

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

美味しい×快適=繁盛店 Lineup 無煙ロースター世界シェアNo.1のシンポの豊富なラインナップから、お店の

Visit shinpo.jp

Key Findings

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

shinpo.jp performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

shinpo.jp

1043 ms

style.css

1956 ms

jquery-1.8.2.min.js

1503 ms

inquiry.js

678 ms

loginForm.js

708 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 87% of them (89 requests) were addressed to the original Shinpo.jp, 9% (9 requests) were made to Admin.shinpo.jp and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Shinpo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 872.2 kB (33%)

Content Size

2.7 MB

After Optimization

1.8 MB

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

HTML Optimization

-83%

Potential reduce by 41.2 kB

  • Original 49.6 kB
  • After minification 45.8 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 41.2 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 109.5 kB

  • Original 1.7 MB
  • After minification 1.6 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. Shinpo images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 504.1 kB

  • Original 626.1 kB
  • After minification 406.6 kB
  • After compression 122.0 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 504.1 kB or 81% of the original size.

CSS Optimization

-87%

Potential reduce by 217.3 kB

  • Original 250.4 kB
  • After minification 189.3 kB
  • After compression 33.1 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. Shinpo.jp needs all CSS files to be minified and compressed as it can save up to 217.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (41%)

Requests Now

101

After Optimization

60

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

Accessibility Review

shinpo.jp accessibility score

63

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

Document doesn't have a <title> element

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

SEO Factors

shinpo.jp SEO score

50

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

Document doesn't have a <title> element

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

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