Tools & Wizards About Us
jwell.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

jwell.com

アクセサリー・ジュエリー通販のJWell(ジェイウェル)

Page Load Speed

5.5 sec in total

First Response

10 ms

Resources Loaded

4.1 sec

Page Rendered

1.4 sec

jwell.com screenshot

About Website

Welcome to jwell.com homepage info - get ready to check Jwell best content for Japan right away, or after learning these important things about jwell.com

日本最大級のアクセサリー通販サイト「JWell(ジェイウェル)」へ。カップル、恋人へのプレゼントに喜ばれる名入れアクセサリーも多数ご用意。最短翌日にお届けします。

Visit jwell.com

Key Findings

We analyzed Jwell.com page load time and found that the first response time was 10 ms and then it took 5.5 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

jwell.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value2,080 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.305

39/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

Network Requests Diagram

jwell.com

10 ms

jwell.com

348 ms

www.jwell.com

615 ms

colorbox.css

342 ms

all.css

29 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 49% of them (38 requests) were addressed to the original Jwell.com, 8% (6 requests) were made to Googletagmanager.com and 5% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source B97.yahoo.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 546.5 kB (63%)

Content Size

873.0 kB

After Optimization

326.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jwell.com main page is 873.0 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. 65% of websites need less resources to load. HTML takes 428.4 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 380.6 kB

  • Original 428.4 kB
  • After minification 349.7 kB
  • After compression 47.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 78.7 kB, which is 18% 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 380.6 kB or 89% of the original size.

Image Optimization

-7%

Potential reduce by 5.8 kB

  • Original 80.2 kB
  • After minification 74.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. Jwell images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 149.3 kB

  • Original 294.4 kB
  • After minification 294.3 kB
  • After compression 145.1 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 149.3 kB or 51% of the original size.

CSS Optimization

-16%

Potential reduce by 10.9 kB

  • Original 70.0 kB
  • After minification 70.0 kB
  • After compression 59.1 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. Jwell.com needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 16% of the original size.

Requests Breakdown

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

Requests Now

71

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jwell.com

jwell.com

10 ms

jwell.com

jwell.com

348 ms

www.jwell.com

www.jwell.com

615 ms

colorbox.css

colorbox.css

342 ms

all.css

all.css

29 ms

style.min.css

style.min.css

509 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

519 ms

eccube.js

eccube.js

340 ms

eccube.legacy.js

eccube.legacy.js

342 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

661 ms

lazyload.min.js

lazyload.min.js

673 ms

common.css

common.css

845 ms

pp_add.css

pp_add.css

673 ms

slick.min.js

slick.min.js

1145 ms

common.js

common.js

1148 ms

L1owIjT9DPtf30471FS.js

L1owIjT9DPtf30471FS.js

795 ms

gtm.js

gtm.js

133 ms

logo.svg

logo.svg

106 ms

dummy_884x220.gif

dummy_884x220.gif

107 ms

dummy_912x520.gif

dummy_912x520.gif

105 ms

dummy_600x600.gif

dummy_600x600.gif

105 ms

dummy_640x460.gif

dummy_640x460.gif

107 ms

feature_jewelry.jpg

feature_jewelry.jpg

108 ms

feature_thekiss.jpg

feature_thekiss.jpg

109 ms

feature_pair-neck.jpg

feature_pair-neck.jpg

108 ms

feature_pair-ring.jpg

feature_pair-ring.jpg

108 ms

feature_pair-bracelet.jpg

feature_pair-bracelet.jpg

109 ms

feature_ladys-neck.jpg

feature_ladys-neck.jpg

110 ms

dummy_750x278.gif

dummy_750x278.gif

110 ms

dummy_912x390.gif

dummy_912x390.gif

112 ms

dummy_360x300.gif

dummy_360x300.gif

111 ms

dummy_300x109.gif

dummy_300x109.gif

111 ms

dummy_245x170.gif

dummy_245x170.gif

111 ms

dummy_130x47.gif

dummy_130x47.gif

112 ms

tiktok.jpg

tiktok.jpg

113 ms

icon_ladys.png

icon_ladys.png

81 ms

icon_pair.png

icon_pair.png

82 ms

icon_mens.png

icon_mens.png

81 ms

osusume.jpg

osusume.jpg

113 ms

fa-solid-900.woff

fa-solid-900.woff

136 ms

fa-regular-400.woff

fa-regular-400.woff

137 ms

fa-brands-400.woff

fa-brands-400.woff

75 ms

js

js

132 ms

destination

destination

256 ms

3083db64-a08d-44c0-a844-8900fbcdb735.js

3083db64-a08d-44c0-a844-8900fbcdb735.js

255 ms

ytag.js

ytag.js

736 ms

get_login_item.php

get_login_item.php

257 ms

a8sales.js

a8sales.js

20 ms

itm.js

itm.js

139 ms

fbevents.js

fbevents.js

13 ms

js

js

39 ms

analytics.js

analytics.js

36 ms

ld.js

ld.js

22 ms

lt.js

lt.js

32 ms

4dtvf8s7bj

4dtvf8s7bj

60 ms

syncframe

syncframe

26 ms

collect

collect

14 ms

mIYegY

mIYegY

211 ms

segment

segment

362 ms

err.gif

err.gif

711 ms

collect

collect

11 ms

ga-audiences

ga-audiences

83 ms

clarity.js

clarity.js

13 ms

icon_login.svg

icon_login.svg

3 ms

conversion.js

conversion.js

173 ms

gtm.js

gtm.js

28 ms

gtm.js

gtm.js

82 ms

conversion_async.js

conversion_async.js

1332 ms

s_retargeting.js

s_retargeting.js

704 ms

im-uid.js

im-uid.js

3 ms

get

get

305 ms

259 ms

beacon.gif

beacon.gif

195 ms

38 ms

log.js

log.js

11 ms

fraud

fraud

280 ms

tracker

tracker

259 ms

collect

collect

147 ms

Accessibility Review

jwell.com accessibility score

85

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

Image elements do not have [alt] attributes

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.

Best Practices

jwell.com 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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jwell.com SEO score

85

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

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 Jwell.com 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 Jwell.com 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

jwell.com

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