9 sec in total
547 ms
7.1 sec
1.3 sec
Click here to check amazing CHAP UP content for Japan. Otherwise, check out these important facts you probably never knew about chapup.jp
ウルトラの父でおなじみ、数々のランキング1位を獲得したWeb売上No.1の育毛ローション。シャンプー、サプリメント、ビオルチアでも人気の全額返金保証書付き定期便をご用意しています。
Visit chapup.jpWe analyzed Chapup.jp page load time and found that the first response time was 547 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
chapup.jp performance score
name
value
score
weighting
Value11.0 s
0/100
10%
Value16.2 s
0/100
25%
Value18.0 s
0/100
10%
Value2,350 ms
5/100
30%
Value0.353
31/100
15%
Value32.4 s
0/100
10%
547 ms
1117 ms
880 ms
22 ms
58 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 95% of them (129 requests) were addressed to the original Chapup.jp, 2% (3 requests) were made to Googletagmanager.com and 1% (1 request) were made to S.yimg.jp. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Chapup.jp.
Page size can be reduced by 152.3 kB (47%)
322.0 kB
169.7 kB
In fact, the total size of Chapup.jp main page is 322.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. Javascripts take 115.0 kB which makes up the majority of the site volume.
Potential reduce by 85.0 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 15.1 kB, which is 14% 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 85.0 kB or 79% of the original size.
Potential reduce by 1 B
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. CHAP UP images are well optimized though.
Potential reduce by 42.6 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 42.6 kB or 37% of the original size.
Potential reduce by 24.7 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. Chapup.jp needs all CSS files to be minified and compressed as it can save up to 24.7 kB or 32% of the original size.
Number of requests can be reduced by 67 (50%)
134
67
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CHAP UP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
chapup.jp
547 ms
chapup.jp
1117 ms
ytag.js
880 ms
fbevents.js
22 ms
gtm.js
58 ms
gtm.js
121 ms
index.js
1533 ms
common.css
374 ms
remodal.css
551 ms
remodal-default-theme.css
554 ms
jquery.lightbox-0.5.css
552 ms
amazon_pay.css
552 ms
main.js
562 ms
pk.css
734 ms
legacy.css
735 ms
clone.js
735 ms
css.js
735 ms
navi.js
750 ms
win_op.js
754 ms
site.js
917 ms
jquery.js
1105 ms
amazon_pay_v2.js
918 ms
jquery.lightbox-0.5.min.js
918 ms
jquery.mouse.wheel.min.js
939 ms
tilescroller.js
943 ms
bestproducts.js.php
1102 ms
remodal.js
1103 ms
store-cv.js
252 ms
pc_style.css
1105 ms
pc_add.css
1127 ms
jquery.matchHeight.js
1132 ms
slick.css
1285 ms
slick.min.js
1289 ms
import.css
193 ms
block.css
202 ms
btn.css
200 ms
footer.css
188 ms
frame.css
187 ms
guide.css
185 ms
header.css
197 ms
index.css
369 ms
main.css
374 ms
news.css
369 ms
products.css
381 ms
shopping.css
387 ms
sub_function.css
386 ms
recommend.css
552 ms
ranking.css
553 ms
window.css
557 ms
chapup.css
576 ms
light_user.css
575 ms
new_mypage.css
740 ms
design_key_w100.css
737 ms
gtm.js
65 ms
logo_chapup.webp
195 ms
pc_img_00_01_lo04.webp
748 ms
pc_img_00_02.webp
193 ms
pc_ttl_01_00.webp
193 ms
pc_slide_01.webp
365 ms
pc_slide_02.webp
193 ms
pc_slide_06.webp
369 ms
pc_slide_07.webp
369 ms
pc_img_02_00_txtseo_lo04.webp
912 ms
pc_img_02_05_lo04.webp
937 ms
pc_ttl_02_01_txtseo.webp
549 ms
pc_img_02_01_lo03.webp
553 ms
pc_ttl_02_02_txtseo.webp
553 ms
pc_img_02_02_lo03.webp
913 ms
pc_ttl_02_03_txtseo.webp
737 ms
pc_img_02_03_lo03_v2.webp
738 ms
pc_ttl_02_04_txtseo.webp
922 ms
pc_img_02_04_lo03.webp
921 ms
pc_img_02t_00_txtseo_v2.webp
1308 ms
pc_ttl_02t_01_txtseo.webp
1096 ms
pc_img_02t_01.webp
1097 ms
pc_ttl_02t_02_txtseo.webp
1105 ms
pc_img_02t_02.webp
1105 ms
pc_ttl_03_00.webp
1125 ms
pc_img_03_01_lo04.webp
1281 ms
pc_ttl_03_01_txtseo.webp
1280 ms
pc_img_03_02_ms02.webp
1287 ms
pc_ttl_03_02_txtseo.webp
1289 ms
pc_img_03_03.webp
1314 ms
pc_ttl_03_03_txtseo.webp
1463 ms
pc_img_03_07.webp
1465 ms
pc_ttl_03_04_txtseo.webp
1470 ms
pc_img_03_06.webp
1471 ms
pc_ttl_03_05_txtseo.webp
1496 ms
pc_img_03_04.webp
1503 ms
pc_ttl_03_06_txtseo.webp
1636 ms
pc_img_03_05.webp
1460 ms
pc_ttl_03_07_txtseo.webp
1465 ms
pc_img_03_08.webp
1465 ms
pc_ttl_03_08_txtseo.webp
1422 ms
pc_ttl_06_00.webp
1331 ms
pc_img_06_08_txtseo.webp
1467 ms
pc_img_06_03_txtseo_v2.webp
1469 ms
pc_img_06_05_txtseo_v2.webp
1473 ms
pc_img_06_07_txtseo.webp
1469 ms
pc_ttl_07_00.webp
1324 ms
pc_ttl_07_01.webp
1147 ms
pc_img_07_01.webp
1283 ms
pc_img_07_02.webp
1276 ms
pc_ttl_07_02.webp
1157 ms
pc_ttl_07_03_19tax.webp
1161 ms
pc_ttl_07_04_19tax.webp
1282 ms
pc_ttl_08_00.webp
1283 ms
pc_img_08_01.webp
1271 ms
pc_img_08_02.webp
1110 ms
pc_img_08_05.webp
1160 ms
pc_img_08_06.webp
1160 ms
pc_img_08_07.webp
1282 ms
pc_img_08_04.webp
1265 ms
pc_ttl_news_00.webp
1109 ms
pc_ttl_09_00.webp
1109 ms
pc_bg_09_00_txtseo.webp
1159 ms
pc_chapup_excellent_lo04.webp
1162 ms
about_credit.jpg
1263 ms
wiz_newbanner405x66.png
1260 ms
about_time02.png
1111 ms
seal_rapid.gif
1109 ms
pc_img_ft_sns_cu_lab.webp
1164 ms
pc_img_ft_sns_cu_lab_ov.webp
1168 ms
pc_img_ft_sns_ttl_cu.webp
1258 ms
pc_img_ft_sns_ico_ig.webp
1255 ms
pc_img_ft_sns_ico_ig_ov.webp
1111 ms
pc_img_ft_sns_ico_tw.webp
1109 ms
pc_img_ft_sns_ico_tw_ov.webp
1170 ms
pc_img_ft_sns_ttl_bl.png
1173 ms
logo_footer.webp
1251 ms
jadma_footer.webp
1250 ms
ico_fd.png
1110 ms
ico_dvr.png
1108 ms
pc_ico_09_01.png
1139 ms
pc_ico_09_02.png
1137 ms
pc_slide_02.webp
1105 ms
chapup.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
chapup.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
chapup.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chapup.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 Chapup.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.
chapup.jp
Open Graph data is detected on the main page of CHAP UP. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: