Tools & Wizards About Us
xeneger.jp screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

xeneger.jp

革紐と蝋引き紐・ワックスコードや根付紐の激安問屋の紐屋。ボールチェーン、ネックレス部品やアクセサリー金具・ステンレスパーツや手芸紐やストラップパーツを安いつぶし玉の業務用割引値引価格で最安値激安卸販売 | 卸値通販 ゼネガー

Page Load Speed

6.3 sec in total

First Response

621 ms

Resources Loaded

5 sec

Page Rendered

697 ms

xeneger.jp screenshot

About Website

Welcome to xeneger.jp homepage info - get ready to check Xeneger best content for Japan right away, or after learning these important things about xeneger.jp

ワックスコード、蝋引き紐・ボールチェーンや革ひも、根付紐とブレスレットクラスプやネックレス部品販売の紐屋。ストラップパーツやヒートン、ビーズ金具ステンレスカニカンアクセサリーパーツを業務用割引値引き価格で革紐とワックスコードを最安値激安卸販売

Visit xeneger.jp

Key Findings

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

Performance Metrics

xeneger.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

xeneger.jp

621 ms

www.xeneger.jp

813 ms

all.css

370 ms

add.css

378 ms

css.js

423 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 85% of them (78 requests) were addressed to the original Xeneger.jp, 2% (2 requests) were made to S.yimg.jp and 2% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Xeneger.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.9 kB (21%)

Content Size

744.5 kB

After Optimization

589.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xeneger.jp main page is 744.5 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. 50% of websites need less resources to load. Images take 446.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 102.7 kB

  • Original 122.5 kB
  • After minification 90.5 kB
  • After compression 19.8 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 32.0 kB, which is 26% 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 102.7 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 10.6 kB

  • Original 446.0 kB
  • After minification 435.4 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. Xeneger images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 38.6 kB

  • Original 163.5 kB
  • After minification 163.1 kB
  • After compression 125.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 38.6 kB or 24% of the original size.

CSS Optimization

-25%

Potential reduce by 3.1 kB

  • Original 12.4 kB
  • After minification 12.4 kB
  • After compression 9.4 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. Xeneger.jp needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (22%)

Requests Now

90

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xeneger.jp

xeneger.jp

621 ms

www.xeneger.jp

www.xeneger.jp

813 ms

all.css

all.css

370 ms

add.css

add.css

378 ms

css.js

css.js

423 ms

navi.js

navi.js

404 ms

win_op.js

win_op.js

397 ms

site.js

site.js

417 ms

jquery.min.js

jquery.min.js

731 ms

ytag.js

ytag.js

883 ms

js

js

81 ms

conversion.js

conversion.js

19 ms

conversion.js

conversion.js

723 ms

analytics.js

analytics.js

97 ms

bg_header.png

bg_header.png

594 ms

logo.png

logo.png

592 ms

btn_entry.png

btn_entry.png

591 ms

btn_login.png

btn_login.png

589 ms

btn_history.png

btn_history.png

592 ms

btn_favorite.png

btn_favorite.png

591 ms

btn_cart.png

btn_cart.png

770 ms

header_banner2.png

header_banner2.png

966 ms

btn_itemsearch.png

btn_itemsearch.png

773 ms

navi01.jpg

navi01.jpg

790 ms

navi02.jpg

navi02.jpg

789 ms

navi03.jpg

navi03.jpg

786 ms

navi04.jpg

navi04.jpg

952 ms

navi05.jpg

navi05.jpg

960 ms

title_category.png

title_category.png

961 ms

61.png

61.png

1318 ms

1.png

1.png

1147 ms

79.png

79.png

1350 ms

78.png

78.png

1157 ms

2.png

2.png

1335 ms

3.png

3.png

1356 ms

68.png

68.png

1405 ms

81.png

81.png

1406 ms

75.png

75.png

1505 ms

74.png

74.png

1517 ms

4.png

4.png

1524 ms

5.png

5.png

1526 ms

6.png

6.png

1576 ms

title_guide.png

title_guide.png

967 ms

shadow.png

shadow.png

963 ms

title_calendar.png

title_calendar.png

1128 ms

title_cart.png

title_cart.png

1140 ms

btn_cart.png

btn_cart.png

1137 ms

title_news.png

title_news.png

1144 ms

btn_rss.jpg

btn_rss.jpg

1145 ms

title_recommend.png

title_recommend.png

1092 ms

conversion_async.js

conversion_async.js

474 ms

collect

collect

157 ms

collect

collect

203 ms

144 ms

conversion_async.js

conversion_async.js

1538 ms

02131056_5c637955d876d.jpg

02131056_5c637955d876d.jpg

732 ms

02181459_5c6a49d55b630.jpg

02181459_5c6a49d55b630.jpg

742 ms

02271645_5c76403530396.jpg

02271645_5c76403530396.jpg

928 ms

02201509_5c6cef37413b3.jpg

02201509_5c6cef37413b3.jpg

766 ms

02181237_5c6a2862463b2.jpg

02181237_5c6a2862463b2.jpg

751 ms

02191715_5c6bbb1adf48b.jpg

02191715_5c6bbb1adf48b.jpg

769 ms

64 ms

52 ms

23 ms

03041302_5c7ca349b6cba.jpg

03041302_5c7ca349b6cba.jpg

732 ms

05191115_591e555614e3b.jpg

05191115_591e555614e3b.jpg

745 ms

08291619_5b86491a4498b.jpg

08291619_5b86491a4498b.jpg

732 ms

02261137_5c74a66432deb.jpg

02261137_5c74a66432deb.jpg

741 ms

02271149_5c75fabf7c22a.jpg

02271149_5c75fabf7c22a.jpg

741 ms

11271155_5ddde5bd0210b.jpg

11271155_5ddde5bd0210b.jpg

727 ms

02221723_5c6fb17545957.jpg

02221723_5c6fb17545957.jpg

735 ms

07271158_62e0a9df00ba7.jpg

07271158_62e0a9df00ba7.jpg

734 ms

07271201_62e0aa7bdf62a.jpg

07271201_62e0aa7bdf62a.jpg

739 ms

09302353_5d921707931cb.jpg

09302353_5d921707931cb.jpg

744 ms

08071019_5b68f3ab30108.jpg

08071019_5b68f3ab30108.jpg

740 ms

07041534_595b36f59dfcd.jpg

07041534_595b36f59dfcd.jpg

725 ms

title_newitem.png

title_newitem.png

734 ms

10071047_615e51cf311b0.jpg

10071047_615e51cf311b0.jpg

735 ms

04221332_6080fc40849ed.jpg

04221332_6080fc40849ed.jpg

738 ms

04081523_606ea15e6782d.jpg

04081523_606ea15e6782d.jpg

745 ms

07201240_5f151230dff28.jpg

07201240_5f151230dff28.jpg

747 ms

07201237_5f151183556f1.jpg

07201237_5f151183556f1.jpg

881 ms

06171246_5ee9922e7d189.jpg

06171246_5ee9922e7d189.jpg

907 ms

pagetop.png

pagetop.png

753 ms

credit.jpg

credit.jpg

263 ms

arr_dot.png

arr_dot.png

744 ms

soldout.png

soldout.png

742 ms

arr_gray.png

arr_gray.png

746 ms

img_5off.png

img_5off.png

869 ms

img_10off.png

img_10off.png

897 ms

img_15off.png

img_15off.png

894 ms

761 ms

Accessibility Review

xeneger.jp accessibility score

78

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

xeneger.jp SEO score

84

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

xeneger.jp

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