Tools & Wizards About Us
wellsjapan.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wellsjapan.co.jp

トップページ

Page Load Speed

7.9 sec in total

First Response

704 ms

Resources Loaded

6.9 sec

Page Rendered

200 ms

wellsjapan.co.jp screenshot

About Website

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

ナウでヤングなレンタルサーバーです。初心者にやさしくて、人気のブログも超カンタンに設置できます。おこづかいでＯＫの格安料金 なんと月額100円（税込105円）から！可愛いアドレスもたくさんで女性に大人気！充実のサポート体制で安心です。

Visit wellsjapan.co.jp

Key Findings

We analyzed Wellsjapan.co.jp page load time and found that the first response time was 704 ms and then it took 7.1 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

wellsjapan.co.jp performance score

0

Network Requests Diagram

wellsjapan.co.jp

704 ms

www.wellsjapan.co.jp

1141 ms

import.css

344 ms

dw_common.js

347 ms

JUDGE.JS

359 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 94% of them (66 requests) were addressed to the original Wellsjapan.co.jp, 4% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Srv2.wa.marketingsolutions.yahoo.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Wellsjapan.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.9 kB (9%)

Content Size

609.6 kB

After Optimization

552.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wellsjapan.co.jp main page is 609.6 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. Images take 537.9 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 17.1 kB

  • Original 23.4 kB
  • After minification 22.8 kB
  • After compression 6.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.1 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 16.1 kB

  • Original 537.9 kB
  • After minification 521.7 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. Wellsjapan images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 4.5 kB

  • Original 24.0 kB
  • After minification 22.6 kB
  • After compression 19.5 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 4.5 kB or 19% of the original size.

CSS Optimization

-79%

Potential reduce by 19.2 kB

  • Original 24.3 kB
  • After minification 18.7 kB
  • After compression 5.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. Wellsjapan.co.jp needs all CSS files to be minified and compressed as it can save up to 19.2 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

53

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wellsjapan.co.jp

wellsjapan.co.jp

704 ms

www.wellsjapan.co.jp

www.wellsjapan.co.jp

1141 ms

import.css

import.css

344 ms

dw_common.js

dw_common.js

347 ms

JUDGE.JS

JUDGE.JS

359 ms

ie7_flash.js

ie7_flash.js

363 ms

smartRollover.js

smartRollover.js

387 ms

content.css

content.css

318 ms

base.css

base.css

327 ms

top.css

top.css

346 ms

form.css

form.css

364 ms

shop.css

shop.css

374 ms

ga.js

ga.js

18 ms

ScriptServlet

ScriptServlet

42 ms

__utm.gif

__utm.gif

49 ms

bg_body.gif

bg_body.gif

177 ms

__utm.gif

__utm.gif

42 ms

logo.gif

logo.gif

317 ms

hAdd.gif

hAdd.gif

337 ms

hNav_02_off.gif

hNav_02_off.gif

343 ms

hNav_03_off.gif

hNav_03_off.gif

347 ms

hNav_04_off.gif

hNav_04_off.gif

364 ms

hNav_05_off.gif

hNav_05_off.gif

558 ms

gNav_01_off.gif

gNav_01_off.gif

629 ms

gNav_02_off.gif

gNav_02_off.gif

634 ms

gNav_03_off.gif

gNav_03_off.gif

631 ms

gNav_04_off.gif

gNav_04_off.gif

708 ms

gNav_05.gif

gNav_05.gif

734 ms

gNav_06.gif

gNav_06.gif

919 ms

gNav_07_off.gif

gNav_07_off.gif

920 ms

gNav_08_off.gif

gNav_08_off.gif

970 ms

category.gif

category.gif

1006 ms

categoryTitle_01.gif

categoryTitle_01.gif

1043 ms

br_cata.JPG

br_cata.JPG

1090 ms

ippa_cata.JPG

ippa_cata.JPG

1222 ms

eco_cata.JPG

eco_cata.JPG

1283 ms

kurisutaru.JPG

kurisutaru.JPG

1257 ms

soriddo.JPG

soriddo.JPG

1318 ms

kagami.JPG

kagami.JPG

1394 ms

etc.JPG

etc.JPG

1429 ms

outlet.JPG

outlet.JPG

1538 ms

sNav_blog_off.jpg

sNav_blog_off.jpg

1567 ms

bnr_left.gif

bnr_left.gif

1633 ms

sAdd.gif

sAdd.gif

1658 ms

bnr_flow_off.jpg

bnr_flow_off.jpg

2200 ms

bnr_06.jpg

bnr_06.jpg

2223 ms

bnr_07.jpg

bnr_07.jpg

2158 ms

title_nProgram.gif

title_nProgram.gif

1926 ms

bnr_new1_off.gif

bnr_new1_off.gif

1974 ms

bnr_new2_off.gif

bnr_new2_off.gif

1995 ms

bnr_01.jpg

bnr_01.jpg

2440 ms

bnr_02_off.jpg

bnr_02_off.jpg

2483 ms

bnr_03_off.jpg

bnr_03_off.jpg

2355 ms

bnr_04_off.jpg

bnr_04_off.jpg

2353 ms

title_ranking.gif

title_ranking.gif

2166 ms

1297765332-269996_s.jpg

1297765332-269996_s.jpg

2276 ms

ranking_01.gif

ranking_01.gif

2453 ms

1297769205-654600_s.jpg

1297769205-654600_s.jpg

2486 ms

ranking_02.gif

ranking_02.gif

2308 ms

1338344524-452050_s.jpg

1338344524-452050_s.jpg

2245 ms

ranking_03.gif

ranking_03.gif

2333 ms

1282788271-898738_s.jpg

1282788271-898738_s.jpg

2408 ms

ranking_04.gif

ranking_04.gif

2461 ms

1340947085-125898_s.jpg

1340947085-125898_s.jpg

2441 ms

ranking_05.gif

ranking_05.gif

2251 ms

company_gift.jpg

company_gift.jpg

2908 ms

flashPlayer.gif

flashPlayer.gif

2305 ms

icon_fNav.gif

icon_fNav.gif

2374 ms

bg_footer.gif

bg_footer.gif

2421 ms

bnr_01_r.jpg

bnr_01_r.jpg

497 ms

SEO Factors

wellsjapan.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wellsjapan.co.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 Wellsjapan.co.jp main page’s claimed encoding is euc-jp. 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

wellsjapan.co.jp

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