7 sec in total
753 ms
6 sec
180 ms
Visit henecia.jp now to see the best up-to-date HENECIA content for Russia and also check out these interesting facts you probably never knew about henecia.jp
キム・ヒョンジュン日本公式ファンクラブ HENECIA JAPAN
Visit henecia.jpWe analyzed Henecia.jp page load time and found that the first response time was 753 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
henecia.jp performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value21.3 s
0/100
25%
Value7.5 s
27/100
10%
Value1,110 ms
23/100
30%
Value0.466
19/100
15%
Value15.4 s
7/100
10%
753 ms
1476 ms
399 ms
29 ms
413 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 82% of them (40 requests) were addressed to the original Henecia.jp, 6% (3 requests) were made to S.ytimg.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Henecia.jp.
Page size can be reduced by 567.6 kB (47%)
1.2 MB
652.8 kB
In fact, the total size of Henecia.jp main page is 1.2 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. 35% of websites need less resources to load. Images take 624.1 kB which makes up the majority of the site volume.
Potential reduce by 10.2 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 17% 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 10.2 kB or 77% of the original size.
Potential reduce by 126.9 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. Obviously, HENECIA needs image optimization as it can save up to 126.9 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 202.3 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 202.3 kB or 66% of the original size.
Potential reduce by 228.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 needs all CSS files to be minified and compressed as it can save up to 228.3 kB or 83% of the original size.
Number of requests can be reduced by 11 (24%)
46
35
The browser has sent 46 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 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
henecia.jp
753 ms
common.css
1476 ms
ver_141201.css
399 ms
jquery.min.js
29 ms
jquery.hoverIntent.minified.js
413 ms
jquery.dcmegamenu.1.2.js
626 ms
jquery.flipcountdown_hn.css
239 ms
jquery.min.1.10.2.js
1553 ms
jquery.flipcountdown.js
592 ms
bg_wrap1506.jpg
747 ms
bg_home150612.jpg
1475 ms
hm_btn_login.png
208 ms
hm_btn_mypage.png
447 ms
hm_navi_profile.png
231 ms
hm_navi_news.png
447 ms
hm_navi_schedule.png
465 ms
hm_navi_gallery.png
506 ms
hm_navi_board.png
582 ms
hm_navi_report.png
617 ms
hm_navi_fcgoods.png
688 ms
countTitle_icon.png
705 ms
countTopL.png
971 ms
countTopR.png
1026 ms
countInLT.png
1133 ms
countInLB.png
903 ms
countInRT.png
1216 ms
countInRB.png
1102 ms
hm_ttl_news.png
1165 ms
hm_ttl_goodsnews.png
1231 ms
bstbs_kangeki_220_60.jpg
1500 ms
2015khjtourdvd_220_60.jpg
2066 ms
khj_bestalbum-re_220_60.jpg
4032 ms
kangekiost-220_60_2.jpg
2166 ms
tosidvd-hene220_62.jpg
1847 ms
khjtosiseibatuost-hene220_62.jpg
1683 ms
bnr4.jpg
2101 ms
khjsp_bnr120420s.jpg
1894 ms
ZfBk1sd5JB0
98 ms
www-embed-player-vflQrT_sR.css
70 ms
www-embed-player.js
95 ms
base.js
237 ms
hm_bg_newsbox.png
1688 ms
digit-md.png
2616 ms
digit-sm.png
2099 ms
digit-sm-col.png
1924 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
30 ms
ad_status.js
66 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
87 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
96 ms
henecia.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 input fields do not have accessible names
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
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.
henecia.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
henecia.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 uses legible font sizes
JA
JA
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.
henecia.jp
Open Graph description is not detected on the main page of HENECIA. 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: