4.5 sec in total
617 ms
3.4 sec
488 ms
Welcome to happylilac.net homepage info - get ready to check Happylilac best content for Japan right away, or after learning these important things about happylilac.net
幼児・小学生の教育に役立つオリジナル教材コンテンツサイト。
Visit happylilac.netWe analyzed Happylilac.net page load time and found that the first response time was 617 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
happylilac.net performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.8 s
30/100
25%
Value9.7 s
10/100
10%
Value1,480 ms
14/100
30%
Value0.591
11/100
15%
Value12.6 s
14/100
10%
617 ms
197 ms
31 ms
9 ms
86 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 64% of them (70 requests) were addressed to the original Happylilac.net, 6% (6 requests) were made to Pagead2.googlesyndication.com and 6% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source I.yimg.jp.
Page size can be reduced by 75.5 kB (25%)
303.7 kB
228.2 kB
In fact, the total size of Happylilac.net main page is 303.7 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. 55% of websites need less resources to load. Images take 218.4 kB which makes up the majority of the site volume.
Potential reduce by 45.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 7.9 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 45.2 kB or 81% of the original size.
Potential reduce by 22.7 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. Happylilac images are well optimized though.
Potential reduce by 6.6 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 6.6 kB or 24% of the original size.
Potential reduce by 1.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. Happylilac.net needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 65% of the original size.
Number of requests can be reduced by 19 (18%)
103
84
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Happylilac. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
happylilac.net
617 ms
css-toppage.css
197 ms
brand
31 ms
show_ads.js
9 ms
widgets.js
86 ms
brand
79 ms
ga.js
95 ms
twitter-a.png
82 ms
google_custom_search_watermark.gif
159 ms
ca-pub-2134185575187691.js
155 ms
zrt_lookup.html
153 ms
show_ads_impl.js
93 ms
white_logo.gif
319 ms
yahoojp_sm.gif
1477 ms
portal-logo200.gif
243 ms
padinhouse-logo20141201.gif
390 ms
facebook-banner-20160107.gif
449 ms
categoryicon-13.gif
466 ms
categoryicon-01.gif
465 ms
categoryicon-02.gif
465 ms
categoryicon-10.gif
466 ms
708banner-2.gif
736 ms
yojinogakusyu-460px.gif
580 ms
087.gif
629 ms
d120-50hiragana-ha.jpg
628 ms
d120--katakana-i.jpg
625 ms
dmeiro-mixer-120.jpg
633 ms
d120ten-katatumuri-an.jpg
757 ms
d120-suuzi-c-3.jpg
814 ms
d120-machi-keisatu-qu-7.jpg
820 ms
d120-nurie-daiku.jpg
821 ms
d120tokei-re-2-1.jpg
829 ms
120nazonazo1-50.jpg
906 ms
d120-hito-nikki-1-2.jpg
935 ms
120sugoroku-kikyu.jpg
1003 ms
120toporigami-koinobori-ln.jpg
1012 ms
--120kotoba-karada.jpg
1014 ms
120s-tenbyousya-1-01.jpg
1025 ms
top120-omocha-okane.jpg
1078 ms
120y-wordpuzzle-01.jpg
1113 ms
120silhouette-02.jpg
1192 ms
hasami-hinakazari-03s120.gif
1204 ms
120hiragana-kakizyun.jpg
1207 ms
120katakana-kakizyun.jpg
1222 ms
d12099hyo2-9-s.jpg
1250 ms
120kazu-30.jpg
1289 ms
d1200_-tokei-poster.jpg
1382 ms
120-crayon-sen-01.jpg
1397 ms
120papertheater-momotarou.gif
1400 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
183 ms
120nurie-alphabet201510.gif
1388 ms
__utm.gif
63 ms
ads
242 ms
cf5f02a7dec1.png
44 ms
osd.js
44 ms
ads
217 ms
ads
337 ms
collect
77 ms
d93e757e1104.png
39 ms
like.php
88 ms
ads
573 ms
ga-audiences
17 ms
vpc6VNjRPXV.js
83 ms
LVx-xkvaJ0b.png
82 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
55 ms
sitelogo-460_113px-15.gif
1184 ms
css
56 ms
m_js_controller.js
25 ms
abg.js
28 ms
460logo-cbms20151106.gif
1082 ms
favicon
74 ms
nessie_icon_tiamat_white.png
51 ms
s
45 ms
googlelogo_color_112x36dp.png
53 ms
x_button_blue2.png
34 ms
jot
98 ms
d1200tizu-ee-todohuken.jpg
1113 ms
sekaitizu-mihon.jpg
1128 ms
120s-rekishi-test_zidai-01.jpg
1132 ms
125-hacalendar-2013-01.gif
1132 ms
d120getsurei2011-n.jpg
1156 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
4 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
59 ms
120sansu-6masu.jpg
1069 ms
d120k1-ichi.jpg
1139 ms
120kanjiQ3_Q1.gif
1157 ms
120roman-hyo3.jpg
1160 ms
120s-romanpractice-alphabet-01.jpg
1137 ms
120s-kanyoku-01.jpg
1084 ms
d1200unit-3.jpg
1071 ms
masu-ta1001as.jpg
1141 ms
s-120-keisan-siritori-th02-01.jpg
1123 ms
120s-jikankoku1-01.jpg
1157 ms
120s-20-kazoekata01.jpg
1154 ms
sitelogo-460_113px-03.gif
1111 ms
top--alphabet-hyo-a4.jpg
1069 ms
top-alphabet-a.jpg
1111 ms
170alphabet-note-1.jpg
1131 ms
caan-top.jpg
1156 ms
top-aloten-iruka-an.jpg
1151 ms
sitelogo-460_113px-08.gif
1281 ms
sitelogo-460_113px-09.gif
1294 ms
sitelogo-460_113px-11.gif
1093 ms
sitelogo-460_113px-12.gif
1316 ms
sitelogo-460_113px-10.gif
1156 ms
sitelogo-460_113px-13.gif
1339 ms
sitelogo-460_113px-04.gif
1209 ms
sitelogo-460_113px-14.gif
1250 ms
activeview
16 ms
happylilac.net 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-*] attributes do not match their roles
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
Form elements do not have associated labels
Links do not have a discernible name
happylilac.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
happylilac.net SEO score
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
Tap targets are not sized appropriately
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Happylilac.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Happylilac.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
happylilac.net
Open Graph description is not detected on the main page of Happylilac. 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: