Tools & Wizards About Us
inknavi.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

inknavi.com

純正の半額！互換インクカートリッジ通販　インクナビ

Page Load Speed

6.1 sec in total

First Response

795 ms

Resources Loaded

4.7 sec

Page Rendered

518 ms

inknavi.com screenshot

About Website

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

純正の半額！互換インクカートリッジ通販　インクナビ

Visit inknavi.com

Key Findings

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

Performance Metrics

inknavi.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.145

77/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

inknavi.com

795 ms

m_sys_common.css

317 ms

import.css

346 ms

script.js

360 ms

conversion.js

15 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 22% of them (29 requests) were addressed to the original Inknavi.com, 22% (28 requests) were made to Image.rakuten.co.jp and 11% (14 requests) were made to Rakuten.ne.jp. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Image.rakuten.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 282.7 kB (29%)

Content Size

990.1 kB

After Optimization

707.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inknavi.com main page is 990.1 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. 50% of websites need less resources to load. Images take 621.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 53.3 kB

  • Original 66.3 kB
  • After minification 56.1 kB
  • After compression 13.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 10.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 53.3 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 30.6 kB

  • Original 621.2 kB
  • After minification 590.6 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. Inknavi images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 154.4 kB

  • Original 248.4 kB
  • After minification 210.5 kB
  • After compression 94.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 154.4 kB or 62% of the original size.

CSS Optimization

-82%

Potential reduce by 44.4 kB

  • Original 54.2 kB
  • After minification 38.0 kB
  • After compression 9.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. Inknavi.com needs all CSS files to be minified and compressed as it can save up to 44.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (52%)

Requests Now

123

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inknavi.com

inknavi.com

795 ms

m_sys_common.css

m_sys_common.css

317 ms

import.css

import.css

346 ms

script.js

script.js

360 ms

conversion.js

conversion.js

15 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

718 ms

check_history.css

check_history.css

312 ms

pager.css

pager.css

315 ms

shopdetail.css

shopdetail.css

338 ms

ranking.css

ranking.css

327 ms

basket.css

basket.css

340 ms

security.css

security.css

359 ms

category_menu.css

category_menu.css

638 ms

topicpath.css

topicpath.css

650 ms

catalog.css

catalog.css

648 ms

header_logo_ink.jpg

header_logo_ink.jpg

821 ms

6k01h-1.gif

6k01h-1.gif

205 ms

search_bt.gif

search_bt.gif

182 ms

count3.makeshop.jp

count3.makeshop.jp

494 ms

footer_h01.gif

footer_h01.gif

311 ms

soryo-muryo-0209.jpg

soryo-muryo-0209.jpg

654 ms

tl.php

tl.php

619 ms

header_phone.jpg

header_phone.jpg

661 ms

header_signup.jpg

header_signup.jpg

680 ms

header_pipe.jpg

header_pipe.jpg

685 ms

header_login.jpg

header_login.jpg

692 ms

header_viewcart.jpg

header_viewcart.jpg

717 ms

side_inq_01.jpg

side_inq_01.jpg

1005 ms

side_inq_02.jpg

side_inq_02.jpg

1019 ms

side_inq_03_ink.jpg

side_inq_03_ink.jpg

1018 ms

side_inq_04.jpg

side_inq_04.jpg

1055 ms

side_inq_05.jpg

side_inq_05.jpg

1084 ms

side_inq_06.jpg

side_inq_06.jpg

1176 ms

side_inq_07.jpg

side_inq_07.jpg

1378 ms

side_inq_08.jpg

side_inq_08.jpg

1376 ms

makerlist_title.jpg

makerlist_title.jpg

1376 ms

futa.jpg

futa.jpg

1173 ms

siharai.gif

siharai.gif

341 ms

footer_h01a.gif

footer_h01a.gif

496 ms

anshin_hosho_l.jpg

anshin_hosho_l.jpg

1185 ms

footer_h02.gif

footer_h02.gif

276 ms

footer_h03.gif

footer_h03.gif

259 ms

footer_h04.gif

footer_h04.gif

265 ms

footer_i_time.gif

footer_i_time.gif

278 ms

footer_h06.gif

footer_h06.gif

263 ms

footer_h07.gif

footer_h07.gif

345 ms

6k01h-2.gif

6k01h-2.gif

375 ms

6k01h-3.gif

6k01h-3.gif

216 ms

6k01h-4.gif

6k01h-4.gif

208 ms

6k01h-5.gif

6k01h-5.gif

411 ms

6k01h-6.gif

6k01h-6.gif

403 ms

sarch-2.gif

sarch-2.gif

642 ms

ink_ct.jpg

ink_ct.jpg

429 ms

6k03a-ca.gif

6k03a-ca.gif

1344 ms

6k03a-ep.gif

6k03a-ep.gif

592 ms

6k03a-br.gif

6k03a-br.gif

797 ms

6k03a-hp.gif

6k03a-hp.gif

1485 ms

6k03a-de.gif

6k03a-de.gif

641 ms

6k03a-le.gif

6k03a-le.gif

1078 ms

6k03a-ri.gif

6k03a-ri.gif

805 ms

shin10b.jpg

shin10b.jpg

975 ms

hazimetenogokan-bana.jpg

hazimetenogokan-bana.jpg

973 ms

i-d-bana1.jpg

i-d-bana1.jpg

1036 ms

bn01d.gif

bn01d.gif

1336 ms

6bn06t-1-prc3333.gif

6bn06t-1-prc3333.gif

1259 ms

6bn01ad-c.gif

6bn01ad-c.gif

1391 ms

6bn01ad-e.gif

6bn01ad-e.gif

1263 ms

6bn01ad-b.gif

6bn01ad-b.gif

1462 ms

6bn01ad-h.gif

6bn01ad-h.gif

1462 ms

6bn01ad-d.gif

6bn01ad-d.gif

1558 ms

6bn01ad-l.gif

6bn01ad-l.gif

1743 ms

6bn01ad-r.gif

6bn01ad-r.gif

1857 ms

topimage_logo.jpg

topimage_logo.jpg

885 ms

478 ms

rogin-180.gif

rogin-180.gif

2902 ms

is_show_gmo_header.html

is_show_gmo_header.html

930 ms

aq_tag_aos.js

aq_tag_aos.js

161 ms

380 ms

search-800-inknavi.htm

search-800-inknavi.htm

342 ms

43 ms

ebis_tag.php

ebis_tag.php

557 ms

34 ms

46 ms

EM34BYVZ46DUGEQNJE6A

EM34BYVZ46DUGEQNJE6A

139 ms

import.css

import.css

193 ms

rakutenMfw.js

rakutenMfw.js

179 ms

gmsync

gmsync

304 ms

segmentation.js

segmentation.js

10 ms

360 ms

cnt

cnt

336 ms

jquery-ui.css

jquery-ui.css

26 ms

css

css

44 ms

calendar.css

calendar.css

234 ms

jquery.min.js

jquery.min.js

47 ms

jquery-ui.js

jquery-ui.js

89 ms

jquery.ui.datepicker-ja.js

jquery.ui.datepicker-ja.js

85 ms

jquery.ui.datepicker-ogaria.js

jquery.ui.datepicker-ogaria.js

87 ms

jquery.contextmenu.js

jquery.contextmenu.js

88 ms

calendar.js

calendar.js

83 ms

pa2.min.js

pa2.min.js

28 ms

reset.css

reset.css

201 ms

funcs.css

funcs.css

199 ms

log.php

log.php

379 ms

MViwy4K6e56oHcyeMzjbCQ.ttf

MViwy4K6e56oHcyeMzjbCQ.ttf

44 ms

ippatsu_step1.png

ippatsu_step1.png

521 ms

ippatsu_arrow.png

ippatsu_arrow.png

515 ms

ippatsu_step2.png

ippatsu_step2.png

534 ms

ippatsu_step3.png

ippatsu_step3.png

553 ms

ippatsu_btn.png

ippatsu_btn.png

563 ms

ippatsu_title_light.jpg

ippatsu_title_light.jpg

204 ms

13 ms

554 ms

calendar.json

calendar.json

245 ms

13 ms

17 ms

ga.js

ga.js

31 ms

__utm.gif

__utm.gif

23 ms

beacon.html

beacon.html

13 ms

pixel

pixel

23 ms

cs

cs

311 ms

Pug

Pug

18 ms

set

set

325 ms

sync

sync

10 ms

sd

sd

4 ms

sync

sync

352 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

24 ms

tap.php

tap.php

185 ms

mapuser

mapuser

150 ms

sync

sync

241 ms

sync

sync

263 ms

Accessibility Review

inknavi.com accessibility score

87

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

High

Links do not have a discernible name

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

inknavi.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inknavi.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inknavi.com 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 Inknavi.com main page’s claimed encoding is euc-jp. 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

inknavi.com

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