Access henecia.jp. キム・ヒョンジュン日本公式ファンクラブ HENECIA JAPAN

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value24.5 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.468

19/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

henecia.jp

367 ms

henecia.jp

711 ms

reset.css

170 ms

common202206.css

341 ms

slick.css

439 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 45% of them (23 requests) were addressed to the original Henecia.jp, 24% (12 requests) were made to Fonts.gstatic.com and 10% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Henecia.jp.

Content Size

3.4 MB

After Optimization

3.2 MB

In fact, the total size of Henecia.jp main page is 3.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 9.7 kB

Original 12.6 kB
After minification 10.2 kB
After compression 2.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 2.3 kB, which is 19% 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 9.7 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 14.8 kB

Original 2.9 MB
After minification 2.9 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. HENECIA images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 227.3 kB

Original 432.5 kB
After minification 432.5 kB
After compression 205.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 227.3 kB or 53% of the original size.

CSS Optimization

-8%

Potential reduce by 5.6 kB

Original 73.0 kB
After minification 73.0 kB
After compression 67.3 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. Henecia.jp has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

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.

High

<frame> or <iframe> elements do not have a title

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

robots.txt is not valid

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

henecia.jp

Open Graph data is detected on the main page of HENECIA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

キム・ヒョンジュン日本公式ファンクラブ HENECIA JAPAN

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

henecia.jp

henecia.jp

reset.css

common202206.css

slick.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

henecia.jp

henecia.jp

reset.css

common202206.css

slick.css

slick-theme.css

jquery.min.js

common.js

slick.min.js

top.js

css

notosansjp.css

css2

js

qCyAN-0sZbg

1052.jpg

btn_text_login.png

btn_text_join.png

icon-login-sm.png

icon-join-sm.png

mainimg-pc-202206.jpg

mainimg-tb-202206.jpg

mainimg-sm-202206.jpg

h2_news.png

h2_movie.png

sns_icon.png

ajax-loader.gif

1051.jpg

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1Z47sMC3Yw.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1Z47sMC3Yw.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j35zS1Z47sMC3Yw.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj35zS1Z47sMC3Yw.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi35zS1Z47sMC3Yw.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k35zS1Z47sMC3Yw.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1Z47sMC3Yw.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk35zS1Z47sMC3Yw.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk35zS1Z47sMC3Yw.woff

bx6ANxqUneKx06UkIXISr3FyDW2J.woff

riesling-webfont.woff

www-player.css

www-embed-player.js

base.js

ad_status.js