Tools & Wizards About Us
store-ink.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

store-ink.jp

HOME - 株式会社STORE ink（ストアインク）｜公式ページ

Page Load Speed

3.4 sec in total

First Response

560 ms

Resources Loaded

2.7 sec

Page Rendered

149 ms

store-ink.jp screenshot

About Website

Click here to check amazing Store Ink content. Otherwise, check out these important facts you probably never knew about store-ink.jp

出版メディア、デジタルメディア、WEB販促、クリエイティブなどを展開するマーケティングカンパニーです。

Visit store-ink.jp

Key Findings

We analyzed Store-ink.jp page load time and found that the first response time was 560 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

store-ink.jp performance score

0

Network Requests Diagram

store-ink.jp

560 ms

urchin.js

5 ms

import.css

183 ms

common.js

528 ms

css_selector.js

362 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 88% of them (21 requests) were addressed to the original Store-ink.jp, 8% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Favo-net.jp. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Store-ink.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.9 kB (17%)

Content Size

427.9 kB

After Optimization

355.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Store-ink.jp main page is 427.9 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. Only 10% of websites need less resources to load. Images take 381.9 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 2.6 kB

  • Original 4.2 kB
  • After minification 4.0 kB
  • After compression 1.7 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 2.6 kB or 61% of the original size.

Image Optimization

-10%

Potential reduce by 39.2 kB

  • Original 381.9 kB
  • After minification 342.7 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. Store Ink images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 20.1 kB

  • Original 29.7 kB
  • After minification 24.0 kB
  • After compression 9.6 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 20.1 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 10.1 kB

  • Original 12.1 kB
  • After minification 8.9 kB
  • After compression 2.0 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. Store-ink.jp needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (45%)

Requests Now

22

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

store-ink.jp

store-ink.jp

560 ms

urchin.js

urchin.js

5 ms

import.css

import.css

183 ms

common.js

common.js

528 ms

css_selector.js

css_selector.js

362 ms

ud2.js

ud2.js

1023 ms

__utm.gif

__utm.gif

3 ms

base.css

base.css

192 ms

style.css

style.css

361 ms

hack.css

hack.css

364 ms

back_image.gif

back_image.gif

183 ms

head_top_logo.gif

head_top_logo.gif

178 ms

head_top_tytle.jpg

head_top_tytle.jpg

932 ms

cover_favo_mk.jpg

cover_favo_mk.jpg

1096 ms

cover_favo_kz.jpg

cover_favo_kz.jpg

1087 ms

cover_samurai.jpg

cover_samurai.jpg

527 ms

menu_wbgimg1.gif

menu_wbgimg1.gif

358 ms

menu_w02.gif

menu_w02.gif

360 ms

menu_w04.gif

menu_w04.gif

539 ms

menu_recruit.gif

menu_recruit.gif

540 ms

menu_w06.gif

menu_w06.gif

701 ms

foot_copyright.gif

foot_copyright.gif

718 ms

menu_wbgimg2.gif

menu_wbgimg2.gif

710 ms

menu_w05.gif

menu_w05.gif

866 ms

SEO Factors

store-ink.jp SEO score

0

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 Store-ink.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 Store-ink.jp 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

store-ink.jp

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