2.5 sec in total
556 ms
1.8 sec
157 ms
Visit monopocket.jp now to see the best up-to-date Monopocket content for Japan and also check out these interesting facts you probably never knew about monopocket.jp
Just another WordPress site
Visit monopocket.jpWe analyzed Monopocket.jp page load time and found that the first response time was 556 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
monopocket.jp performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value1.6 s
100/100
10%
Value90 ms
99/100
30%
Value0.197
62/100
15%
Value3.1 s
95/100
10%
556 ms
188 ms
268 ms
369 ms
5 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 14% of them (8 requests) were addressed to the original Monopocket.jp, 43% (25 requests) were made to Widgets.itunes.apple.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (556 ms) belongs to the original domain Monopocket.jp.
Page size can be reduced by 430.8 kB (63%)
680.9 kB
250.0 kB
In fact, the total size of Monopocket.jp main page is 680.9 kB. 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. Javascripts take 539.9 kB which makes up the majority of the site volume.
Potential reduce by 11.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 11.6 kB or 69% of the original size.
Potential reduce by 7.6 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. Monopocket images are well optimized though.
Potential reduce by 377.1 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 377.1 kB or 70% of the original size.
Potential reduce by 34.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. Monopocket.jp needs all CSS files to be minified and compressed as it can save up to 34.6 kB or 83% of the original size.
Number of requests can be reduced by 32 (56%)
57
25
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Monopocket. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
monopocket.jp
556 ms
style.css
188 ms
all.js
268 ms
monopocket.js
369 ms
widgets.js
5 ms
bookmark_button.js
329 ms
button-only.gif
313 ms
background.png
401 ms
logo.png
373 ms
drama_fun.png
373 ms
148 ms
background_head.png
363 ms
xd_arbiter.php
262 ms
xd_arbiter.php
459 ms
widget.html
62 ms
background_content.png
321 ms
ga.js
10 ms
counter.js
35 ms
224 ms
__utm.gif
23 ms
t.php
187 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
54 ms
widget.css
32 ms
jquery.js
52 ms
handlebars.js
48 ms
underscore.js
47 ms
backbone.js
48 ms
bootstrap-typeahead.js
81 ms
itunes_item.js
90 ms
widget_templates.js
90 ms
widget.js
90 ms
jquery.tinyscrollbar.min.js
90 ms
web-storefront-preview.js
93 ms
web-storefront-base.js
89 ms
web-storefront-previewRegionSensitive.js
121 ms
itmsCheck.js
116 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
32 ms
xd_arbiter.php
226 ms
like.php
75 ms
piwik.js
53 ms
lookup
200 ms
vpc6VNjRPXV.js
500 ms
LVx-xkvaJ0b.png
556 ms
reset.css
11 ms
entry-button.css
12 ms
vbutton-bg.png
5 ms
jot
100 ms
countries.json
34 ms
ja_JP.css
50 ms
ja_JP.json
127 ms
100x100bb.jpg
74 ms
ajax-loader.gif
29 ms
header_app_store.png
27 ms
background_generic.png
30 ms
footer.png
31 ms
btn_view_jp.png
130 ms
background_scrollbar.png
38 ms
scrollbar_thumb.png
52 ms
monopocket.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
monopocket.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
monopocket.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Monopocket.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 Monopocket.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.
monopocket.jp
Open Graph data is detected on the main page of Monopocket. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: