Tools & Wizards About Us
mosimon.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mosimon.co.jp

株式会社あなたの幸せが私の幸せ

Page Load Speed

7 sec in total

First Response

1.4 sec

Resources Loaded

5.3 sec

Page Rendered

250 ms

mosimon.co.jp screenshot

About Website

Welcome to mosimon.co.jp homepage info - get ready to check Mosimon best content for Japan right away, or after learning these important things about mosimon.co.jp

もしもんは関東全域を中心に、個人様向けの各携帯電話ショップや法人様向けにドコモ、au、ソフトバンク、ウィルコム、ワイモバイルの法人携帯電話とデータ通信端末を取り扱っております。相見積も承ります。

Visit mosimon.co.jp

Key Findings

We analyzed Mosimon.co.jp page load time and found that the first response time was 1.4 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

mosimon.co.jp performance score

0

Network Requests Diagram

mosimon.co.jp

1427 ms

cache-1449627555-01b9cec2243b4152635b47c8e3d4830b.css

1287 ms

custom_css_path_5180cd8280790.css

394 ms

jquery-1.7.2.min.js

1280 ms

jquery.upload.1.0.2.js

354 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 21% of them (10 requests) were addressed to the original Mosimon.co.jp, 69% (33 requests) were made to All-in-one-cms.s3-ap-northeast-1.amazonaws.com and 4% (2 requests) were made to Analytics.sitefarm04.info. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Mosimon.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 503.5 kB (37%)

Content Size

1.4 MB

After Optimization

850.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mosimon.co.jp main page is 1.4 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. 25% of websites need less resources to load. Images take 690.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 14.5 kB

  • Original 20.0 kB
  • After minification 18.9 kB
  • After compression 5.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 14.5 kB or 72% of the original size.

Image Optimization

-4%

Potential reduce by 27.1 kB

  • Original 690.0 kB
  • After minification 662.9 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. Mosimon images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 388.8 kB

  • Original 558.5 kB
  • After minification 556.4 kB
  • After compression 169.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 388.8 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 73.1 kB

  • Original 85.1 kB
  • After minification 66.5 kB
  • After compression 11.9 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. Mosimon.co.jp needs all CSS files to be minified and compressed as it can save up to 73.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (21%)

Requests Now

47

After Optimization

37

  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mosimon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

mosimon.co.jp

mosimon.co.jp

1427 ms

cache-1449627555-01b9cec2243b4152635b47c8e3d4830b.css

cache-1449627555-01b9cec2243b4152635b47c8e3d4830b.css

1287 ms

custom_css_path_5180cd8280790.css

custom_css_path_5180cd8280790.css

394 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1280 ms

jquery.upload.1.0.2.js

jquery.upload.1.0.2.js

354 ms

cache-1457352271-96c0b5f73c12b138c3954368a27bf498.js

cache-1457352271-96c0b5f73c12b138c3954368a27bf498.js

2055 ms

widget.js

widget.js

57 ms

pc_banner_55063ec0611f4.png

pc_banner_55063ec0611f4.png

485 ms

close.png

close.png

341 ms

loading.gif

loading.gif

530 ms

prev.png

prev.png

365 ms

next.png

next.png

366 ms

bf88ffefda3c43f0bb4d28cb408f596f.jpg

bf88ffefda3c43f0bb4d28cb408f596f.jpg

562 ms

banner_path_52e0e62c07589.png

banner_path_52e0e62c07589.png

326 ms

img_path_53e1f719f1d99.png

img_path_53e1f719f1d99.png

1193 ms

banner_file506a84fea18a8.png

banner_file506a84fea18a8.png

325 ms

banner_file4e522ab44dcbd.png

banner_file4e522ab44dcbd.png

347 ms

banner_file4e24f9ac9e254.jpg

banner_file4e24f9ac9e254.jpg

473 ms

top_banner_1348803200.png

top_banner_1348803200.png

803 ms

top_banner_1348803281.png

top_banner_1348803281.png

708 ms

img_path_551e049319d39.png

img_path_551e049319d39.png

1145 ms

img_path_55434954e300b.png

img_path_55434954e300b.png

1396 ms

ibent.PNG

ibent.PNG

813 ms

top_banner_1311045677.jpg

top_banner_1311045677.jpg

1033 ms

10580015_05_100_JP.gif

10580015_05_100_JP.gif

992 ms

090831_ciesf1_R.PNG

090831_ciesf1_R.PNG

982 ms

top_banner_1331777012.gif

top_banner_1331777012.gif

1163 ms

banner_1311045945.jpg

banner_1311045945.jpg

1163 ms

banner_1311045932.jpg

banner_1311045932.jpg

1239 ms

banner_1311045918.jpg

banner_1311045918.jpg

1333 ms

banner_1330400844.jpg

banner_1330400844.jpg

1351 ms

banner_1311045899.jpg

banner_1311045899.jpg

1347 ms

copyright_img_file4e24f75d7bbe6.jpg

copyright_img_file4e24f75d7bbe6.jpg

1389 ms

img_off_file5008b85b59e85.jpg

img_off_file5008b85b59e85.jpg

1426 ms

img_off_file501f7a46eb7f8.jpg

img_off_file501f7a46eb7f8.jpg

1496 ms

img_off_file4e24fa95cf0f8.jpg

img_off_file4e24fa95cf0f8.jpg

1544 ms

img_off_file4e27b3ba41342.jpg

img_off_file4e27b3ba41342.jpg

1508 ms

img_off_file4f5eff77ee9b7.png

img_off_file4f5eff77ee9b7.png

1572 ms

img_off_file5008bbd12a88b.jpg

img_off_file5008bbd12a88b.jpg

1571 ms

analytics.js

analytics.js

647 ms

omatome.jpg

omatome.jpg

1578 ms

analytics

analytics

377 ms

ga.js

ga.js

19 ms

__utm.gif

__utm.gif

11 ms

banner_file4e522785955ba.jpg

banner_file4e522785955ba.jpg

652 ms

wakutin.PNG

wakutin.PNG

632 ms

banner_file4e52279e4a69e.gif

banner_file4e52279e4a69e.gif

634 ms

banner_file4e5227a742d90.gif

banner_file4e5227a742d90.gif

626 ms

SEO Factors

mosimon.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mosimon.co.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 Mosimon.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.

Social Sharing Optimization

mosimon.co.jp

Open Graph description is not detected on the main page of Mosimon. 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: