Tools & Wizards About Us
mobileplus.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mobileplus.jp

モバイル事業 | ホームページ制作会社マーケティングプラス

Page Load Speed

9.1 sec in total

First Response

2.1 sec

Resources Loaded

6.6 sec

Page Rendered

417 ms

mobileplus.jp screenshot

About Website

Welcome to mobileplus.jp homepage info - get ready to check Mobileplus best content right away, or after learning these important things about mobileplus.jp

ホームページ制作会社のマーケティングプラス。東京-渋谷、名古屋。ホームページ 制作料金プラン（Web作成・リニューアル更新の料金見積もり）、サイト作成実績や SEO、スマホサイト制作。03-5456-4704

Visit mobileplus.jp

Key Findings

We analyzed Mobileplus.jp page load time and found that the first response time was 2.1 sec 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.

Performance Metrics

mobileplus.jp performance score

0

Network Requests Diagram

2144 ms

style.css

338 ms

jquery-1.9.1.min.js

1631 ms

sm_scroll.js

358 ms

rollover.js

365 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mobileplus.jp, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Plusline.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 444.6 kB (64%)

Content Size

691.4 kB

After Optimization

246.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 26.9 kB

  • Original 34.6 kB
  • After minification 30.4 kB
  • After compression 7.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 4.1 kB, which is 12% 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 26.9 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 9.0 kB

  • Original 89.9 kB
  • After minification 80.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. Mobileplus images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 250.8 kB

  • Original 379.8 kB
  • After minification 343.2 kB
  • After compression 129.0 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 250.8 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 157.9 kB

  • Original 187.1 kB
  • After minification 153.1 kB
  • After compression 29.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. Mobileplus.jp needs all CSS files to be minified and compressed as it can save up to 157.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (53%)

Requests Now

47

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2144 ms

style.css

style.css

338 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

1631 ms

sm_scroll.js

sm_scroll.js

358 ms

rollover.js

rollover.js

365 ms

heightLine.js

heightLine.js

568 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

836 ms

bootstrap.js

bootstrap.js

1400 ms

jquery.slides.min.js

jquery.slides.min.js

916 ms

styles.css

styles.css

549 ms

pagenavi-css.css

pagenavi-css.css

580 ms

lightbox.min.css

lightbox.min.css

733 ms

jquery.js

jquery.js

1751 ms

bootstrap.css

bootstrap.css

1671 ms

reset.css

reset.css

762 ms

common.css

common.css

1120 ms

layout.css

layout.css

945 ms

lightbox.min.css

lightbox.min.css

1129 ms

mobile.css

mobile.css

1244 ms

jquery.form.js

jquery.form.js

1281 ms

scripts.js

scripts.js

1108 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

1218 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

1569 ms

analytics.js

analytics.js

49 ms

bg_body.gif

bg_body.gif

919 ms

spritesheet.png

spritesheet.png

366 ms

il01.png

il01.png

192 ms

il02.png

il02.png

180 ms

menu_icon.jpg

menu_icon.jpg

179 ms

tel_icon.jpg

tel_icon.jpg

168 ms

il03.png

il03.png

336 ms

img_logo.png

img_logo.png

356 ms

ico_sitemap.png

ico_sitemap.png

358 ms

all.js

all.js

270 ms

bg_gnavi.gif

bg_gnavi.gif

358 ms

bg_glovalnavi.gif

bg_glovalnavi.gif

483 ms

bg_footer.png

bg_footer.png

511 ms

bg_sitemap.jpg

bg_sitemap.jpg

870 ms

ico_nw.gif

ico_nw.gif

526 ms

collect

collect

18 ms

95 ms

xd_arbiter.php

xd_arbiter.php

222 ms

xd_arbiter.php

xd_arbiter.php

429 ms

pta.js

pta.js

482 ms

like.php

like.php

99 ms

wy1X4hBW7e7.js

wy1X4hBW7e7.js

487 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

552 ms

7ff5c0ca.js

7ff5c0ca.js

788 ms

SEO Factors

mobileplus.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

mobileplus.jp

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