Tools & Wizards About Us
grapac.co.jp screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

grapac.co.jp

3D印刷・紙器・パッケージの企画・製造｜グラパックジャパン - GRAPAC JAPAN

Page Load Speed

3.7 sec in total

First Response

443 ms

Resources Loaded

2.9 sec

Page Rendered

292 ms

grapac.co.jp screenshot

About Website

Welcome to grapac.co.jp homepage info - get ready to check GRAPAC best content right away, or after learning these important things about grapac.co.jp

グラパックジャパンは、紙、印刷、パッケージ、3D印刷のエキスパートとしてお客様のあらゆるニーズにお応えします。

Visit grapac.co.jp

Key Findings

We analyzed Grapac.co.jp page load time and found that the first response time was 443 ms and then it took 3.2 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

grapac.co.jp performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.363

30/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

grapac.co.jp

443 ms

bootstrap.min.css

579 ms

new_common.css

285 ms

ajust_bootstrap.css

289 ms

cookie_confirm.css

290 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 87% of them (33 requests) were addressed to the original Grapac.co.jp, 8% (3 requests) were made to Contents.bownow.jp and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Grapac.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 658.4 kB (24%)

Content Size

2.7 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grapac.co.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. 40% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 21.3 kB

  • Original 26.0 kB
  • After minification 14.9 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 11.1 kB, which is 43% 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 21.3 kB or 82% of the original size.

Image Optimization

-15%

Potential reduce by 351.8 kB

  • Original 2.3 MB
  • After minification 1.9 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. Obviously, GRAPAC needs image optimization as it can save up to 351.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 154.6 kB

  • Original 233.0 kB
  • After minification 233.0 kB
  • After compression 78.4 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.6 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 130.7 kB

  • Original 154.3 kB
  • After minification 149.2 kB
  • After compression 23.6 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. Grapac.co.jp needs all CSS files to be minified and compressed as it can save up to 130.7 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

grapac.co.jp

grapac.co.jp

443 ms

bootstrap.min.css

bootstrap.min.css

579 ms

new_common.css

new_common.css

285 ms

ajust_bootstrap.css

ajust_bootstrap.css

289 ms

cookie_confirm.css

cookie_confirm.css

290 ms

cookie_confirm.js

cookie_confirm.js

310 ms

ajust_smartphone.css

ajust_smartphone.css

311 ms

css

css

32 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

710 ms

bootstrap.min.js

bootstrap.min.js

722 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

727 ms

js

js

50 ms

01_logo_grapacKANA.svg

01_logo_grapacKANA.svg

146 ms

01_logo_grapac.png

01_logo_grapac.png

309 ms

03.png

03.png

727 ms

03_sp.png

03_sp.png

1892 ms

menu_arrow.png

menu_arrow.png

145 ms

sales_inquiry.png

sales_inquiry.png

311 ms

gaplas_web.jpg

gaplas_web.jpg

1011 ms

banner_grapacmaster.gif

banner_grapacmaster.gif

290 ms

top_net.gif

top_net.gif

436 ms

package.png

package.png

1080 ms

pop.jpeg

pop.jpeg

778 ms

game.jpeg

game.jpeg

872 ms

stationery.jpeg

stationery.jpeg

871 ms

d_print.jpg

d_print.jpg

934 ms

brio.jpg

brio.jpg

1017 ms

gaplas.jpg

gaplas.jpg

1017 ms

wedys.png

wedys.png

1090 ms

yt_logo.png

yt_logo.png

1155 ms

glyph-logo_May2016.png

glyph-logo_May2016.png

1162 ms

twitter.gif

twitter.gif

1162 ms

epc_img.gif

epc_img.gif

1234 ms

kumiai03.gif

kumiai03.gif

1245 ms

01_logo_grapacKANA.png

01_logo_grapacKANA.png

1299 ms

trace.js

trace.js

683 ms

trace.js

trace.js

174 ms

trace.js

trace.js

175 ms

Accessibility Review

grapac.co.jp accessibility score

82

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.

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

Definition list items are not wrapped in <dl> elements

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

Links do not have a discernible name

Best Practices

grapac.co.jp best practices score

75

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

High

Page has valid source maps

SEO Factors

grapac.co.jp SEO score

91

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Grapac.co.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 Grapac.co.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

grapac.co.jp

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