7.4 sec in total
559 ms
6.1 sec
731 ms
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 559 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
chapup.jp performance score
name
value
score
weighting
Value10.9 s
0/100
10%
Value16.4 s
0/100
25%
Value16.6 s
0/100
10%
Value3,530 ms
1/100
30%
Value0.003
100/100
15%
Value55.3 s
0/100
10%
559 ms
158 ms
314 ms
316 ms
329 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 51% of them (78 requests) were addressed to the original Chapup.jp, 3% (4 requests) were made to Cs.adingo.jp and 3% (4 requests) were made to Vizury.com. 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 640.9 kB (33%)
2.0 MB
1.3 MB
In fact, the total size of Chapup.jp main page is 2.0 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 27.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. 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 27.0 kB or 74% of the original size.
Potential reduce by 71.3 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. CHAP UP images are well optimized though.
Potential reduce by 352.8 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 352.8 kB or 64% of the original size.
Potential reduce by 189.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. Chapup.jp needs all CSS files to be minified and compressed as it can save up to 189.8 kB or 88% of the original size.
Number of requests can be reduced by 98 (69%)
143
45
The browser has sent 143 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 39 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
chapup.jp
559 ms
common.css
158 ms
jquery.lightbox-0.5.css
314 ms
main.js
316 ms
pk.css
329 ms
clone.js
330 ms
css.js
330 ms
navi.js
467 ms
win_op.js
467 ms
site.js
468 ms
jquery.js
984 ms
jquery.lightbox-0.5.min.js
490 ms
jquery.mouse.wheel.min.js
491 ms
tilescroller.js
619 ms
bestproducts.js.php
621 ms
7b68e663e5684a.js
458 ms
webantenna.js
890 ms
jquery.pageslide.min.js
616 ms
import.css
505 ms
block.css
158 ms
btn.css
312 ms
footer.css
167 ms
frame.css
170 ms
guide.css
161 ms
header.css
316 ms
index.css
316 ms
main.css
821 ms
mypage.css
331 ms
news.css
466 ms
products.css
621 ms
shopping.css
468 ms
sub_function.css
487 ms
recommend.css
493 ms
ranking.css
622 ms
window.css
622 ms
media-queries.css
651 ms
chapup.css
658 ms
light_user.css
774 ms
design_controller.js.php
162 ms
rogo.png
187 ms
tel.png
157 ms
main_top2_1.jpg
495 ms
otoko_top.png
331 ms
about_chap675_1.jpg
311 ms
tassei.jpg
613 ms
top_san.gif
623 ms
shanpu.jpg
493 ms
fukusayou.jpg
622 ms
seibun_1.jpg
494 ms
hosyou_1.jpg
659 ms
teiki_1.jpg
658 ms
usuge_1.jpg
660 ms
taiken_1.jpg
769 ms
q&a_1.jpg
778 ms
syo.gif
778 ms
buy670_1.jpg
1150 ms
buy670_2.jpg
985 ms
buy670_3.jpg
1154 ms
haisou_670.png
1235 ms
buy670_4_2.jpg
933 ms
buy670_4_1.jpg
1088 ms
sinki.gif
1089 ms
mypage.gif
1150 ms
side_q&a.gif
1244 ms
tel_side.jpg
1245 ms
side_faq.gif
1315 ms
side_usuge.gif
1316 ms
zassi.gif
1318 ms
about_credit.jpg
1390 ms
about_time.jpg
1399 ms
footer_rogo.png
1553 ms
page-top.png
1478 ms
gtm.js
104 ms
tag.js
48 ms
_webantenna.png
477 ms
tag
31 ms
main_back.png
1375 ms
top_main_btn.png
1541 ms
oct.js
62 ms
conversion_async.js
58 ms
dc.js
59 ms
analytics.js
32 ms
h2_back2.gif
1403 ms
h2_title.png
1402 ms
collect
39 ms
collect
57 ms
icon_news_s.png
1460 ms
50 ms
adsct
90 ms
adsct
63 ms
s_retargeting.js
575 ms
__utm.gif
19 ms
43 ms
35 ms
buy670_btn.jpg
1338 ms
buy670_btn.jpg
1377 ms
footer_back.png
1220 ms
pixel.js
330 ms
pixel
150 ms
pixel
37 ms
Pug
17 ms
sync.ad-stir.com
300 ms
sync
9 ms
sync
465 ms
is
410 ms
blade_track_jp.js
326 ms
nexRt.js
25 ms
sd
5 ms
294 ms
rt
300 ms
pixel.php
86 ms
cookie_enabled_get.html
341 ms
adfunnel
151 ms
xrost
151 ms
beacon.gif
162 ms
analyze.php
327 ms
bl_track.cgi
359 ms
bl_track.cgi
384 ms
pixel
39 ms
cs
349 ms
302 ms
Pug
28 ms
rum
14 ms
pixel.gif
183 ms
sync
15 ms
Pug
31 ms
309 ms
320 ms
322 ms
rum
20 ms
tap.php
18 ms
cmr.php
76 ms
cmrapp.php
73 ms
178 ms
cmradf.php
38 ms
cmrxrost.php
74 ms
ld.js
25 ms
ya.js
348 ms
conversion_async.js
65 ms
adv.js
43 ms
event
20 ms
event
351 ms
dg_gateway.js
35 ms
15 ms
conversion.js
979 ms
20 ms
adv_inner.js
17 ms
adv.aspx
520 ms
pb.js
526 ms
337 ms
344 ms
dis.aspx
360 ms
dgcore.js
17 ms
adSiteVisit.js
384 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
<frame> or <iframe> elements do not have a title
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>).
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 description is not detected on the main page of CHAP UP. 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: