Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

kidsline.me

キッズライン | ベビーシッターマッチング・病児保育/一時保育

Page Load Speed

76.6 sec in total

First Response

315 ms

Resources Loaded

74.1 sec

Page Rendered

2.2 sec

kidsline.me screenshot

About Website

Click here to check amazing Kidsline content for Japan. Otherwise, check out these important facts you probably never knew about kidsline.me

【キッズライン】ベビーシッターならご予算や依頼内容に合わせてサポーターが選べる安全安心のkidsline。入会金不要で手続きもオンラインで簡単。手軽にご利用いただけます。

Visit kidsline.me

Key Findings

We analyzed Kidsline.me page load time and found that the first response time was 315 ms and then it took 76.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 74 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

kidsline.me performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value33.0 s

0/100

25%

SI (Speed Index)

Value25.9 s

0/100

10%

TBT (Total Blocking Time)

Value3,880 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value39.7 s

0/100

10%

Network Requests Diagram

kidsline.me

315 ms

kidsline.me

13846 ms

bootstrap.min.css

19922 ms

font-awesome-6.5.2-all.min.css

19922 ms

font-awesome-4.6.3.min.css

19921 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 58% of them (76 requests) were addressed to the original Kidsline.me, 24% (32 requests) were made to D1g4k4av3m79e8.cloudfront.net and 3% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Kidsline.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 422.2 kB (12%)

Content Size

3.7 MB

After Optimization

3.2 MB

In fact, the total size of Kidsline.me main page is 3.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. Only a small number of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 141.9 kB

  • Original 178.2 kB
  • After minification 178.1 kB
  • After compression 36.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. 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 141.9 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 275.0 kB

  • Original 2.6 MB
  • After minification 2.3 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, Kidsline needs image optimization as it can save up to 275.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 3.4 kB

  • Original 658.1 kB
  • After minification 658.1 kB
  • After compression 654.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 1.8 kB

  • Original 252.4 kB
  • After minification 252.4 kB
  • After compression 250.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. Kidsline.me has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (38%)

Requests Now

55

After Optimization

34

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

Accessibility Review

kidsline.me accessibility score

74

Accessibility Issues

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

High

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

High

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

High

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

Best Practices

kidsline.me best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

kidsline.me SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Kidsline.me 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 Kidsline.me 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 Kidsline. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: