Access heartin.com. クリック募金 | HEARTiN（ハーティン）

Report Summary

About Website

Click here to check amazing HEARTiN content for Japan. Otherwise, check out these important facts you probably never knew about heartin.com

世界をよりよくするために。クリック募金「ハーティン」。ハートボタンをクリックすると、あなたに代わってスポンサーが寄付をします。

Visit heartin.com

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

heartin.com

712 ms

import.css

337 ms

main.js

355 ms

jquery.min.js

32 ms

script.js

366 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 84% of them (52 requests) were addressed to the original Heartin.com, 5% (3 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Heartin.com.

Content Size

1.2 MB

After Optimization

1.1 MB

In fact, the total size of Heartin.com 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 22.9 kB

Original 29.0 kB
After minification 24.4 kB
After compression 6.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.6 kB, which is 16% 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 22.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

Original 1.1 MB
After minification 1.1 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. HEARTiN images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 9.8 kB

Original 12.8 kB
After minification 10.2 kB
After compression 3.0 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 9.8 kB or 77% of the original size.

CSS Optimization

-78%

Potential reduce by 37.0 kB

Original 47.4 kB
After minification 44.2 kB
After compression 10.4 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. Heartin.com needs all CSS files to be minified and compressed as it can save up to 37.0 kB or 78% of the original size.

Requests Now

After Optimization

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HEARTiN. 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 18 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heartin.com 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 Heartin.com main page’s claimed encoding is euc-jp. 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.

Social Sharing Optimization

heartin.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

クリック募金 | HEARTiN（ハーティン）

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)