8.9 sec in total
551 ms
7.6 sec
844 ms
Click here to check amazing 4 Mini content for Japan. Otherwise, check out these important facts you probably never knew about 4-mini.net
モンキーのカスタム応援サイト
Visit 4-mini.netWe analyzed 4-mini.net page load time and found that the first response time was 551 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
4-mini.net performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value23.1 s
0/100
25%
Value13.4 s
2/100
10%
Value4,790 ms
0/100
30%
Value0.699
7/100
15%
Value21.0 s
1/100
10%
551 ms
176 ms
1257 ms
1023 ms
518 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 80% of them (44 requests) were addressed to the original 4-mini.net, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain 4-mini.net.
Page size can be reduced by 245.5 kB (11%)
2.2 MB
2.0 MB
In fact, the total size of 4-mini.net main page is 2.2 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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 133.5 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 133.5 kB or 82% of the original size.
Potential reduce by 3.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. 4 Mini images are well optimized though.
Potential reduce by 15.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 93.5 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. 4-mini.net needs all CSS files to be minified and compressed as it can save up to 93.5 kB or 64% of the original size.
Number of requests can be reduced by 36 (73%)
49
13
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4 Mini. 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 15 to 1 for CSS and as a result speed up the page load time.
4-mini.net
551 ms
custom
176 ms
1257 ms
style.min.css
1023 ms
styles.css
518 ms
style.css
523 ms
style.css
867 ms
wpp.css
527 ms
style.css
858 ms
style.css
691 ms
shortcode.css
696 ms
css
48 ms
css
65 ms
font-awesome.min.css
49 ms
slick.min.css
704 ms
font-awesome.min.css
1036 ms
jquery.min.js
32 ms
wpp.min.js
869 ms
adsbygoogle.js
173 ms
amp-auto-ads-0.1.js
33 ms
vertical.css
880 ms
animate.css
522 ms
index.js
614 ms
index.js
613 ms
imagesloaded.min.js
614 ms
masonry.min.js
768 ms
jquery.masonry.min.js
768 ms
rsvp.js
769 ms
scripts.js
768 ms
modernizr.custom.min.js
769 ms
slick.min.js
915 ms
jquery.sonar.min.js
913 ms
lazy-load.js
914 ms
no-right-click-images-frontend.js
913 ms
api.js
35 ms
wp-polyfill-inert.min.js
913 ms
regenerator-runtime.min.js
914 ms
wp-polyfill.min.js
1043 ms
index.js
1042 ms
toggle.js
1063 ms
a97b4cbe0b70ed7b3ff17b65ff6fb3ee.jpg
561 ms
440px.jpg
861 ms
1x1.trans.gif
573 ms
noimg.png
647 ms
side_banner01.jpg
664 ms
c18e694248f3436b0f374dda382717bc.jpg
861 ms
d444609e917156c591c13ccedadbeb15.jpg
4199 ms
shadow1.png
609 ms
font
66 ms
font
66 ms
fontawesome-webfont.woff
607 ms
fontawesome-webfont.woff
65 ms
recaptcha__en.js
80 ms
2180423-monkey125_006H-360x230.jpg
289 ms
tb.-360x230.jpg
305 ms
4-mini.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
4-mini.net 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
4-mini.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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 4-mini.net 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 4-mini.net 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.
4-mini.net
Open Graph data is detected on the main page of 4 Mini. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: