13.4 sec in total
4.3 sec
8.7 sec
455 ms
Visit mon-ey.jp now to see the best up-to-date Mon Ey content for Japan and also check out these interesting facts you probably never knew about mon-ey.jp
「門衛」は、各業界の専門家が当サイト用に執筆したオリジナルの記事を厳選し、掲載している情報サイトです。
Visit mon-ey.jpWe analyzed Mon-ey.jp page load time and found that the first response time was 4.3 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
mon-ey.jp performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value4.6 s
34/100
25%
Value6.7 s
36/100
10%
Value50 ms
100/100
30%
Value0
100/100
15%
Value7.1 s
52/100
10%
4328 ms
380 ms
1099 ms
39 ms
2096 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 46% of them (45 requests) were addressed to the original Mon-ey.jp, 22% (21 requests) were made to Static.xx.fbcdn.net and 12% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Mon-ey.jp.
Page size can be reduced by 174.2 kB (25%)
707.3 kB
533.0 kB
In fact, the total size of Mon-ey.jp main page is 707.3 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. 55% of websites need less resources to load. Images take 528.5 kB which makes up the majority of the site volume.
Potential reduce by 25.3 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 25.3 kB or 74% of the original size.
Potential reduce by 75.3 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. Obviously, Mon Ey needs image optimization as it can save up to 75.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 29.0 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 29.0 kB or 31% of the original size.
Potential reduce by 44.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. Mon-ey.jp needs all CSS files to be minified and compressed as it can save up to 44.6 kB or 87% of the original size.
Number of requests can be reduced by 38 (40%)
96
58
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mon Ey. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
mon-ey.jp
4328 ms
import.css
380 ms
top.css
1099 ms
jquery.min.js
39 ms
script.js
2096 ms
smoothscroll.js
415 ms
bookmark_button.js
438 ms
ga.js
2123 ms
reset.css
196 ms
common.css
2479 ms
jquery.bxslider.css
263 ms
widgets.js
131 ms
analytics.js
121 ms
logo.gif
229 ms
top_gnavi_search_btn.jpg
384 ms
top_lead01.gif
225 ms
160219074.jpg
644 ms
160219066.jpg
265 ms
160219143.jpg
398 ms
160219089.jpg
574 ms
160219142.jpg
639 ms
160219021.jpg
424 ms
160219001.jpg
762 ms
160219084.jpg
779 ms
160219061.jpg
638 ms
160219063.jpg
928 ms
160219058.jpg
1260 ms
160219087.jpg
1262 ms
footer_logo.gif
856 ms
sdk.js
119 ms
head_bg01.gif
1003 ms
head_icon01.gif
1004 ms
top_view_bg01.gif
1146 ms
top_view_bg02.gif
1151 ms
top_gnavi_line.gif
1212 ms
top_gnavi_off.gif
1216 ms
top_gnavi_search.jpg
1215 ms
top_title_bg01.gif
1215 ms
com_rankicon01.jpg
1215 ms
com_rankicon02.jpg
1216 ms
com_rankicon03.jpg
1317 ms
com_rankicon04.jpg
1348 ms
com_rankicon05.jpg
1318 ms
com_rankicon06.jpg
1352 ms
com_rankicon07.jpg
1352 ms
com_rankicon08.jpg
1330 ms
com_rankicon09.jpg
1480 ms
com_rankicon10.jpg
1477 ms
pagetop01.gif
1491 ms
footer_icon01.gif
1517 ms
linkid.js
86 ms
plusone.js
226 ms
176 ms
collect
50 ms
collect
210 ms
xd_arbiter.php
148 ms
xd_arbiter.php
221 ms
page.php
295 ms
cb=gapi.loaded_0
62 ms
N5keFt2bFAu.css
131 ms
NRhzQHyZYbs.css
167 ms
MKiDk2JIhZf.css
208 ms
XCdv7aD40Gm.js
293 ms
IGjVwCaq5H5.js
333 ms
nw0sMxy_KfY.js
264 ms
hNf_FhaQk_d.js
239 ms
In4aku49oAV.js
377 ms
995951_536133403101227_399119628_n.jpg
306 ms
safe_image.php
379 ms
safe_image.php
343 ms
safe_image.php
313 ms
safe_image.php
476 ms
safe_image.php
328 ms
11209722_636093869865503_3388756331809217963_n.jpg
268 ms
10614336_557800210986816_3928503023882403621_n.jpg
271 ms
521968_1378818835679075_1166773631_n.jpg
269 ms
11218887_1627467830859310_1613885265527087219_n.jpg
282 ms
10354686_10150004552801856_220367501106153455_n.jpg
275 ms
148332_161106523926055_1749485_n.jpg
281 ms
11224372_924686740947051_54409021774148886_n.jpg
280 ms
12115827_954538117987148_7331212129203548347_n.jpg
281 ms
1509018_10202018078161745_1840292068_n.jpg
279 ms
11796328_836234939817415_4724402015162256074_n.jpg
311 ms
10616567_440754602733396_2708657327939014901_n.jpg
279 ms
wL6VQj7Ab77.png
253 ms
WTZ_Jhk-ooC.png
250 ms
mbF8ssTVP_5.png
251 ms
Fe6g47SXw-8.png
252 ms
L5AOQ9vzKfo.png
251 ms
oULnqcel5Nm.png
250 ms
q2ibvFgTxmh.png
269 ms
A2JLtDOGyCJ.png
268 ms
Qo6jLTrNZQ5.js
59 ms
R9GKCzjAnbk.js
12 ms
AWWjhOengNF.js
11 ms
YnSasnyq68i.js
16 ms
kQf_jlUv-kX.js
10 ms
mon-ey.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.
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.
mon-ey.jp 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
mon-ey.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Mon-ey.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 Mon-ey.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.
mon-ey.jp
Open Graph data is detected on the main page of Mon Ey. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: