8 sec in total
1000 ms
6.6 sec
421 ms
Click here to check amazing Megahouse content for Japan. Otherwise, check out these important facts you probably never knew about megahouse.co.jp
株式会社メガハウスの公式サイトです。商品情報や会社情報などを掲載しています。
Visit megahouse.co.jpWe analyzed Megahouse.co.jp page load time and found that the first response time was 1000 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
megahouse.co.jp performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value8.3 s
2/100
25%
Value8.4 s
18/100
10%
Value30 ms
100/100
30%
Value0.509
16/100
15%
Value7.6 s
47/100
10%
1000 ms
342 ms
692 ms
530 ms
1057 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 87% of them (85 requests) were addressed to the original Megahouse.co.jp, 11% (11 requests) were made to Bandainamco.co.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Megahouse.co.jp.
Page size can be reduced by 283.0 kB (11%)
2.6 MB
2.3 MB
In fact, the total size of Megahouse.co.jp main page is 2.6 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 32.4 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 32.4 kB or 73% of the original size.
Potential reduce by 49.4 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. Megahouse images are well optimized though.
Potential reduce by 166.1 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 166.1 kB or 66% of the original size.
Potential reduce by 35.0 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. Megahouse.co.jp needs all CSS files to be minified and compressed as it can save up to 35.0 kB or 83% of the original size.
Number of requests can be reduced by 28 (29%)
97
69
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Megahouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
megahouse.co.jp
1000 ms
import.css
342 ms
megahouse_common.css
692 ms
top.css
530 ms
jquery.js
1057 ms
jquery.biggerlink.js
545 ms
jquery.corner.js
679 ms
common.js
686 ms
jquery.min.js
1413 ms
chili-1.7.pack.js
909 ms
jquery.cycle.all.2.72.js
1354 ms
heightLine.js
1030 ms
jquery.readmore.js
863 ms
header.js
927 ms
cmn_reset.css
698 ms
cmn_layout.css
753 ms
cmn_style.css
1036 ms
categoryBorderColor.css
872 ms
categoryIconColor.css
891 ms
footer.js
447 ms
ga.js
90 ms
bg_ft_yellow.gif
175 ms
img_hd_logo.gif
180 ms
btn_hd_search.gif
176 ms
56b45d63c9a5f.jpg
705 ms
56b08556bb2a9.jpg
947 ms
56b08660ec939.jpg
1016 ms
566a419137603.jpg
2073 ms
562ed988474d0.jpg
1383 ms
55fb8d1ddb1a1.jpg
885 ms
title_site_information.jpg
883 ms
btn_mhtop_megahobby.jpg
1059 ms
btn_mhtop_megatoy.jpg
1239 ms
btn_mhtop_megatrea.jpg
1129 ms
h2_top_01.gif
1186 ms
btn_top_01.gif
1237 ms
h2_top_02.gif
1313 ms
h2_top_03.gif
1356 ms
56cad86a9e874.jpg
1414 ms
56cad88192a2b.gif
1418 ms
56ce6f119d75c.png
1856 ms
56ce6f1913c96.gif
1526 ms
56cad7102e200.jpg
1555 ms
56cad73eea42b.gif
1591 ms
56ca7426b5af3.jpg
1770 ms
56c683fa1f619.gif
1696 ms
56b0649a25670.jpg
1729 ms
56b064c0a3031.gif
1767 ms
btn_top_02.gif
2034 ms
h2_top_04.gif
1902 ms
5639ac873b3c8.jpg
2821 ms
5639ac94f2a07.gif
1948 ms
56162fc184338.jpg
2581 ms
56162fd6974fb.gif
2076 ms
55f8d2fc9cd5b.jpg
2516 ms
55f8d346b4bf8.gif
2204 ms
55b42a8cd3d80.jpg
2578 ms
AC_RunActiveContent.js
322 ms
DynamicFlashStage.js
324 ms
swfobject.js
325 ms
__utm.gif
11 ms
logo.png
379 ms
btnTH.png
379 ms
btnNE.png
380 ms
btnVM.png
626 ms
btnAF.png
634 ms
btn_top_03.gif
2251 ms
img_ft_logo01.gif
2203 ms
tit_ft_01.png
2370 ms
footer_bg.jpg
676 ms
img_ft_logo02.png
1896 ms
icon_hd_arrow.gif
1816 ms
bg_hd_textarea.gif
1834 ms
gnavi.jpg
3310 ms
bg_contents.gif
1751 ms
box_infoBg_03.gif
1714 ms
box_infoBg_02.gif
1747 ms
box_infoBg_01.gif
1702 ms
icn_top_01.gif
1703 ms
icn_top_02.gif
1709 ms
icn_top_03.gif
1689 ms
bg_box_01_body.gif
1698 ms
bg_box_01_header.gif
1678 ms
bg_box_01_footer.gif
1699 ms
bg_box_02_body.gif
1703 ms
bg_box_02_header.gif
1651 ms
bg_box_02_footer.gif
1677 ms
bg_ft_blue_s.jpg
1638 ms
bg_ft_blue.jpg
2969 ms
bg_ft_bt.png
1566 ms
btn_hd_search_on.gif
1588 ms
btn_mhtop_megahobby_on.jpg
1966 ms
btn_mhtop_megatoy_on.jpg
1906 ms
btn_mhtop_megatrea_on.jpg
1909 ms
btn_top_01_on.gif
1584 ms
btn_top_02_on.gif
1676 ms
btn_top_03_on.gif
1816 ms
icn_top_04.gif
1831 ms
megahouse.co.jp 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-hidden="true"] elements contain focusable descendents
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
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.
megahouse.co.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
megahouse.co.jp 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Megahouse.co.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 Megahouse.co.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.
megahouse.co.jp
Open Graph description is not detected on the main page of Megahouse. 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: