Tools & Wizards About Us
inkan.pro screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

inkan.pro

inkan.pro

Page Load Speed

9.6 sec in total

First Response

2 sec

Resources Loaded

7.3 sec

Page Rendered

275 ms

inkan.pro screenshot

About Website

Click here to check amazing Inkan content. Otherwise, check out these important facts you probably never knew about inkan.pro

国士堂は、はんこ作成・販売の専門サイトです。個人様向けの認印、銀行印、実印はもちろん、会社様向けの法人印、角印、ゴム印など全ての印章を取り扱っている通販サイトです。お急ぎのお客様も安心の即日発送も対応可能。全国一律、送料無料でお届け致します。

Visit inkan.pro

Key Findings

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

inkan.pro performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.199

62/100

15%

TTI (Time to Interactive)

Value3.0 s

95/100

10%

Network Requests Diagram

inkan.pro

1972 ms

reset.css

347 ms

common.css

709 ms

index.js

357 ms

inkan.pro

1757 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 88% of them (80 requests) were addressed to the original Inkan.pro, 3% (3 requests) were made to Hankoman.jp and 2% (2 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 Inkan.pro.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.2 kB (16%)

Content Size

360.0 kB

After Optimization

303.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inkan.pro main page is 360.0 kB. 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 268.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 32.4 kB

  • Original 41.6 kB
  • After minification 35.2 kB
  • After compression 9.1 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 6.4 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 32.4 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 886 B

  • Original 268.4 kB
  • After minification 267.5 kB

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. Inkan images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 8.2 kB

  • Original 32.4 kB
  • After minification 30.8 kB
  • After compression 24.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 8.2 kB or 25% of the original size.

CSS Optimization

-83%

Potential reduce by 14.7 kB

  • Original 17.6 kB
  • After minification 12.2 kB
  • After compression 2.9 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. Inkan.pro needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

74

  • AJAX
  • Images
  • JavaScript
  • CSS

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

inkan.pro

inkan.pro

1972 ms

reset.css

reset.css

347 ms

common.css

common.css

709 ms

index.js

index.js

357 ms

inkan.pro

inkan.pro

1757 ms

2nd_gets.php

2nd_gets.php

331 ms

clickheat.js

clickheat.js

531 ms

gtm.js

gtm.js

62 ms

card_taiou.jpg

card_taiou.jpg

602 ms

bnr.gif

bnr.gif

311 ms

convenience.jpg

convenience.jpg

795 ms

global.jpg

global.jpg

628 ms

logo.gif

logo.gif

181 ms

topText.gif

topText.gif

187 ms

cartBtn.gif

cartBtn.gif

177 ms

menuBg.gif

menuBg.gif

186 ms

menu01.gif

menu01.gif

350 ms

menu02.gif

menu02.gif

360 ms

menu03.gif

menu03.gif

368 ms

menu04.gif

menu04.gif

362 ms

menu05.gif

menu05.gif

367 ms

menu06.gif

menu06.gif

379 ms

title_menu.gif

title_menu.gif

524 ms

arrow.gif

arrow.gif

543 ms

left_menu01.gif

left_menu01.gif

752 ms

left_menu02.gif

left_menu02.gif

552 ms

support.gif

support.gif

737 ms

recoImage.gif

recoImage.gif

1139 ms

1112.png

1112.png

872 ms

header_111.jpg

header_111.jpg

1448 ms

top008.jpg

top008.jpg

734 ms

top009.jpg

top009.jpg

919 ms

top006.jpg

top006.jpg

924 ms

top007.jpg

top007.jpg

930 ms

top01.jpg

top01.jpg

1047 ms

subBg.gif

subBg.gif

1099 ms

icon_jitsu.gif

icon_jitsu.gif

1110 ms

icon_soku.gif

icon_soku.gif

1108 ms

hanko_image01.jpg

hanko_image01.jpg

1435 ms

icon_bank.gif

icon_bank.gif

1279 ms

hanko_image11.jpg

hanko_image11.jpg

1466 ms

icon_kaku.gif

icon_kaku.gif

1294 ms

hanko_image06.jpg

hanko_image06.jpg

1516 ms

hanko_image16.jpg

hanko_image16.jpg

1460 ms

hanko_image17.jpg

hanko_image17.jpg

1479 ms

icon_3set.gif

icon_3set.gif

1608 ms

hanko_image04.jpg

hanko_image04.jpg

1632 ms

2014081231385.gif

2014081231385.gif

299 ms

icon_4set.gif

icon_4set.gif

1605 ms

analytics.js

analytics.js

4 ms

collect

collect

3 ms

collect

collect

69 ms

hanko_image09.jpg

hanko_image09.jpg

1479 ms

icon_other.gif

icon_other.gif

1490 ms

hanko_image13.jpg

hanko_image13.jpg

1529 ms

hanko_image14.jpg

hanko_image14.jpg

1602 ms

hanko_image15.jpg

hanko_image15.jpg

1472 ms

mat_akane.jpg

mat_akane.jpg

1471 ms

mat_satsuma.jpg

mat_satsuma.jpg

1471 ms

mat_kurosuigyu.jpg

mat_kurosuigyu.jpg

1489 ms

mat_oreo.jpg

mat_oreo.jpg

1537 ms

mat_saika_red.jpg

mat_saika_red.jpg

1584 ms

mat_saika_brown.jpg

mat_saika_brown.jpg

1478 ms

mat_kaede_black.jpg

mat_kaede_black.jpg

1468 ms

mat_kaede_brown.jpg

mat_kaede_brown.jpg

1462 ms

mat_byakudan.jpg

mat_byakudan.jpg

1305 ms

mat_kohaku.jpg

mat_kohaku.jpg

1359 ms

mat_kurosuigyu_cr.jpg

mat_kurosuigyu_cr.jpg

1386 ms

mat_gyukaku.jpg

mat_gyukaku.jpg

1311 ms

mat_zouge.jpg

mat_zouge.jpg

1272 ms

mat_titan.jpg

mat_titan.jpg

1266 ms

hanko_image18.jpg

hanko_image18.jpg

1296 ms

hanko_image19.jpg

hanko_image19.jpg

1239 ms

hanko_image21.jpg

hanko_image21.jpg

1212 ms

hanko_image22.jpg

hanko_image22.jpg

1265 ms

hanko_image20.jpg

hanko_image20.jpg

1258 ms

namepenBnr.gif

namepenBnr.gif

1431 ms

jyusyoinBnr.gif

jyusyoinBnr.gif

1317 ms

stampBnr.gif

stampBnr.gif

1371 ms

sub_index01.gif

sub_index01.gif

1054 ms

flow.gif

flow.gif

1110 ms

sub_index02.gif

sub_index02.gif

1098 ms

subImage.jpg

subImage.jpg

1545 ms

sub_index03.gif

sub_index03.gif

1255 ms

sub_index04.gif

sub_index04.gif

1233 ms

tel.gif

tel.gif

1149 ms

taku_col_logo.gif

taku_col_logo.gif

1150 ms

yamato.gif

yamato.gif

1214 ms

time.gif

time.gif

1263 ms

footer_bg.gif

footer_bg.gif

1264 ms

inkan.pro

inkan.pro

1556 ms

Accessibility Review

inkan.pro accessibility score

53

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.

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

<frame> or <iframe> elements do not have a title

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

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

inkan.pro best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

inkan.pro SEO score

83

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

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

    N/A

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inkan.pro can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Inkan.pro 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

inkan.pro

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