Tools & Wizards About Us

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

chapup.jp

【公式】チャップアップ-CHAP UP | 育毛の父が、あなたを救う！シリーズ累計1000万本突破！-[チャップアップ(CHAPUP)公式ショップ]

Page Load Speed

9 sec in total

First Response

547 ms

Resources Loaded

7.1 sec

Page Rendered

1.3 sec

About Website

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.jp

Key Findings

We 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.

Performance Metrics

chapup.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,350 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.353

31/100

15%

TTI (Time to Interactive)

Value32.4 s

0/100

10%

Network Requests Diagram

chapup.jp

547 ms

chapup.jp

1117 ms

ytag.js

880 ms

fbevents.js

22 ms

gtm.js

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 Optimization Overview & Recommendations

Page size can be reduced by 152.3 kB (47%)

Content Size

322.0 kB

After Optimization

169.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-79%

Potential reduce by 85.0 kB

  • Original 106.9 kB
  • After minification 91.9 kB
  • After compression 21.9 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.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 23.3 kB
  • After minification 23.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.

JavaScript Optimization

-37%

Potential reduce by 42.6 kB

  • Original 115.0 kB
  • After minification 113.7 kB
  • After compression 72.4 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.

CSS Optimization

-32%

Potential reduce by 24.7 kB

  • Original 76.8 kB
  • After minification 73.9 kB
  • After compression 52.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. 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.

Requests Breakdown

Number of requests can be reduced by 67 (50%)

Requests Now

134

After Optimization

67

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

chapup.jp accessibility score

73

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

chapup.jp best practices score

67

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

SEO Factors

chapup.jp SEO score

79

Search Engine Optimization Advices

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 doesn't use 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 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.

Social Sharing Optimization

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: