8.4 sec in total
1.5 sec
6.4 sec
473 ms
Click here to check amazing Minmin content for Japan. Otherwise, check out these important facts you probably never knew about minmin.org
詳しくはこちらをご覧ください
Visit minmin.orgWe analyzed Minmin.org page load time and found that the first response time was 1.5 sec 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.
minmin.org performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value4.1 s
46/100
25%
Value18.6 s
0/100
10%
Value7,340 ms
0/100
30%
Value0.08
94/100
15%
Value28.3 s
0/100
10%
1526 ms
873 ms
358 ms
363 ms
370 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 54% of them (65 requests) were addressed to the original Minmin.org, 14% (17 requests) were made to Apis.google.com and 6% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Minmin.org.
Page size can be reduced by 480.4 kB (62%)
777.8 kB
297.4 kB
In fact, the total size of Minmin.org main page is 777.8 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. 65% of websites need less resources to load. Javascripts take 397.1 kB which makes up the majority of the site volume.
Potential reduce by 62.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. This page needs HTML code to be minified as it can gain 7.9 kB, which is 11% 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 62.3 kB or 84% of the original size.
Potential reduce by 28.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, Minmin needs image optimization as it can save up to 28.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 262.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 262.5 kB or 66% of the original size.
Potential reduce by 127.3 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. Minmin.org needs all CSS files to be minified and compressed as it can save up to 127.3 kB or 82% of the original size.
Number of requests can be reduced by 60 (51%)
117
57
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Minmin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.minmin.org
1526 ms
foundation.css
873 ms
app.css
358 ms
ie.css
363 ms
shortcode.css
370 ms
elements.css
754 ms
style.css
889 ms
red.css
540 ms
styles.css
552 ms
default.min.css
834 ms
jquery.js
1616 ms
jquery-migrate.min.js
920 ms
jquery.orbit.js
1318 ms
app.js
1002 ms
jquery.placeholder.min.js
1041 ms
jquery.reveal.js
1063 ms
jquery.tooltips.js
1287 ms
modernizr.foundation.js
1338 ms
menu.js
1215 ms
plusone.js
1241 ms
oembed-twitter.js
1389 ms
mobilemenu.js
1263 ms
video.js
1315 ms
jquery.easing.1.3.js
1538 ms
jquery.elastislide.js
1517 ms
jquery.nivo.slider.js
1406 ms
jquery.lightbox-0.5.js
1616 ms
jquery.form.min.js
1542 ms
scripts.js
1622 ms
core.min.js
1304 ms
widget.min.js
1353 ms
tabs.min.js
1594 ms
wp-embed.min.js
1458 ms
wp-emoji-release.min.js
1640 ms
plusone.js
63 ms
cb=gapi.loaded_0
4 ms
ga.js
21 ms
noise.jpg
230 ms
000.gif
700 ms
twitter.png
397 ms
googlemaps.png
439 ms
rss.png
535 ms
home.png
518 ms
magnify.png
607 ms
spinner.gif
635 ms
NPO%E6%83%85%E5%A0%B1%E3%83%A9%E3%82%A4%E3%83%96%E3%83%A9%E3%83%AA.jpg
1861 ms
%E3%82%BB%E3%83%9F%E3%83%8A%E3%83%BC%E8%AC%9B%E5%B8%AB%E6%B4%BE%E9%81%A31.jpg
1665 ms
0041.jpg
2097 ms
default.png
892 ms
facebook.png
894 ms
twitter.png
940 ms
reddit.png
990 ms
linkedin.png
1143 ms
Commentsgrey.png
1144 ms
bn_kokurenbousai.jpg
1572 ms
rss.png
1262 ms
bn_kessai_minmin.jpg
1654 ms
flasco.gif
1617 ms
library1.gif
2125 ms
minmindou1.gif
1973 ms
sensapo1.gif
2013 ms
tagasapo.gif
1854 ms
sss1.gif
2420 ms
bn_fb.gif
2035 ms
widgets.js
80 ms
__utm.gif
13 ms
embed
48 ms
like.php
156 ms
embed
102 ms
like.php
152 ms
like.php
171 ms
like.php
150 ms
like.php
159 ms
like.php
137 ms
0992f33945a94632a64d2587cfa6f814embedcompiled_fastui.css
4 ms
0992f33945a94632a64d2587cfa6f814embedcompiled__en.js
9 ms
client.js
40 ms
qeKvIRsJabD.js
52 ms
LVx-xkvaJ0b.png
45 ms
cb=gapi.loaded_0
32 ms
postmessageRelay
66 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
260 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
263 ms
cb=gapi.loaded_1
29 ms
fastbutton
158 ms
fastbutton
87 ms
fastbutton
121 ms
fastbutton
86 ms
fastbutton
80 ms
fastbutton
143 ms
arrow.png
1784 ms
postmessageRelay
45 ms
3193398744-postmessagerelay.js
53 ms
rpc:shindig_random.js
142 ms
rs=AGLTcCMnDeXbzq1T_DzqIKnxZkbM5OL1-w
7 ms
cb=gapi.loaded_0
59 ms
cb=gapi.loaded_1
30 ms
xZQOmYg4x3YaWkTJi1kErvesZW2xOQ-xsNqO47m55DA.woff
81 ms
cb=gapi.loaded_0
5 ms
logo-plus.png
41 ms
googlelogo_color_46x16dp.png
68 ms
proxy.html
58 ms
menu_arrow_open.gif
31 ms
syndication
124 ms
423626900083208192
262 ms
cb=gapi.loaded_0
22 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
72 ms
events
64 ms
proxy.jpg
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
28 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
52 ms
09_minminbird_logo_normal.JPG
237 ms
EBd5sR8V_normal.jpg
305 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
22 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
116 ms
proxy.jpg
14 ms
jot.html
27 ms
right-arrow.png
171 ms
left-arrow.png
191 ms
bullets2.png
187 ms
minmin.org 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
minmin.org 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
minmin.org SEO score
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Minmin.org 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 Minmin.org 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.
minmin.org
Open Graph description is not detected on the main page of Minmin. 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: