12.7 sec in total
1 sec
10 sec
1.7 sec
Visit substance.themedia.jp now to see the best up-to-date Substance Themedia content for Japan and also check out these interesting facts you probably never knew about substance.themedia.jp
substance、グルメ、ラーメン、musicを紹介するブログ
Visit substance.themedia.jpWe analyzed Substance.themedia.jp page load time and found that the first response time was 1 sec and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
substance.themedia.jp performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value17.9 s
0/100
25%
Value13.6 s
2/100
10%
Value420 ms
66/100
30%
Value0.518
15/100
15%
Value16.6 s
5/100
10%
1012 ms
1525 ms
766 ms
1632 ms
790 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Substance.themedia.jp, 50% (29 requests) were made to Static.amebaowndme.com and 22% (13 requests) were made to Cdn.amebaowndme.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Cdn.amebaowndme.com.
Page size can be reduced by 256.0 kB (2%)
11.2 MB
11.0 MB
In fact, the total size of Substance.themedia.jp main page is 11.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. 30% of websites need less resources to load. Images take 10.9 MB which makes up the majority of the site volume.
Potential reduce by 62.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. This page needs HTML code to be minified as it can gain 15.2 kB, which is 21% 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.5 kB or 85% of the original size.
Potential reduce by 11.8 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. Substance Themedia images are well optimized though.
Potential reduce by 72 B
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 181.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. Substance.themedia.jp needs all CSS files to be minified and compressed as it can save up to 181.6 kB or 68% of the original size.
Number of requests can be reduced by 7 (14%)
51
44
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Substance Themedia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
substance.themedia.jp
1012 ms
user-ed5cac6494.min.css
1525 ms
index-d5b0503ba3.min.css
766 ms
public_libs-a1e97b8f79.min.js
1632 ms
index-8a81982e0b.min.js
790 ms
public-ba701d10a1.mdrd.min.js
1690 ms
public-5f94473d87.min.js
2112 ms
analytics.js
49 ms
gtm.js
80 ms
proxy
654 ms
header-96609285b7.html
150 ms
footer-caae6311c7.html
302 ms
collect
46 ms
static-35bf53f5d8.html
259 ms
sprite-1fc0a189e9.png
475 ms
static-400c78cb6d.html
151 ms
%7B%7Bblock.url%7D%7D
160 ms
siteCover-40901e7970.html
248 ms
list-eedd08d67f.html
198 ms
list-e70770367f.html
148 ms
list-75a9bb1384.html
230 ms
list-summary-0b66733693.html
258 ms
list-summary-d3590c4b68.html
262 ms
feed_facebook-04c1da8f4d.html
293 ms
feed_twitter-c27b728e54.html
300 ms
auth-40d1147559.min.js
860 ms
post-summary-c37ca586c2.html
159 ms
post-summary-91dd23b9fe.html
164 ms
post-summary-magazine-ebc52c2e22.html
232 ms
post-summary-full-1e176f9984.html
301 ms
list-l-e63fbd974b.html
518 ms
type_2-a9868b9562.html
584 ms
blogPosts
1520 ms
post-summary-cd69e29ff9.html
615 ms
d8e4c4d1cc8a7f65a4565a9dbe9b0a38_201640478dfe1af179c323f452e350d3.jpg
921 ms
date-314f5c50bf.html
487 ms
%7B%7Bblock.url%7D%7D
379 ms
exchange
156 ms
proxy
303 ms
collect
26 ms
fuse.js
818 ms
collect
61 ms
tracking
344 ms
fb1c45b41822a3d042ee9d0f06f92321_688e6978ee09a1c968c882866333ca92.jpg
1725 ms
b6b8086cfccc1930749e331921ddd34e_ec8eabb0a82b392efd8191953beb5474.jpg
2256 ms
d7cb27eaaa2a64aa336512e711642257_3600f8bdf3e3255826aefeb6f61d3b84.jpg
2106 ms
aa3d180c59b04ecc029e9b40eedb0163_e69f7cba805e3852af27e60eb2c0a2c0.jpg
2810 ms
31bfe2ddf848eaef8be3a5c3e6db4ed2_f31d314af8853fd671b776737370954b.jpg
2272 ms
152f2302c71bf801874a85349c42c7b5_0d6c2a8d79e237ac80db186900566cd3.jpg
2213 ms
c0fecbd23d831da4ebd0d316729aebb8_2eb729e33034e5d6f73d0e204feadec8.jpg
3056 ms
f614dee21d76b9345a5a57449bd49921_6e1a1f4e0609c6b8db6a101461bb580a.jpg
2890 ms
025c5a6c582cdf901f89f91583c5e6ef_a429de12592de24b79e88609ca6e685d.jpg
3047 ms
8af65cdf1be92f44d885bb6baca75383_4beed9e5bab429460c81e150e7c0daa9.jpg
2928 ms
0ecbc51ed6e085d9e78588d7c65f5ebe_ccc5118a032005e99cf8581d1ff22388.jpg
3273 ms
026141d78d58590a57770bcb56cd60cb_34d0bb1671006726a1537503e0bf0f91.jpg
3740 ms
owndicons-0dc0710bba.woff
355 ms
gY5kzIUAAAAAVaAuBYAAA==
14 ms
VEjNLioj
224 ms
substance.themedia.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
Links do not have a discernible name
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.
substance.themedia.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
substance.themedia.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Substance.themedia.jp 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 Substance.themedia.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.
substance.themedia.jp
Open Graph data is detected on the main page of Substance Themedia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: