Tools & Wizards About Us
comply.jp screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

comply.jp

コンプライ™ | イヤホンチップで生まれ変わるあなたのイヤホン

Page Load Speed

25.6 sec in total

First Response

2.2 sec

Resources Loaded

19.9 sec

Page Rendered

3.5 sec

comply.jp screenshot

About Website

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

コンプライは、遮音性、装着感、原音伝達性に優れた、イヤホン性能を最大限に引き出すイヤホンチップです。

Visit comply.jp

Key Findings

We analyzed Comply.jp page load time and found that the first response time was 2.2 sec and then it took 23.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

comply.jp performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value32.0 s

0/100

25%

SI (Speed Index)

Value20.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,980 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.372

28/100

15%

TTI (Time to Interactive)

Value58.2 s

0/100

10%

Network Requests Diagram

www.comply.jp

2189 ms

analytics.js

66 ms

wp-emoji-release.min.js

188 ms

style.min.css

368 ms

slick.css

65 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 57% of them (60 requests) were addressed to the original Comply.jp, 17% (18 requests) were made to Platform.twitter.com and 6% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (12.3 sec) belongs to the original domain Comply.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (17%)

Content Size

7.9 MB

After Optimization

6.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Comply.jp main page is 7.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 45.2 kB

  • Original 56.4 kB
  • After minification 45.1 kB
  • After compression 11.2 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.3 kB, which is 20% 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 45.2 kB or 80% of the original size.

Image Optimization

-15%

Potential reduce by 1.1 MB

  • Original 7.2 MB
  • After minification 6.2 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, Comply needs image optimization as it can save up to 1.1 MB 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

-40%

Potential reduce by 205.9 kB

  • Original 510.7 kB
  • After minification 510.7 kB
  • After compression 304.8 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 205.9 kB or 40% of the original size.

CSS Optimization

-12%

Potential reduce by 17.4 kB

  • Original 149.0 kB
  • After minification 149.0 kB
  • After compression 131.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. Comply.jp needs all CSS files to be minified and compressed as it can save up to 17.4 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (56%)

Requests Now

99

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.comply.jp

www.comply.jp

2189 ms

analytics.js

analytics.js

66 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

188 ms

style.min.css

style.min.css

368 ms

slick.css

slick.css

65 ms

css

css

68 ms

basic.css

basic.css

523 ms

layout.css

layout.css

532 ms

modal.css

modal.css

784 ms

fullscreen.css

fullscreen.css

552 ms

swipebox.min.css

swipebox.min.css

538 ms

styles.css

styles.css

896 ms

bootstrap.min.css

bootstrap.min.css

868 ms

styles.css

styles.css

720 ms

styles.css

styles.css

1178 ms

cftf.min.css

cftf.min.css

78 ms

jquery.min.js

jquery.min.js

54 ms

modal.js

modal.js

741 ms

customize.js

customize.js

903 ms

langswitcher.js

langswitcher.js

922 ms

jquery.cookie.js

jquery.cookie.js

965 ms

fullscreen.js

fullscreen.js

1041 ms

menudrop.js

menudrop.js

1076 ms

common.js

common.js

1080 ms

iselector.js

iselector.js

1103 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1143 ms

jquery.easyListSplitter.js

jquery.easyListSplitter.js

1213 ms

bgstretcher.js

bgstretcher.js

1261 ms

pc.js

pc.js

1260 ms

sp.js

sp.js

1283 ms

js

js

90 ms

headphone-app.js

headphone-app.js

1326 ms

widgets.js

widgets.js

53 ms

cftf.min.js

cftf.min.js

85 ms

collect

collect

13 ms

js

js

48 ms

css

css

18 ms

layout.css

layout.css

212 ms

sfNeqLh9AA4

sfNeqLh9AA4

161 ms

sns1.png

sns1.png

1024 ms

logo.png

logo.png

225 ms

btn_sp_menu.png

btn_sp_menu.png

562 ms

btn_close.png

btn_close.png

558 ms

btn_cart.png

btn_cart.png

225 ms

btn_search_tips_pc.png

btn_search_tips_pc.png

788 ms

prize.png

prize.png

502 ms

prize2.png

prize2.png

502 ms

p1.jpg

p1.jpg

3374 ms

logo.png

logo.png

1412 ms

sample.png

sample.png

1349 ms

t200.png

t200.png

1597 ms

btn_back.png

btn_back.png

1066 ms

TZicon.png

TZicon.png

1994 ms

IconTZ.png

IconTZ.png

1744 ms

TRZicon.jpg

TRZicon.jpg

4059 ms

IconTRZ.png

IconTRZ.png

2107 ms

TOZicon.jpg

TOZicon.jpg

5392 ms

IconTOZ.png

IconTOZ.png

2252 ms

TWicon.jpg

TWicon.jpg

3049 ms

IconTW.png

IconTW.png

2629 ms

TWRicon.jpg

TWRicon.jpg

12316 ms

IconTWR.png

IconTWR.png

3151 ms

TWoicon.jpg

TWoicon.jpg

5678 ms

IconTWo.png

IconTWo.png

3672 ms

APP2.0_Amazon_ProductCloseUp_V1%20copy_JP.jpg

APP2.0_Amazon_ProductCloseUp_V1%20copy_JP.jpg

3899 ms

cover_pc.png

cover_pc.png

3961 ms

sns2.png

sns2.png

1004 ms

sns3.png

sns3.png

1027 ms

sns4.png

sns4.png

1006 ms

btn_shopall_off.png

btn_shopall_off.png

4012 ms

scope.png

scope.png

4070 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

75 ms

260e.svg

260e.svg

43 ms

remote.php

remote.php

5542 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

54 ms

www-player.css

www-player.css

12 ms

www-embed-player.js

www-embed-player.js

46 ms

base.js

base.js

79 ms

settings

settings

320 ms

ad_status.js

ad_status.js

190 ms

wQkdmVX08K_HD_9NHn0QjGfgu04J0GwVvAmYELAxlpM.js

wQkdmVX08K_HD_9NHn0QjGfgu04J0GwVvAmYELAxlpM.js

138 ms

embed.js

embed.js

50 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

17 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

52 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

27 ms

Create

Create

96 ms

id

id

13 ms

comply_jp

comply_jp

87 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

108 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

128 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

131 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

129 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

130 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

130 ms

_buildManifest.js

_buildManifest.js

163 ms

_ssgManifest.js

_ssgManifest.js

129 ms

GenerateIT

GenerateIT

49 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

11 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

12 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

4 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

9 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

8 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

22 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

8 ms

log_event

log_event

16 ms

Accessibility Review

comply.jp accessibility score

82

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

comply.jp best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

comply.jp 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

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

comply.jp

Open Graph data is detected on the main page of Comply. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: