Tools & Wizards About Us
4048.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

4048.jp

ラシンシア化粧品会員専用サイト シンシアリークラブ -ラシンシア・ATP・アクアゲル-

Page Load Speed

9.5 sec in total

First Response

800 ms

Resources Loaded

8.5 sec

Page Rendered

236 ms

4048.jp screenshot

About Website

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

ゲル化粧品のラシンシア会員専用サイト - ラシンシア・ATP・アクアゲルなど天然ゲル化粧品＆美容健康食品 -

Visit 4048.jp

Key Findings

We analyzed 4048.jp page load time and found that the first response time was 800 ms and then it took 8.7 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

4048.jp performance score

0

Network Requests Diagram

4048.jp

800 ms

top_re.css

350 ms

jquery-1.11.0.min.js

1842 ms

smartRollover.js

371 ms

jquery.bxslider.min.js

586 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 96% of them (72 requests) were addressed to the original 4048.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain 4048.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.9 kB (17%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 16.3 kB

  • Original 21.1 kB
  • After minification 16.3 kB
  • After compression 4.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 4.8 kB, which is 23% 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 16.3 kB or 77% of the original size.

Image Optimization

-11%

Potential reduce by 164.5 kB

  • Original 1.5 MB
  • After minification 1.3 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, 4048 needs image optimization as it can save up to 164.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 83.2 kB

  • Original 141.4 kB
  • After minification 140.8 kB
  • After compression 58.2 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 83.2 kB or 59% of the original size.

CSS Optimization

-79%

Potential reduce by 21.9 kB

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

Requests Breakdown

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

Requests Now

69

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

4048.jp

4048.jp

800 ms

top_re.css

top_re.css

350 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

1842 ms

smartRollover.js

smartRollover.js

371 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

586 ms

jquery.bxslider.css

jquery.bxslider.css

403 ms

lightbox.min.js

lightbox.min.js

580 ms

lightbox.css

lightbox.css

672 ms

scriptaculous.js

scriptaculous.js

739 ms

shared_class_re.css

shared_class_re.css

460 ms

default_re.css

default_re.css

552 ms

header_re.css

header_re.css

605 ms

footer_re.css

footer_re.css

695 ms

leftbox_re.css

leftbox_re.css

760 ms

top_news.html

top_news.html

194 ms

lightbox.css

lightbox.css

190 ms

loading.gif

loading.gif

320 ms

prev.png

prev.png

349 ms

next.png

next.png

369 ms

logo.gif

logo.gif

370 ms

season.gif

season.gif

527 ms

logo2.gif

logo2.gif

579 ms

arrow_brown.gif

arrow_brown.gif

690 ms

menu_sub.gif

menu_sub.gif

741 ms

menu_main.gif

menu_main.gif

923 ms

img_h2_login.jpg

img_h2_login.jpg

772 ms

img_bg_login.jpg

img_bg_login.jpg

1044 ms

img_btn_login.png

img_btn_login.png

968 ms

img_h2_this_month.jpg

img_h2_this_month.jpg

1058 ms

img_this_month.jpg

img_this_month.jpg

1478 ms

img_h2_new_info.png

img_h2_new_info.png

1142 ms

img_h2_link.png

img_h2_link.png

1313 ms

img_bg_link.jpg

img_bg_link.jpg

1286 ms

img_btn_ls_corp.jpg

img_btn_ls_corp.jpg

1384 ms

img_btn_ls_info.jpg

img_btn_ls_info.jpg

1459 ms

img_btn_beluce.jpg

img_btn_beluce.jpg

1487 ms

img_btn_fb.gif

img_btn_fb.gif

1632 ms

bn_medicated_atp.jpg

bn_medicated_atp.jpg

2265 ms

bn_maginne.jpg

bn_maginne.jpg

2302 ms

bn_ls.jpg

bn_ls.jpg

2288 ms

img_sc_point_02.png

img_sc_point_02.png

2563 ms

img_h2_skincare.png

img_h2_skincare.png

1866 ms

img_ls_skincare.png

img_ls_skincare.png

2551 ms

img_mnk_skincare.png

img_mnk_skincare.png

2788 ms

img_atp_skincare.png

img_atp_skincare.png

3183 ms

img_aq_skincare.png

img_aq_skincare.png

3152 ms

img_h2_pickup.png

img_h2_pickup.png

2640 ms

bn_mme_new.jpg

bn_mme_new.jpg

3586 ms

bn_mlife_new.jpg

bn_mlife_new.jpg

3721 ms

ga.js

ga.js

14 ms

bn_botanical_new.jpg

bn_botanical_new.jpg

3501 ms

__utm.gif

__utm.gif

12 ms

collect

collect

52 ms

top_news.css

top_news.css

2948 ms

img_h2_ranking.png

img_h2_ranking.png

3341 ms

img_rank_01.png

img_rank_01.png

3210 ms

img_rank_01_pro.jpg

img_rank_01_pro.jpg

3388 ms

img_rank_01_review_l.jpg

img_rank_01_review_l.jpg

5031 ms

img_rank_02.png

img_rank_02.png

3526 ms

img_rank_02_pro.jpg

img_rank_02_pro.jpg

3606 ms

img_rank_02_review_l.jpg

img_rank_02_review_l.jpg

4974 ms

img_rank_03.png

img_rank_03.png

3366 ms

img_rank_03_pro.jpg

img_rank_03_pro.jpg

4029 ms

img_rank_03_review_l.jpg

img_rank_03_review_l.jpg

4652 ms

arrow_brown.gif

arrow_brown.gif

3536 ms

tel.gif

tel.gif

3484 ms

fax.gif

fax.gif

3777 ms

pdf.gif

pdf.gif

3771 ms

net.gif

net.gif

4034 ms

acclog.cgi

acclog.cgi

3852 ms

bx_loader.gif

bx_loader.gif

3884 ms

controls.png

controls.png

4127 ms

close.png

close.png

4108 ms

default.css

default.css

2476 ms

arrow_pink_down.gif

arrow_pink_down.gif

371 ms

SEO Factors

4048.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

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

4048.jp

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