Tools & Wizards About Us
harmorise.jp screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

harmorise.jp

ひとつ屋根の、ツバサの下で | harmorise

Page Load Speed

8.5 sec in total

First Response

494 ms

Resources Loaded

6.6 sec

Page Rendered

1.4 sec

harmorise.jp screenshot

About Website

Click here to check amazing Harmorise content for South Korea. Otherwise, check out these important facts you probably never knew about harmorise.jp

女の子と一つ屋根の下、空戦競技に挑む夏!

Visit harmorise.jp

Key Findings

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

Performance Metrics

harmorise.jp performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value25.6 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value2,210 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.425

22/100

15%

TTI (Time to Interactive)

Value22.3 s

1/100

10%

Network Requests Diagram

494 ms

style.css

860 ms

css

48 ms

fontplus.js

1206 ms

script.js

1302 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 64% of them (88 requests) were addressed to the original Harmorise.jp, 13% (18 requests) were made to Platform.twitter.com and 6% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Harmorise.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.8 kB (3%)

Content Size

7.7 MB

After Optimization

7.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Harmorise.jp main page is 7.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 7.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.1 kB

  • Original 59.2 kB
  • After minification 51.7 kB
  • After compression 11.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 7.5 kB, which is 13% 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 48.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 984 B

  • Original 7.2 MB
  • After minification 7.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. Harmorise images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 149.9 kB

  • Original 391.5 kB
  • After minification 391.5 kB
  • After compression 241.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 149.9 kB or 38% of the original size.

CSS Optimization

-30%

Potential reduce by 28.8 kB

  • Original 96.1 kB
  • After minification 95.9 kB
  • After compression 67.3 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. Harmorise.jp needs all CSS files to be minified and compressed as it can save up to 28.8 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (25%)

Requests Now

126

After Optimization

94

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

494 ms

style.css

style.css

860 ms

css

css

48 ms

fontplus.js

fontplus.js

1206 ms

script.js

script.js

1302 ms

prf6voe.js

prf6voe.js

87 ms

character.png

character.png

1544 ms

mainvisual_bg.jpg

mainvisual_bg.jpg

1079 ms

logo.png

logo.png

363 ms

catch.png

catch.png

523 ms

release.png

release.png

522 ms

look1.jpg

look1.jpg

522 ms

look2.jpg

look2.jpg

554 ms

look3.jpg

look3.jpg

840 ms

look1.jpg

look1.jpg

840 ms

look2.jpg

look2.jpg

840 ms

look3.jpg

look3.jpg

840 ms

look1.jpg

look1.jpg

966 ms

look2.jpg

look2.jpg

965 ms

look3.jpg

look3.jpg

968 ms

look1.jpg

look1.jpg

926 ms

look2.jpg

look2.jpg

1078 ms

look3.jpg

look3.jpg

1191 ms

diagram.png

diagram.png

1866 ms

01.jpg

01.jpg

1722 ms

02.jpg

02.jpg

1374 ms

03.jpg

03.jpg

1556 ms

04.jpg

04.jpg

1487 ms

05.jpg

05.jpg

1703 ms

06.jpg

06.jpg

1860 ms

07.jpg

07.jpg

1870 ms

08.jpg

08.jpg

1879 ms

09.jpg

09.jpg

2031 ms

10.jpg

10.jpg

2099 ms

11.jpg

11.jpg

2046 ms

12.jpg

12.jpg

2240 ms

13.jpg

13.jpg

2035 ms

14.jpg

14.jpg

2201 ms

15.jpg

15.jpg

2196 ms

16.jpg

16.jpg

2199 ms

17.jpg

17.jpg

2232 ms

widgets.js

widgets.js

12 ms

18.jpg

18.jpg

2247 ms

BlPWAyhb2j8

BlPWAyhb2j8

316 ms

analytics.js

analytics.js

235 ms

mkfont

mkfont

676 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

112 ms

3d4c80e6

3d4c80e6

520 ms

d

d

64 ms

d

d

109 ms

d

d

109 ms

d

d

152 ms

d

d

109 ms

d

d

200 ms

d

d

120 ms

p.gif

p.gif

112 ms

19.jpg

19.jpg

2002 ms

collect

collect

33 ms

js

js

121 ms

settings

settings

454 ms

www-player.css

www-player.css

62 ms

www-embed-player.js

www-embed-player.js

90 ms

base.js

base.js

148 ms

20.jpg

20.jpg

1846 ms

title.jpg

title.jpg

2167 ms

title_patch.jpg

title_patch.jpg

1901 ms

dlsite.jpg

dlsite.jpg

1844 ms

ad_status.js

ad_status.js

198 ms

jDVVIT4ZwDHfBiET8TcWj790JrYgF6qU1g_sOcBWI_w.js

jDVVIT4ZwDHfBiET8TcWj790JrYgF6qU1g_sOcBWI_w.js

191 ms

embed.js

embed.js

80 ms

sofmap.gif

sofmap.gif

1641 ms

sofmap_01.png

sofmap_01.png

1854 ms

sofmap_02.png

sofmap_02.png

1855 ms

icon_sofmap.png

icon_sofmap.png

1768 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

93 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

100 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

39 ms

id

id

62 ms

getchu.gif

getchu.gif

1692 ms

getchu.png

getchu.png

2270 ms

icon_getchu.png

icon_getchu.png

1828 ms

trader.jpg

trader.jpg

1838 ms

Create

Create

120 ms

Harmorise_info

Harmorise_info

214 ms

trader.png

trader.png

2094 ms

melonbooks.gif

melonbooks.gif

1780 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

4 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

19 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

24 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

32 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

47 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

49 ms

_buildManifest.js

_buildManifest.js

58 ms

_ssgManifest.js

_ssgManifest.js

45 ms

melonbooks.png

melonbooks.png

1830 ms

GenerateIT

GenerateIT

78 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

13 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

12 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

5 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

11 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

18 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

18 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

8 ms

toranoana.gif

toranoana.gif

1607 ms

toranoana.png

toranoana.png

1880 ms

yodobashi.png

yodobashi.png

1481 ms

yodobashi.png

yodobashi.png

1797 ms

amazon.png

amazon.png

1484 ms

amazon.png

amazon.png

1468 ms

mk.png

mk.png

1474 ms

fammys.png

fammys.png

1488 ms

chukyomycom.png

chukyomycom.png

1483 ms

bookmate.png

bookmate.png

1545 ms

takarajima.png

takarajima.png

1464 ms

comroad.png

comroad.png

1483 ms

prop.png

prop.png

1473 ms

alicenet.png

alicenet.png

1441 ms

sofpit.png

sofpit.png

1359 ms

surugaya.png

surugaya.png

1414 ms

nankai.png

nankai.png

1456 ms

furukawa.png

furukawa.png

1450 ms

dmm.png

dmm.png

1443 ms

amiami.png

amiami.png

1438 ms

bg1.jpg

bg1.jpg

1568 ms

bg2.jpg

bg2.jpg

1627 ms

bg3.jpg

bg3.jpg

1561 ms

visual.png

visual.png

1419 ms

visual.png

visual.png

1369 ms

visual.png

visual.png

1308 ms

visual.png

visual.png

1404 ms

bg.png

bg.png

1334 ms

bg.jpg

bg.jpg

1409 ms

bg.png

bg.png

1427 ms

bg.png

bg.png

1351 ms

bg.png

bg.png

1377 ms

bg.png

bg.png

1321 ms

log_event

log_event

16 ms

Accessibility Review

harmorise.jp accessibility score

71

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

harmorise.jp best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

harmorise.jp SEO score

92

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

Image elements do not have [alt] attributes

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

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

harmorise.jp

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