7.7 sec in total
783 ms
6.3 sec
539 ms
Click here to check amazing Mwbunko content for Japan. Otherwise, check out these important facts you probably never knew about mwbunko.com
手のひらに、感動とトキメキと冒険を。かつてないエンタメノベル、メディアワークス文庫(毎月25日頃発売)の情報をお届けするオフィシャルウェブサイト。
Visit mwbunko.comWe analyzed Mwbunko.com page load time and found that the first response time was 783 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mwbunko.com performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value10.7 s
0/100
25%
Value25.8 s
0/100
10%
Value7,460 ms
0/100
30%
Value0.137
80/100
15%
Value50.5 s
0/100
10%
783 ms
703 ms
1319 ms
1187 ms
510 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 65% of them (72 requests) were addressed to the original Mwbunko.com, 9% (10 requests) were made to Cdn.kdkw.jp and 4% (4 requests) were made to Line-website.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Cdn.kdkw.jp.
Page size can be reduced by 1.5 MB (27%)
5.6 MB
4.1 MB
In fact, the total size of Mwbunko.com main page is 5.6 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. 70% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 46.6 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 46.6 kB or 80% of the original size.
Potential reduce by 66.5 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. Mwbunko images are well optimized though.
Potential reduce by 806.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 806.6 kB or 68% of the original size.
Potential reduce by 580.9 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. Mwbunko.com needs all CSS files to be minified and compressed as it can save up to 580.9 kB or 80% of the original size.
Number of requests can be reduced by 52 (50%)
103
51
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mwbunko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
mwbunko.com
783 ms
acms-admin.min.css
703 ms
bootstrap.min.css
1319 ms
bundle.min.css
1187 ms
reset.css
510 ms
common.css
680 ms
font.css
511 ms
newsicon.css
679 ms
top.css
851 ms
abj.css
848 ms
jquery-2.2.3.min.js
1059 ms
slick.min.js
24 ms
modernizr.js
876 ms
bundle.js
1859 ms
acms.js
1020 ms
index.js
1599 ms
bookmark_button.js
21 ms
pushy.css
1196 ms
pushy.js
1228 ms
loader.min.js
192 ms
top.js
1351 ms
widgets.js
93 ms
footer.js
1358 ms
gtm.js
58 ms
js
61 ms
analytics.js
28 ms
collect
114 ms
collect
33 ms
ga-audiences
77 ms
322309000385.jpg
1508 ms
cover.jpg
189 ms
chara2_top.jpg
1365 ms
0395836b1b758ff3d77a3d54e1c46bf5.png
186 ms
8451b36d37b0bdd2d14f7bc1caa1b8a7.png
185 ms
btn_more.png
184 ms
chara3_top.png
681 ms
b9807cf361454f73d11921ce8b2d5071.gif
345 ms
d20bf1431f49f0d7eac7ff2e96a44850.gif
345 ms
d485c04cba0454c60ef6db9a76744e27.png
346 ms
cd21cb20d3a8fbb1e0bff7ba9e3698af.gif
353 ms
7c31d517c07594269e75ceceb8edbed6.jpg
514 ms
logo_corporate.jpg
509 ms
logo_abj.svg
521 ms
heading-blog.svg
529 ms
mode3_w240_h240-807fa681767c636572678145fbee1971.jpg
674 ms
322309000386.jpg
1544 ms
322311001159.jpg
1704 ms
322401001347.jpg
1516 ms
322401001345.jpg
1510 ms
322402001787.jpg
1529 ms
322304000917.jpg
3132 ms
321905000122.jpg
2943 ms
322401001342.jpg
3030 ms
322401001341.jpg
2981 ms
sdk.js
116 ms
translation.json
667 ms
translation.json
617 ms
bg_release.gif
606 ms
logo.svg
740 ms
fontawesome-webfont.woff
752 ms
share_button.php
238 ms
p_icon_gnav_1.svg
758 ms
p_icon_gnav_2.svg
773 ms
p_icon_gnav_3.svg
801 ms
p_icon_gnav_4.svg
897 ms
p_icon_gnav_5.svg
913 ms
bg_news.gif
910 ms
chara1.png
936 ms
icon_tw.png
963 ms
bi.js
900 ms
td.min.js
104 ms
share
738 ms
share
795 ms
sdk.js
31 ms
arrow-left.svg
899 ms
arrow-right.svg
918 ms
ajax-loader.gif
930 ms
mode3__h360-44f7d36596d7ed08fd625426630a771d.jpg
961 ms
slick.woff
968 ms
mwbunko_all
46 ms
LdI20IMSy2-.js
30 ms
GzgedhmzSQa.png
50 ms
pixel
61 ms
pixel
19 ms
sync
4 ms
config.js
597 ms
widget.1.23.2.0.css
175 ms
button.1.23.2.0.js
153 ms
sentry.1.23.2.0.js
151 ms
torimochi.js
7 ms
line_v3@3x.png
4 ms
mode3__h360-c9b70e493ea2a6bac820c129648461eb.jpg
177 ms
jquery-ui.min.js
341 ms
mode3__h360-b793625df18d62e299c1a55d039ccf7e.jpg
177 ms
mode3__h360-e48d7a28e9adcd28ee6208861606f707.jpg
177 ms
jquery.ui.touch-punch.min.js
172 ms
mode3__h360-70cae19239f2ef18bbfed85fd6ff3c82.jpg
178 ms
jquery.cookie.js
172 ms
mode3__h360-25d32dda9f4fbf805f8be153aa0d66a4.jpg
178 ms
dispatch.js
172 ms
mode3__h360-96deddd410ecf07b4dbccee7e451cd9c.jpg
178 ms
bundle.css
343 ms
jquery-ui.min.css
180 ms
jquery-ui.min.css
182 ms
moduleDialog.js
177 ms
linkmatchlocation.js
200 ms
mode3__h360-9f4e23242d728b93728885ea97f6a11b.jpg
183 ms
mode3__h360-7eb668f5564c5c93a731dba109a8b808.jpg
178 ms
mode3__h360-7f3f9cdca2186d38c3e7b8107fc478e9.jpg
202 ms
mode3__h360-95e3adb1064936dd80f9541449c1f749.jpg
178 ms
mwbunko.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
mwbunko.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
mwbunko.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mwbunko.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 Mwbunko.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.
mwbunko.com
Open Graph data is detected on the main page of Mwbunko. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: