Tools & Wizards About Us
ippinkan.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 41

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

ippinkan.com

大阪・日本橋　オーディオ・ホームシアター専門店　逸品館

Page Load Speed

5.7 sec in total

First Response

2 sec

Resources Loaded

3.1 sec

Page Rendered

542 ms

ippinkan.com screenshot

About Website

Click here to check amazing Ippinkan content for Japan. Otherwise, check out these important facts you probably never knew about ippinkan.com

オーディオ逸品館　情報ページです。ご注文・お問い合わせ・各種ご相談は専門店(株)逸品館が承ります。

Visit ippinkan.com

Key Findings

We analyzed Ippinkan.com page load time and found that the first response time was 2 sec and then it took 3.7 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

ippinkan.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

54/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

ippinkan.com

2007 ms

new-web_bk.jpg

380 ms

ippinkan_logo_90.jpg

565 ms

btn_ip.com.jpg

822 ms

btn_ip.jp.jpg

807 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 21% of them (6 requests) were addressed to the original Ippinkan.com, 41% (12 requests) were made to Gigaplus.makeshop.jp and 24% (7 requests) were made to Ippinkan.jp. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ippinkan.com.

Page Optimization Overview & Recommendations

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

Content Size

5.9 MB

After Optimization

5.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ippinkan.com main page is 5.9 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 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 92.8 kB

  • Original 105.6 kB
  • After minification 66.9 kB
  • After compression 12.8 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 38.7 kB, which is 37% 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 92.8 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 120.1 kB

  • Original 5.6 MB
  • After minification 5.4 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. Ippinkan images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 91.5 kB

  • Original 134.8 kB
  • After minification 124.2 kB
  • After compression 43.3 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 91.5 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 65.5 kB

  • Original 78.3 kB
  • After minification 53.3 kB
  • After compression 12.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. Ippinkan.com needs all CSS files to be minified and compressed as it can save up to 65.5 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

28

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ippinkan. 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

ippinkan.com

ippinkan.com

2007 ms

new-web_bk.jpg

new-web_bk.jpg

380 ms

ippinkan_logo_90.jpg

ippinkan_logo_90.jpg

565 ms

btn_ip.com.jpg

btn_ip.com.jpg

822 ms

btn_ip.jp.jpg

btn_ip.jp.jpg

807 ms

btn_ip.used.jpg

btn_ip.used.jpg

906 ms

btn_e.ip.jpg

btn_e.ip.jpg

1139 ms

zerrulea.gif

zerrulea.gif

189 ms

rental.jpg

rental.jpg

691 ms

page396.html

page396.html

931 ms

sitadori.jpg

sitadori.jpg

883 ms

cashback_new_150.jpg

cashback_new_150.jpg

1075 ms

sale_info.jpg

sale_info.jpg

778 ms

page23.html

page23.html

773 ms

page23.html

page23.html

785 ms

page23.html

page23.html

786 ms

zerbul1a.gif

zerbul1a.gif

200 ms

zerbul2a.gif

zerbul2a.gif

188 ms

m_sys_common.css

m_sys_common.css

333 ms

import.css

import.css

338 ms

script.js

script.js

343 ms

commonDesign.css

commonDesign.css

185 ms

jquery.min.js

jquery.min.js

384 ms

jquery.event.hover.js

jquery.event.hover.js

187 ms

jquery.xdomainajax.js

jquery.xdomainajax.js

329 ms

0yenReplace.js

0yenReplace.js

314 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

344 ms

jquery.bxslider.css

jquery.bxslider.css

341 ms

purl.js

purl.js

343 ms

Accessibility Review

ippinkan.com accessibility score

41

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

ippinkan.com SEO score

50

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ippinkan.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 Ippinkan.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

ippinkan.com

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