6 sec in total
904 ms
4.8 sec
294 ms
Visit ienohikari.net now to see the best up-to-date Ienohikari content for Ukraine and also check out these interesting facts you probably never knew about ienohikari.net
家の光協会は、JAグループの出版文化団体です。月刊誌『家の光』をはじめ、各種雑誌・書籍を発行するほか、それらを活用したさまざまな文化事業を行っています。
Visit ienohikari.netWe analyzed Ienohikari.net page load time and found that the first response time was 904 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ienohikari.net performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value6.2 s
11/100
25%
Value7.1 s
31/100
10%
Value210 ms
88/100
30%
Value0.007
100/100
15%
Value9.5 s
30/100
10%
904 ms
507 ms
680 ms
686 ms
687 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 98% of them (83 requests) were addressed to the original Ienohikari.net, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ienohikari.net.
Page size can be reduced by 219.2 kB (13%)
1.7 MB
1.5 MB
In fact, the total size of Ienohikari.net main page is 1.7 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. 25% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 16.1 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 4.4 kB, which is 21% 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 16.1 kB or 78% of the original size.
Potential reduce by 85.4 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. Ienohikari images are well optimized though.
Potential reduce by 85.5 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 85.5 kB or 59% of the original size.
Potential reduce by 32.2 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. Ienohikari.net needs all CSS files to be minified and compressed as it can save up to 32.2 kB or 81% of the original size.
Number of requests can be reduced by 29 (35%)
84
55
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ienohikari. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ienohikari.net
904 ms
reset.css
507 ms
layout.css
680 ms
content.css
686 ms
index.css
687 ms
header_logo.png
724 ms
header_gnav_img01.png
491 ms
header_gnav_img02.png
656 ms
header_gnav_img03.png
672 ms
4%E6%9C%88%E8%A1%A8%E7%B4%99.jpg
1553 ms
header_gnav_img04.png
665 ms
header_gnav_img05.png
682 ms
header_subnav_img01.png
690 ms
header_subnav_img02.png
697 ms
header_fontsize_ttl.png
700 ms
header_fontsize_btn01.png
729 ms
header_fontsize_btn02.png
831 ms
header_fontsize_btn03.png
849 ms
header_search_btn.png
858 ms
px.png
867 ms
index_ttl01.png
871 ms
index_ttl02.png
904 ms
16cj04_01_OL.jpg
1559 ms
1604hyoshi.jpg
1560 ms
Vege16Spring-cover.jpg
2381 ms
index_img02.jpg
997 ms
index_img04.jpg
1019 ms
index_img06.jpg
1030 ms
index_img07.jpg
1211 ms
index_ttl03.png
875 ms
ja.png
914 ms
lib.js
1902 ms
common.js
1264 ms
bookrack.js
1156 ms
aside_ttl01.png
1347 ms
aside_bnr13.gif
1193 ms
aside_bnr14.jpg
1486 ms
aside_bnr15.jpg
1530 ms
aside_bnr17.jpg
1545 ms
aside_bnr09.png
1438 ms
aside_bnr02.jpg
1850 ms
aside_bnr04.jpg
1636 ms
content_returntop.png
1483 ms
footer_bnr08.gif
1378 ms
body_bg.png
1519 ms
container_bg.png
2115 ms
header_bg02.png
1502 ms
header_search_bg.png
1581 ms
main_bg.jpg
2004 ms
loading.gif
1551 ms
shade03.jpg
1553 ms
shade01.jpg
1556 ms
bg01.png
1628 ms
index_bg01.png
1685 ms
arrow01.png
1676 ms
dotline01.png
1586 ms
arrow02.png
1651 ms
arrow04.png
1695 ms
aside_frame_bg01.png
1708 ms
aside_frame_bg02.png
1717 ms
arrow03.png
1773 ms
footer_bg01.png
1680 ms
footer_bg02.png
1654 ms
footer_bg03.png
1583 ms
ga.js
4 ms
top.xml
632 ms
__utm.gif
11 ms
header_gnav_img01_on.png
694 ms
header_gnav_img02_on.png
722 ms
header_gnav_img03_on.png
760 ms
header_gnav_img04_on.png
772 ms
header_gnav_img05_on.png
785 ms
header_fontsize_btn01_on.png
800 ms
header_fontsize_btn02_on.png
858 ms
header_fontsize_btn03_on.png
899 ms
prev01_disable.jpg
929 ms
next01_disable.jpg
940 ms
book_01.jpg
661 ms
book_02.jpg
679 ms
book_03.jpg
555 ms
book_04.jpg
1148 ms
book_05.jpg
1308 ms
book_06.jpg
640 ms
shade02.jpg
721 ms
prev02_disable.jpg
808 ms
ienohikari.net accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
ienohikari.net 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
ienohikari.net SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ienohikari.net 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 Ienohikari.net 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.
ienohikari.net
Open Graph description is not detected on the main page of Ienohikari. 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: