Tools & Wizards About Us
mihoyo.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mihoyo.co.jp

美少女・萌えゲーム/アプリ「崩壊学園」 - 公式サイト

Page Load Speed

7 sec in total

First Response

486 ms

Resources Loaded

5.9 sec

Page Rendered

622 ms

mihoyo.co.jp screenshot

About Website

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

美少女・萌えゲーム/アプリ「崩壊学園」。スマホ向け爽快横スクロールシューティングゲーム「崩壊学園」公式サイト

Visit mihoyo.co.jp

Key Findings

We analyzed Mihoyo.co.jp page load time and found that the first response time was 486 ms and then it took 6.5 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

mihoyo.co.jp performance score

0

Network Requests Diagram

mihoyo.co.jp

486 ms

UA.js

315 ms

Home.js

316 ms

Banner.js

318 ms

i.js

319 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 67% of them (49 requests) were addressed to the original Mihoyo.co.jp, 5% (4 requests) were made to Platform.twitter.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Mihoyo.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 409.1 kB (16%)

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 11.0 kB

  • Original 14.5 kB
  • After minification 9.7 kB
  • After compression 3.4 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.8 kB, which is 33% 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 11.0 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 22.9 kB

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

JavaScript Optimization

-65%

Potential reduce by 164.5 kB

  • Original 253.5 kB
  • After minification 252.9 kB
  • After compression 88.9 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 164.5 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 210.6 kB

  • Original 254.2 kB
  • After minification 250.8 kB
  • After compression 43.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. Mihoyo.co.jp needs all CSS files to be minified and compressed as it can save up to 210.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (49%)

Requests Now

70

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mihoyo.co.jp

mihoyo.co.jp

486 ms

UA.js

UA.js

315 ms

Home.js

Home.js

316 ms

Banner.js

Banner.js

318 ms

i.js

i.js

319 ms

i.css

i.css

318 ms

banner.css

banner.css

319 ms

menu.css

menu.css

611 ms

FooterLoad.js

FooterLoad.js

627 ms

MenuInit.js

MenuInit.js

664 ms

home_pc.css

home_pc.css

315 ms

dot_1.gif

dot_1.gif

300 ms

title.png

title.png

896 ms

h6.png

h6.png

316 ms

appstore.png

appstore.png

315 ms

googleplay.png

googleplay.png

316 ms

bg.jpg

bg.jpg

317 ms

button1.jpg

button1.jpg

923 ms

button2.jpg

button2.jpg

1065 ms

button3.jpg

button3.jpg

1071 ms

button4.jpg

button4.jpg

1073 ms

i.gif

i.gif

631 ms

visual_pc.html

visual_pc.html

911 ms

footer.html

footer.html

1305 ms

footer.css

footer.css

1321 ms

VQ4SyNPU4dQ

VQ4SyNPU4dQ

115 ms

visual1.jpg

visual1.jpg

1252 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

71 ms

www-embed-player.js

www-embed-player.js

98 ms

base.js

base.js

170 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

71 ms

ad_status.js

ad_status.js

93 ms

div.png

div.png

165 ms

0.png

0.png

321 ms

1.png

1.png

320 ms

2.png

2.png

316 ms

3.png

3.png

317 ms

4.png

4.png

456 ms

mihoyo.png

mihoyo.png

619 ms

arrow.png

arrow.png

627 ms

tag.js

tag.js

18 ms

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

80 ms

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

88 ms

tag

tag

46 ms

banner.html

banner.html

171 ms

ya.js

ya.js

375 ms

visual2.jpg

visual2.jpg

1281 ms

VQ4SyNPU4dQ

VQ4SyNPU4dQ

86 ms

TwitterScript.js

TwitterScript.js

161 ms

bn1.jpg

bn1.jpg

897 ms

pr-manga.jpg

pr-manga.jpg

792 ms

pv_wait.jpg

pv_wait.jpg

633 ms

pv_text.png

pv_text.png

327 ms

sound.jpg

sound.jpg

1113 ms

gamegift.png

gamegift.png

956 ms

lobi.png

lobi.png

937 ms

twitter.png

twitter.png

1107 ms

youtube.png

youtube.png

1210 ms

bn3.png

bn3.png

1254 ms

bn3-2.png

bn3-2.png

1254 ms

widgets.js

widgets.js

5 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

24 ms

pb.js

pb.js

521 ms

343 ms

syndication

syndication

109 ms

560688127065354240

560688127065354240

124 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

9 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

12 ms

sOz0iWAg_normal.png

sOz0iWAg_normal.png

137 ms

CcIe3t-UsAMe-5Z.jpg:small

CcIe3t-UsAMe-5Z.jpg:small

216 ms

CcIe3t-UsAMe-5Z.jpg

CcIe3t-UsAMe-5Z.jpg

243 ms

jot

jot

29 ms

visual3.jpg

visual3.jpg

1285 ms

SEO Factors

mihoyo.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mihoyo.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mihoyo.co.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

mihoyo.co.jp

Open Graph description is not detected on the main page of Mihoyo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: