4.8 sec in total
516 ms
4.2 sec
84 ms
Visit mokuzu120.booth.pm now to see the best up-to-date Mokuzu 120 BOOTH content for Japan and also check out these interesting facts you probably never knew about mokuzu120.booth.pm
サークル名はA4サイズですが、B5です。
Visit mokuzu120.booth.pmWe analyzed Mokuzu120.booth.pm page load time and found that the first response time was 516 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mokuzu120.booth.pm performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value11.1 s
0/100
25%
Value8.6 s
17/100
10%
Value1,540 ms
13/100
30%
Value0.523
15/100
15%
Value14.8 s
8/100
10%
516 ms
967 ms
1000 ms
1656 ms
23 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Mokuzu120.booth.pm, 32% (9 requests) were made to Asset.booth.pm and 14% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Asset.booth.pm.
Page size can be reduced by 439.3 kB (67%)
651.6 kB
212.3 kB
In fact, the total size of Mokuzu120.booth.pm main page is 651.6 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. 30% of websites need less resources to load. Javascripts take 497.9 kB which makes up the majority of the site volume.
Potential reduce by 14.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 14.3 kB or 73% of the original size.
Potential reduce by 0 B
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. Mokuzu 120 BOOTH images are well optimized though.
Potential reduce by 321.7 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 321.7 kB or 65% of the original size.
Potential reduce by 103.2 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. Mokuzu120.booth.pm needs all CSS files to be minified and compressed as it can save up to 103.2 kB or 81% of the original size.
Number of requests can be reduced by 12 (50%)
24
12
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mokuzu 120 BOOTH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
mokuzu120.booth.pm
516 ms
mokuzu120.booth.pm
967 ms
application-3272d462e31d839eb41be82d2c1bbcaa.css
1000 ms
main-e8d5c254e23be598d68ca0c35091ff6b.js
1656 ms
widgets.js
23 ms
google_analytics-13af1ac30455b616b81e45ac5e86c7b9.js
891 ms
google_tag_manager-ffbebaa14640dbffe235320264d79fc0.js
916 ms
twitter-80b1d1e046ee8f82100729985b2df919.js
919 ms
analytics.js
58 ms
thumbnail_placeholder_f_150x150-21d6f1e8c141c21efeff0a5ac2144c0d.png
187 ms
thumbnail-alert-146-83a9943dc9004ff6487c5f8d97b2e08a.png
171 ms
gtm.js
104 ms
sdk.js
74 ms
status
882 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
14 ms
booth-logo-under-shop-5a922f76351039a393d4a9ad8408ebba.png
180 ms
booth_font-deeb187ea95ac5966560c14973385ea2.woff
157 ms
linkid.js
16 ms
ec.js
15 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
21 ms
collect
43 ms
collect
59 ms
conversion_async.js
56 ms
s_retargeting.js
904 ms
136 ms
xd_arbiter.php
24 ms
33 ms
39 ms
mokuzu120.booth.pm 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
mokuzu120.booth.pm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mokuzu120.booth.pm SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mokuzu120.booth.pm can be misinterpreted by Google and other search engines. Our service has detected that English 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 Mokuzu120.booth.pm 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.
mokuzu120.booth.pm
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: