9.4 sec in total
976 ms
8.1 sec
395 ms
Visit m-78.jp now to see the best up-to-date M 78 content for Japan and also check out these interesting facts you probably never knew about m-78.jp
ウルトラマンシリーズを中心とする円谷プロ作品の最新情報をチェック!
Visit m-78.jpWe analyzed M-78.jp page load time and found that the first response time was 976 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
m-78.jp performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value6.4 s
9/100
25%
Value7.6 s
25/100
10%
Value5,610 ms
0/100
30%
Value0.04
99/100
15%
Value13.9 s
10/100
10%
976 ms
923 ms
347 ms
880 ms
1238 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 71% of them (80 requests) were addressed to the original M-78.jp, 9% (10 requests) were made to Static.xx.fbcdn.net and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain M-78.jp.
Page size can be reduced by 745.1 kB (25%)
2.9 MB
2.2 MB
In fact, the total size of M-78.jp main page is 2.9 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. 50% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 46.7 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 6.6 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 46.7 kB or 79% of the original size.
Potential reduce by 152.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. M 78 images are well optimized though.
Potential reduce by 244.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 244.5 kB or 56% of the original size.
Potential reduce by 301.1 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. M-78.jp needs all CSS files to be minified and compressed as it can save up to 301.1 kB or 85% of the original size.
Number of requests can be reduced by 28 (25%)
110
82
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M 78. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
m-78.jp
976 ms
style.css
923 ms
twitter-feed.css
347 ms
animate.min.css
880 ms
jquery.js
1238 ms
jquery-migrate.min.js
361 ms
public.min.js
324 ms
jquery.min.js
32 ms
jquery.easing.1.3.js
341 ms
jquery.bxSlider.min.js
547 ms
common.js
671 ms
hero.js
672 ms
s_retargeting.js
580 ms
ga.js
114 ms
th_0c9e40fa455a30287507d73d877db9ea_1449465656movie2016.png
686 ms
th_fa76374fe51f1a1744fb02f1a995184c_1449465647movie2016main.jpg
1107 ms
th_0c9e40fa455a30287507d73d877db9ea_1372682866uldenlogo.PNG
636 ms
th_fa76374fe51f1a1744fb02f1a995184c_1396854941NUR_201404banner2.jpg
990 ms
th_0c9e40fa455a30287507d73d877db9ea_1365676686toptfclogo.png
671 ms
th_fa76374fe51f1a1744fb02f1a995184c_1433148717tfctop.jpg
774 ms
side-title1.png
945 ms
side-title2.png
1015 ms
side-title3.png
1027 ms
side-title4.png
1152 ms
side-title5.png
1274 ms
side-title6.png
1315 ms
banner01.jpg
1779 ms
facebook2.jpg
1386 ms
ultraman-kikin.png
1762 ms
ultra-50.jpg
3308 ms
news-icon-mobile.jpg
1769 ms
news-icon-goods.jpg
1635 ms
news-icon-event.jpg
1741 ms
news-icon-stores.jpg
2157 ms
news-icon-streaming.jpg
2087 ms
recommend.png
2123 ms
sukagawa-hikari.jpg
2503 ms
ultramangaia_banner_100x80.jpg
2502 ms
banner_kaettekita-kaiju-sakaba.jpg
2395 ms
ganso.jpg
2642 ms
a-man-of-ultra.jpg
2649 ms
ultraman_banner.jpg
2707 ms
TCJ_logo.jpg
2864 ms
tfc.jpg
3265 ms
foot-chara002.png
3003 ms
foot-chara001.png
3011 ms
foot-title1.jpg
3016 ms
foot-title2.jpg
3235 ms
foot-title3.jpg
3334 ms
sdk.js
168 ms
foot-title4.jpg
3524 ms
widgets.js
36 ms
bi.js
511 ms
2KRMeNjPm48
104 ms
4zIGWylZXfI
153 ms
inpage_linkid.js
18 ms
likebox.php
217 ms
__utm.gif
19 ms
145 ms
xd_arbiter.php
151 ms
xd_arbiter.php
274 ms
www-embed-player-vflZsBgOl.css
71 ms
www-embed-player.js
97 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
38 ms
ad_status.js
80 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
33 ms
jTuqQ-OPDr6.css
177 ms
n370yiaI2G6.css
214 ms
_rx8naC75Dy.js
287 ms
x5F9OMjKyLw.js
370 ms
ICDbTSzjQEg.js
309 ms
TTCre3391I0.js
308 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
78 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
81 ms
359 ms
foot-title5.jpg
2756 ms
foot-title6.jpg
3070 ms
tca_pc.jpg
4785 ms
421228_384020861610925_917495676_n.jpg
31 ms
wL6VQj7Ab77.png
38 ms
s7jcwEQH7Sx.png
40 ms
navbg.jpg
2901 ms
I6-MnjEovm5.js
39 ms
vlXaquuXMrr.js
42 ms
logo-main.png
2734 ms
logo-main.jpg
2729 ms
houjin.jpg
2923 ms
mainnav.png
3299 ms
main-bg.jpg
4151 ms
dot.gif
2925 ms
front-btn.png
2815 ms
side-bg.jpg
2986 ms
side-nav1.png
3013 ms
side-nav2.png
2801 ms
side-nav3.png
2892 ms
side-nav3-2.png
2928 ms
side-nav4.png
2953 ms
side-nav5.png
3013 ms
side-nav6.png
2896 ms
side-nav6-2.png
2897 ms
side-nav6-1.png
2912 ms
pickup-bg.jpg
3234 ms
btn-detail.png
2838 ms
section-bg1.jpg
3104 ms
title-top1.png
2748 ms
newslist-btn.png
2947 ms
title-top2.png
2952 ms
foot-bg.jpg
3344 ms
foot-arrow.jpg
2789 ms
foot-nav.jpg
3275 ms
page-top.png
2935 ms
close.png
2769 ms
front-arrow.png
2724 ms
m-78.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
Image elements do not have [alt] attributes
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.
m-78.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
m-78.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 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 M-78.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 M-78.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.
m-78.jp
Open Graph data is detected on the main page of M 78. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: