Tools & Wizards About Us
heartland.jp screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

heartland.jp

HEARTLAND｜キリン

Page Load Speed

5.7 sec in total

First Response

488 ms

Resources Loaded

3.9 sec

Page Rendered

1.3 sec

heartland.jp screenshot

About Website

Click here to check amazing HEARTLAND content for Japan. Otherwise, check out these important facts you probably never knew about heartland.jp

ハートランドビール。「素（そ・もと）」モノの本来の価値の発見。流行や権威、既存の価値観に左右されることなくモノ本来の価値に気付く、発見する、自分にとっての本物を追求する。

Visit heartland.jp

Key Findings

We analyzed Heartland.jp page load time and found that the first response time was 488 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

heartland.jp performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value1,740 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

heartland.jp

488 ms

common.css

314 ms

modern.css

316 ms

plugin.css

318 ms

style.css

628 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 92% of them (57 requests) were addressed to the original Heartland.jp, 6% (4 requests) were made to Googletagmanager.com and 2% (1 request) were made to Kirinholdings.co.jp. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Heartland.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 628.8 kB (9%)

Content Size

7.3 MB

After Optimization

6.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heartland.jp main page is 7.3 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. 65% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 13.4 kB

  • Original 18.6 kB
  • After minification 16.8 kB
  • After compression 5.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 13.4 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 55.3 kB

  • Original 6.6 MB
  • After minification 6.5 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. HEARTLAND images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 463.3 kB

  • Original 618.7 kB
  • After minification 584.9 kB
  • After compression 155.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 463.3 kB or 75% of the original size.

CSS Optimization

-88%

Potential reduce by 96.8 kB

  • Original 110.2 kB
  • After minification 86.1 kB
  • After compression 13.5 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. Heartland.jp needs all CSS files to be minified and compressed as it can save up to 96.8 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (14%)

Requests Now

59

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heartland.jp

heartland.jp

488 ms

common.css

common.css

314 ms

modern.css

modern.css

316 ms

plugin.css

plugin.css

318 ms

style.css

style.css

628 ms

code.js

code.js

294 ms

plugin.js

plugin.js

1191 ms

app.js

app.js

624 ms

gtm.js

gtm.js

36 ms

gtm.js

gtm.js

45 ms

bg-gray.jpg

bg-gray.jpg

162 ms

loading-logo-bg.png

loading-logo-bg.png

164 ms

bg-gray.jpg

bg-gray.jpg

163 ms

text-scrolldown.png

text-scrolldown.png

161 ms

pct-banner01.jpg

pct-banner01.jpg

1081 ms

pct-banner04.jpg

pct-banner04.jpg

1253 ms

pct-banner03.jpg

pct-banner03.jpg

948 ms

pct-banner02.jpg

pct-banner02.jpg

1101 ms

title01.png

title01.png

476 ms

bg-grid.png

bg-grid.png

1306 ms

bg02.png

bg02.png

880 ms

pct-page01.png

pct-page01.png

1050 ms

pct-page02.png

pct-page02.png

1108 ms

pct-page03.png

pct-page03.png

1221 ms

pct-page04.png

pct-page04.png

1239 ms

pct-page01.png

pct-page01.png

1260 ms

pct-page02.png

pct-page02.png

1267 ms

pct-page03.png

pct-page03.png

1391 ms

pct-page04.png

pct-page04.png

1397 ms

title02.png

title02.png

1411 ms

title03.png

title03.png

1420 ms

title-sub01.png

title-sub01.png

1427 ms

title-sub02.png

title-sub02.png

1475 ms

title04.png

title04.png

1560 ms

arw-right.png

arw-right.png

1555 ms

btn-history.png

btn-history.png

1569 ms

btn-journey.jpg

btn-journey.jpg

1580 ms

btn-forest.jpg

btn-forest.jpg

1741 ms

btn-slice.jpg

btn-slice.jpg

2800 ms

bg.jpg

bg.jpg

1715 ms

btn-concept.png

btn-concept.png

1730 ms

btn-history.png

btn-history.png

1727 ms

btn-gallery.png

btn-gallery.png

1739 ms

btn-journey.png

btn-journey.png

1846 ms

gtm.js

gtm.js

152 ms

gtm.js

gtm.js

79 ms

btn-forest.png

btn-forest.png

1748 ms

btn-slice.png

btn-slice.png

1743 ms

title-share.png

title-share.png

1741 ms

bg-sns.png

bg-sns.png

1742 ms

btn-facebook.png

btn-facebook.png

1872 ms

btn-twitter.png

btn-twitter.png

1573 ms

se.json

se.json

1292 ms

text-attention.png

text-attention.png

1194 ms

pagetop_001.jpg

pagetop_001.jpg

1119 ms

logo_01.png

logo_01.png

1144 ms

foot_copy_001.jpg

foot_copy_001.jpg

1128 ms

foot_img_001.jpg

foot_img_001.jpg

1120 ms

loading-logo.png

loading-logo.png

1116 ms

btn-yes.png

btn-yes.png

162 ms

btn-no.png

btn-no.png

172 ms

style-sp.css

style-sp.css

161 ms

Accessibility Review

heartland.jp accessibility score

82

Accessibility Issues

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

Links do not have a discernible name

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

heartland.jp 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

Missing source maps for large first-party JavaScript

SEO Factors

heartland.jp SEO score

83

Search Engine Optimization Advices

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 doesn't use legible font sizes

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 Heartland.jp 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 Heartland.jp 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

heartland.jp

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