Tools & Wizards About Us
mwissoku.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mwissoku.com

魔法使いの俺とウィズ速報

Page Load Speed

7.9 sec in total

First Response

658 ms

Resources Loaded

5.1 sec

Page Rendered

2.1 sec

mwissoku.com screenshot

About Website

Visit mwissoku.com now to see the best up-to-date Mwissoku content for Japan and also check out these interesting facts you probably never knew about mwissoku.com

当サイトは株式会社コロプラ提供のスマホ用ゲーム 「魔法使いと黒猫のウィズ」の情報を扱ったまとめサイトです

Visit mwissoku.com

Key Findings

We analyzed Mwissoku.com page load time and found that the first response time was 658 ms and then it took 7.2 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

mwissoku.com performance score

0

Network Requests Diagram

mwissoku.com

658 ms

template.css

523 ms

site.css

640 ms

c2.js

527 ms

smartphone.js

554 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Mwissoku.com, 28% (35 requests) were made to Cdn.b.st-hatena.com and 11% (13 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 200.1 kB (18%)

Content Size

1.1 MB

After Optimization

901.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mwissoku.com main page is 1.1 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 838.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 135.8 kB

  • Original 156.9 kB
  • After minification 140.6 kB
  • After compression 21.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. 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 135.8 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 3.7 kB

  • Original 838.1 kB
  • After minification 834.4 kB

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. Mwissoku images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 25.1 kB

  • Original 64.6 kB
  • After minification 57.7 kB
  • After compression 39.5 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 25.1 kB or 39% of the original size.

CSS Optimization

-84%

Potential reduce by 35.4 kB

  • Original 42.0 kB
  • After minification 30.6 kB
  • After compression 6.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. Mwissoku.com needs all CSS files to be minified and compressed as it can save up to 35.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 82 (67%)

Requests Now

122

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mwissoku.com

mwissoku.com

658 ms

template.css

template.css

523 ms

site.css

site.css

640 ms

c2.js

c2.js

527 ms

smartphone.js

smartphone.js

554 ms

ad.js

ad.js

515 ms

blogroll.js

blogroll.js

856 ms

default2.css

default2.css

477 ms

ads.js

ads.js

484 ms

widgets.js

widgets.js

244 ms

mwissoku.js

mwissoku.js

581 ms

rank.php

rank.php

610 ms

jsapi

jsapi

324 ms

ga.js

ga.js

163 ms

2c6ffd58.jpg

2c6ffd58.jpg

1471 ms

default_profile_0_bigger.png

default_profile_0_bigger.png

116 ms

rranking.gif

rranking.gif

228 ms

futa.jpg

futa.jpg

796 ms

c

c

627 ms

__utm.gif

__utm.gif

45 ms

roll_data

roll_data

344 ms

roll_data

roll_data

349 ms

title_line.gif

title_line.gif

336 ms

icon_categry.gif

icon_categry.gif

339 ms

icon_comment.gif

icon_comment.gif

339 ms

adcore.js

adcore.js

53 ms

adcore_pc.js

adcore_pc.js

99 ms

adcore_pc_inline.js

adcore_pc_inline.js

47 ms

ad_spot.aspx

ad_spot.aspx

1177 ms

ad_spot.aspx

ad_spot.aspx

1102 ms

1.gif

1.gif

189 ms

blank.gif

blank.gif

1023 ms

blank.gif

blank.gif

323 ms

like.php

like.php

456 ms

like.php

like.php

587 ms

like.php

like.php

581 ms

like.php

like.php

557 ms

like.php

like.php

579 ms

like.php

like.php

601 ms

roll_data

roll_data

323 ms

like.php

like.php

622 ms

ad_spot.aspx

ad_spot.aspx

737 ms

arrow.gif

arrow.gif

317 ms

ad_spot.aspx

ad_spot.aspx

832 ms

like.php

like.php

583 ms

ad_spot.aspx

ad_spot.aspx

721 ms

like.php

like.php

550 ms

like.php

like.php

588 ms

like.php

like.php

620 ms

like.php

like.php

661 ms

popular_articles.json

popular_articles.json

561 ms

ad_spot.aspx

ad_spot.aspx

801 ms

pvi.php

pvi.php

634 ms

00000.gif

00000.gif

216 ms

pvi.php

pvi.php

1190 ms

ad_spot.aspx

ad_spot.aspx

790 ms

ad_spot.aspx

ad_spot.aspx

677 ms

00000.gif

00000.gif

159 ms

00000.gif

00000.gif

172 ms

00000.gif

00000.gif

159 ms

00000.gif

00000.gif

169 ms

Sh_BYjerrZ8.js

Sh_BYjerrZ8.js

2413 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

2488 ms

00000.gif

00000.gif

221 ms

ad_spot.aspx

ad_spot.aspx

575 ms

blank.gif

blank.gif

296 ms

00000.gif

00000.gif

212 ms

147 ms

like.php

like.php

235 ms

00000.gif

00000.gif

155 ms

00000.gif

00000.gif

153 ms

00000.gif

00000.gif

153 ms

00000.gif

00000.gif

141 ms

00000.gif

00000.gif

136 ms

00000.gif

00000.gif

133 ms

style.css

style.css

458 ms

ad_creative.ashx

ad_creative.ashx

258 ms

default+en.css

default+en.css

95 ms

default+en.I.js

default+en.I.js

140 ms

style.css

style.css

281 ms

ad_creative.ashx

ad_creative.ashx

322 ms

00000.gif

00000.gif

358 ms

00000.gif

00000.gif

117 ms

ad_creative.ashx

ad_creative.ashx

353 ms

00000.gif

00000.gif

119 ms

00000.gif

00000.gif

108 ms

00000.gif

00000.gif

77 ms

ad_creative.ashx

ad_creative.ashx

244 ms

u.js

u.js

646 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

192 ms

ad_creative.ashx

ad_creative.ashx

620 ms

00000.gif

00000.gif

45 ms

00000.gif

00000.gif

46 ms

ad_creative.ashx

ad_creative.ashx

612 ms

00000.gif

00000.gif

42 ms

ad_creative.ashx

ad_creative.ashx

429 ms

ad_creative.ashx

ad_creative.ashx

507 ms

00000.gif

00000.gif

46 ms

00000.gif

00000.gif

43 ms

ad_creative.ashx

ad_creative.ashx

562 ms

tweet_button.fd774b599f565016d763dd860cb31c79.ja.html

tweet_button.fd774b599f565016d763dd860cb31c79.ja.html

214 ms

00000.gif

00000.gif

320 ms

00000.gif

00000.gif

238 ms

00000.gif

00000.gif

237 ms

00000.gif

00000.gif

182 ms

00000.gif

00000.gif

65 ms

00000.gif

00000.gif

50 ms

00000.gif

00000.gif

50 ms

00000.gif

00000.gif

42 ms

00000.gif

00000.gif

35 ms

00000.gif

00000.gif

57 ms

00000.gif

00000.gif

38 ms

00000.gif

00000.gif

33 ms

jot.html

jot.html

54 ms

RestoreXidToMediaStorage.html

RestoreXidToMediaStorage.html

158 ms

Gfeeds

Gfeeds

74 ms

Gfeeds

Gfeeds

73 ms

Gfeeds

Gfeeds

141 ms

Gfeeds

Gfeeds

139 ms

Gfeeds

Gfeeds

181 ms

Gfeeds

Gfeeds

185 ms

Gfeeds

Gfeeds

183 ms

Gfeeds

Gfeeds

192 ms

SEO Factors

mwissoku.com SEO score

0

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 Mwissoku.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 Mwissoku.com 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

mwissoku.com

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