Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

happylilac.net

幼児・小学生・中学生の無料知育教材、無料学習教材プリント|ちびむすドリル

Page Load Speed

6.8 sec in total

First Response

564 ms

Resources Loaded

5.8 sec

Page Rendered

412 ms

happylilac.net screenshot

About Website

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

Key Findings

We analyzed Happylilac.net page load time and found that the first response time was 564 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.

Performance Metrics

happylilac.net performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.591

11/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

happylilac.net

564 ms

happylilac.net

761 ms

jquery.min.js

59 ms

font-awesome.min.css

69 ms

reset.css

190 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 57% of them (72 requests) were addressed to the original Happylilac.net, 6% (7 requests) were made to Tpc.googlesyndication.com and 4% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Happylilac.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (55%)

Content Size

4.2 MB

After Optimization

1.9 MB

In fact, the total size of Happylilac.net main page is 4.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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 51.9 kB

  • Original 66.8 kB
  • After minification 63.7 kB
  • After compression 14.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.9 kB or 78% of the original size.

Image Optimization

-60%

Potential reduce by 1.8 MB

  • Original 3.0 MB
  • After minification 1.2 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. Obviously, Happylilac needs image optimization as it can save up to 1.8 MB or 60% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-41%

Potential reduce by 432.0 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 612.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 432.0 kB or 41% of the original size.

CSS Optimization

-22%

Potential reduce by 3.5 kB

  • Original 16.1 kB
  • After minification 16.1 kB
  • After compression 12.6 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 3.5 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (37%)

Requests Now

120

After Optimization

76

The browser has sent 120 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 30 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

happylilac.net accessibility score

86

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

happylilac.net best practices score

83

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

Page has valid source maps

SEO Factors

happylilac.net SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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

Social Sharing Optimization

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