Tools & Wizards About Us
666-666.jp screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

666-666.jp

【公式】日本直販｜テレビショッピング・ラジオショッピング通販

Page Load Speed

10.9 sec in total

First Response

531 ms

Resources Loaded

9.5 sec

Page Rendered

855 ms

666-666.jp screenshot

About Website

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

★プレミアム会員募集中★日本直販の公式ネット通販ではメルマガ登録するだけでいつでもお得5％OFF。「日本直販といえばカニ」だけでなく、補聴器、電動爪削り、マッサージチェアなどシニアに人気の商品や、家電、家具、雑貨、コスメ、サプリメントなどテレビショッピングやラジオで話題の商品が豊富に揃います。商品選びにはランキングやおすすめ特集、SALE情報が便利。CM動画でオリジナル商品をチェック出来るのも◎。

Visit 666-666.jp

Key Findings

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

Performance Metrics

666-666.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value19.7 s

0/100

25%

SI (Speed Index)

Value24.5 s

0/100

10%

TBT (Total Blocking Time)

Value4,970 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.353

31/100

15%

TTI (Time to Interactive)

Value31.8 s

0/100

10%

Network Requests Diagram

666-666.jp

531 ms

www.666-666.jp

1314 ms

bootstrap.css

1088 ms

font-awesome.css

775 ms

jquery-ui.min.css

836 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 81% of them (87 requests) were addressed to the original 666-666.jp, 6% (6 requests) were made to Log1.mobylog.jp and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain 666-666.jp.

Page Optimization Overview & Recommendations

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

Content Size

5.1 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 666-666.jp main page is 5.1 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. 35% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 58.5 kB

  • Original 68.0 kB
  • After minification 52.0 kB
  • After compression 9.5 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 16.0 kB, which is 24% 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 58.5 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 332.1 kB

  • Original 3.9 MB
  • After minification 3.5 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. 666 images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 636.3 kB

  • Original 872.7 kB
  • After minification 674.7 kB
  • After compression 236.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 636.3 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 273.5 kB

  • Original 319.3 kB
  • After minification 240.0 kB
  • After compression 45.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. 666-666.jp needs all CSS files to be minified and compressed as it can save up to 273.5 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

104

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

666-666.jp

666-666.jp

531 ms

www.666-666.jp

www.666-666.jp

1314 ms

bootstrap.css

bootstrap.css

1088 ms

font-awesome.css

font-awesome.css

775 ms

jquery-ui.min.css

jquery-ui.min.css

836 ms

import.css

import.css

339 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

1165 ms

jquery-ui.min.js

jquery-ui.min.js

1665 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

813 ms

jquery.ba-throttle-debounce.min.js

jquery.ba-throttle-debounce.min.js

931 ms

velocity.js

velocity.js

1474 ms

jquery.waypoints.js

jquery.waypoints.js

1009 ms

infinite.js

infinite.js

1091 ms

inview.js

inview.js

1179 ms

sticky.js

sticky.js

1242 ms

bootstrap.min.js

bootstrap.min.js

1402 ms

win_op.js

win_op.js

1331 ms

site.js

site.js

1347 ms

_common.js

_common.js

1402 ms

_base.js

_base.js

1506 ms

_nccom.js

_nccom.js

1518 ms

jquery.address-search.js

jquery.address-search.js

1560 ms

_base.css

_base.css

1990 ms

_top.css

_top.css

1304 ms

_button.css

_button.css

1343 ms

_guide.css

_guide.css

1353 ms

common.css

common.css

1385 ms

bloc.css

bloc.css

1471 ms

my.css

my.css

1497 ms

detail.css

detail.css

1516 ms

contact.css

contact.css

1523 ms

_top.js

_top.js

1401 ms

500228.js

500228.js

508 ms

gtm.js

gtm.js

68 ms

scrolltop.png

scrolltop.png

183 ms

logo_chokuhan.png

logo_chokuhan.png

186 ms

navi_gnavi.png

navi_gnavi.png

188 ms

navi_category.png

navi_category.png

341 ms

bnr_slide_riha.jpg

bnr_slide_riha.jpg

2544 ms

bnr_slide_5off.jpg

bnr_slide_5off.jpg

675 ms

bnr_slide_lum.jpg

bnr_slide_lum.jpg

941 ms

bnr_slide_tokutoku.jpg

bnr_slide_tokutoku.jpg

1397 ms

bnr_slide_kome.jpg

bnr_slide_kome.jpg

2019 ms

slider_prev.png

slider_prev.png

507 ms

slider_next.png

slider_next.png

678 ms

bnr60_imp.png

bnr60_imp.png

1007 ms

bnr60_catalog.jpg

bnr60_catalog.jpg

854 ms

bnr60_5off.jpg

bnr60_5off.jpg

1027 ms

bnr60_hoken.jpg

bnr60_hoken.jpg

1112 ms

resize_image.php

resize_image.php

2182 ms

resize_image.php

resize_image.php

1709 ms

resize_image.php

resize_image.php

2575 ms

resize_image.php

resize_image.php

1983 ms

resize_image.php

resize_image.php

3536 ms

resize_image.php

resize_image.php

2430 ms

resize_image.php

resize_image.php

2462 ms

resize_image.php

resize_image.php

2826 ms

resize_image.php

resize_image.php

3030 ms

resize_image.php

resize_image.php

2774 ms

resize_image.php

resize_image.php

3012 ms

resize_image.php

resize_image.php

3191 ms

resize_image.php

resize_image.php

3539 ms

resize_image.php

resize_image.php

3464 ms

bnr_slide_yoizu.jpg

bnr_slide_yoizu.jpg

4175 ms

bnr_slide_hakusan.jpg

bnr_slide_hakusan.jpg

4578 ms

08201118_55d53906ef087.jpg

08201118_55d53906ef087.jpg

3528 ms

06301714_559250030b06d.jpg

06301714_559250030b06d.jpg

3642 ms

11241650_565416ba736f8.jpg

11241650_565416ba736f8.jpg

3864 ms

07091644_559e2642423e0.jpg

07091644_559e2642423e0.jpg

4371 ms

02100916_56ba814ddcb4f.jpg

02100916_56ba814ddcb4f.jpg

3853 ms

ga.js

ga.js

79 ms

analytics.js

analytics.js

64 ms

_tag_mobylog.js

_tag_mobylog.js

347 ms

xd_plugin.js

xd_plugin.js

389 ms

pta.js

pta.js

502 ms

tag.js

tag.js

37 ms

__utm.gif

__utm.gif

36 ms

collect

collect

64 ms

tag

tag

17 ms

collect

collect

55 ms

collect

collect

17 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3807 ms

info_tel.png

info_tel.png

3857 ms

bnr50_net.png

bnr50_net.png

3856 ms

bnr50_affi.jpg

bnr50_affi.jpg

3828 ms

xd_deduplicate.js

xd_deduplicate.js

196 ms

bnr50_imp.png

bnr50_imp.png

3679 ms

7049331a.js

7049331a.js

481 ms

msb.php

msb.php

196 ms

bnr50_omimai.png

bnr50_omimai.png

3536 ms

bnr50_ssl.png

bnr50_ssl.png

3654 ms

jadma.gif

jadma.gif

3501 ms

dot.php

dot.php

182 ms

privacy01.png

privacy01.png

3408 ms

logo_tci.png

logo_tci.png

3372 ms

product_lg.png

product_lg.png

3475 ms

product_md.png

product_md.png

3395 ms

product_xl.png

product_xl.png

3128 ms

rank1.png

rank1.png

2839 ms

rank2.png

rank2.png

2567 ms

rank3.png

rank3.png

2658 ms

rank4.png

rank4.png

2485 ms

rank5.png

rank5.png

2263 ms

ui-bg_highlight-soft_100_eeeeee_1x100.png

ui-bg_highlight-soft_100_eeeeee_1x100.png

2253 ms

xsync

xsync

783 ms

conversion_async.js

conversion_async.js

34 ms

42 ms

48 ms

Accessibility Review

666-666.jp accessibility score

63

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

Buttons do not have an accessible name

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

Best Practices

666-666.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

666-666.jp SEO score

90

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

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

666-666.jp

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