Tools & Wizards About Us
explode.jp screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

explode.jp

色見本の通信販売 - Ｇ＆Ｅ

Page Load Speed

8.3 sec in total

First Response

1.1 sec

Resources Loaded

7 sec

Page Rendered

135 ms

explode.jp screenshot

About Website

Visit explode.jp now to see the best up-to-date Explode content for Japan and also check out these interesting facts you probably never knew about explode.jp

PANTONE、DIC色見本帳、カラーチャートを即日発送。送料無料、代引手数料無料、請求書後払い、領収書発行もOKです。

Visit explode.jp

Key Findings

We analyzed Explode.jp page load time and found that the first response time was 1.1 sec and then it took 7.2 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

explode.jp performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

explode.jp

1115 ms

style.css

496 ms

style-soza.css

498 ms

lightbox.css

508 ms

jquery-1.7.2.min.js

1063 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 93% of them (82 requests) were addressed to the original Explode.jp, 2% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Explode.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.4 kB (34%)

Content Size

193.9 kB

After Optimization

128.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Explode.jp main page is 193.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. 25% of websites need less resources to load. Javascripts take 101.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 21.4 kB

  • Original 26.8 kB
  • After minification 23.3 kB
  • After compression 5.4 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 3.5 kB, which is 13% 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.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 78 B

  • Original 61.6 kB
  • After minification 61.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. Explode images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 42.9 kB

  • Original 101.9 kB
  • After minification 101.9 kB
  • After compression 59.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 42.9 kB or 42% of the original size.

CSS Optimization

-28%

Potential reduce by 1.0 kB

  • Original 3.7 kB
  • After minification 3.7 kB
  • After compression 2.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. Explode.jp needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (46%)

Requests Now

87

After Optimization

47

  • Images
  • JavaScript
  • CSS

The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Explode. 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 as a result speed up the page load time.

Network Requests Diagram

explode.jp

explode.jp

1115 ms

style.css

style.css

496 ms

style-soza.css

style-soza.css

498 ms

lightbox.css

lightbox.css

508 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1063 ms

lightbox.js

lightbox.js

539 ms

conversion.js

conversion.js

75 ms

gtm.js

gtm.js

96 ms

2014_header_logo.gif

2014_header_logo.gif

346 ms

2014_header_info.gif

2014_header_info.gif

346 ms

2014_header_privacy.gif

2014_header_privacy.gif

346 ms

2014_header_guide.gif

2014_header_guide.gif

345 ms

2014_header_mypage.gif

2014_header_mypage.gif

351 ms

2014_header_cart.gif

2014_header_cart.gif

363 ms

2014_header_txt.gif

2014_header_txt.gif

670 ms

2014_gmenu_side.gif

2014_gmenu_side.gif

774 ms

2014_gmenu_home_a.gif

2014_gmenu_home_a.gif

779 ms

2014_gmenu_chart.gif

2014_gmenu_chart.gif

778 ms

2014_gmenu_colorguide.gif

2014_gmenu_colorguide.gif

778 ms

2014_gmenu_pantone.gif

2014_gmenu_pantone.gif

772 ms

2014_gmenu_cdrom.gif

2014_gmenu_cdrom.gif

1025 ms

2014_gmenu_book.gif

2014_gmenu_book.gif

1109 ms

2014_gmenu_tools.gif

2014_gmenu_tools.gif

1105 ms

category_link.gif

category_link.gif

1114 ms

category_link_02.gif

category_link_02.gif

1113 ms

span.gif

span.gif

1123 ms

top_main_img.jpg

top_main_img.jpg

2065 ms

main_news.gif

main_news.gif

1441 ms

soza_navi_subcat_all.gif

soza_navi_subcat_all.gif

1439 ms

menu-mixa.gif

menu-mixa.gif

1454 ms

menu-mixa-ta.gif

menu-mixa-ta.gif

1462 ms

menu-daj.gif

menu-daj.gif

1473 ms

menu-ilso.gif

menu-ilso.gif

1764 ms

menu-makunouchi.gif

menu-makunouchi.gif

1780 ms

menu-oden.gif

menu-oden.gif

1790 ms

menu-d-soza.gif

menu-d-soza.gif

1814 ms

menu-d-sozar.gif

menu-d-sozar.gif

1837 ms

menu-d-sozabooks.gif

menu-d-sozabooks.gif

2093 ms

menu-gran.gif

menu-gran.gif

2117 ms

menu-uri-vip.gif

menu-uri-vip.gif

2140 ms

menu-uri-jfi.gif

menu-uri-jfi.gif

2139 ms

menu-stocksozai.gif

menu-stocksozai.gif

2188 ms

soza_navi_subcat_syokuzai.gif

soza_navi_subcat_syokuzai.gif

2404 ms

39 ms

tag.js

tag.js

20 ms

menu-maruk.gif

menu-maruk.gif

2404 ms

52 ms

js

js

56 ms

soza_navi_subcat_syokubutsu.gif

soza_navi_subcat_syokubutsu.gif

2116 ms

menu-face.gif

menu-face.gif

2125 ms

soza_navi_subcat_illust.gif

soza_navi_subcat_illust.gif

2134 ms

menu-mixa-ir.gif

menu-mixa-ir.gif

2184 ms

menu-kyo-ib.gif

menu-kyo-ib.gif

2394 ms

menu-pra-g.gif

menu-pra-g.gif

2426 ms

menu-pra-p.gif

menu-pra-p.gif

2127 ms

menu-pra-m.gif

menu-pra-m.gif

2035 ms

menu-pra-h.gif

menu-pra-h.gif

2042 ms

menu-pra-k.gif

menu-pra-k.gif

2091 ms

menu-fudewaza.gif

menu-fudewaza.gif

2291 ms

menu-tatsumidou.gif

menu-tatsumidou.gif

2344 ms

menu-gaou.gif

menu-gaou.gif

2097 ms

soza_navi_subcat_background.gif

soza_navi_subcat_background.gif

2052 ms

menu-d-wss.gif

menu-d-wss.gif

2044 ms

menu-d-hana.gif

menu-d-hana.gif

2093 ms

menu-gr-bit.gif

menu-gr-bit.gif

2280 ms

soza_navi_subcat_cg.gif

soza_navi_subcat_cg.gif

2335 ms

menu-vgl.gif

menu-vgl.gif

2022 ms

menu-stocklayer.gif

menu-stocklayer.gif

2035 ms

soza_navi_subcat_jinbutu.gif

soza_navi_subcat_jinbutu.gif

2027 ms

menu-mixa-na.gif

menu-mixa-na.gif

2089 ms

menu-mixa-gr.gif

menu-mixa-gr.gif

2256 ms

menu-iconics.gif

menu-iconics.gif

2018 ms

menu-iwf.gif

menu-iwf.gif

2018 ms

menu-egaos.gif

menu-egaos.gif

2019 ms

menu-pra-gphoto.gif

menu-pra-gphoto.gif

2015 ms

menu-tgv.gif

menu-tgv.gif

2048 ms

menu-d-qxq.gif

menu-d-qxq.gif

2009 ms

menu-tomoco.gif

menu-tomoco.gif

2030 ms

soza_navi_subcat_gaikoku.gif

soza_navi_subcat_gaikoku.gif

2048 ms

menu-uri-gv.gif

menu-uri-gv.gif

2017 ms

soza_navi_subcat_fuukei.gif

soza_navi_subcat_fuukei.gif

2024 ms

menu-mixa-zenkoku.gif

menu-mixa-zenkoku.gif

2059 ms

menu-mixa-lm.gif

menu-mixa-lm.gif

2004 ms

menu-mixa-big.gif

menu-mixa-big.gif

2015 ms

menu-uri-tc.gif

menu-uri-tc.gif

2052 ms

footer_info_img.gif

footer_info_img.gif

2538 ms

loading.gif

loading.gif

2194 ms

close.png

close.png

2058 ms

Accessibility Review

explode.jp accessibility score

81

Accessibility Issues

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

Best Practices

explode.jp best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

explode.jp SEO score

64

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

explode.jp

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