Tools & Wizards About Us
mobilecommerce.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mobilecommerce.co.jp

mobilecommerce.co.jp – このドメインはお名前.comで取得されています。

Page Load Speed

10.2 sec in total

First Response

584 ms

Resources Loaded

9.1 sec

Page Rendered

587 ms

mobilecommerce.co.jp screenshot

About Website

Welcome to mobilecommerce.co.jp homepage info - get ready to check Mobile Co Mmerce best content right away, or after learning these important things about mobilecommerce.co.jp

モバイル業界16年のノウハウで、お客様のスマートフォンサイトの売上を上げる「サイト改善」をご提案いたします。

Visit mobilecommerce.co.jp

Key Findings

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

Performance Metrics

mobilecommerce.co.jp performance score

0

Network Requests Diagram

mobilecommerce.co.jp

584 ms

style_top.css

323 ms

text.css

368 ms

content.css

370 ms

owl.theme.css

371 ms

Our browser made a total of 149 requests to load all elements on the main page. We found that 98% of them (146 requests) were addressed to the original Mobilecommerce.co.jp, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Mobilecommerce.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.6 kB (22%)

Content Size

956.2 kB

After Optimization

750.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 35.2 kB

  • Original 44.3 kB
  • After minification 41.3 kB
  • After compression 9.2 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 35.2 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 62.5 kB

  • Original 768.4 kB
  • After minification 705.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. Mobile Co Mmerce images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 78.3 kB

  • Original 109.2 kB
  • After minification 72.7 kB
  • After compression 30.9 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 78.3 kB or 72% of the original size.

CSS Optimization

-87%

Potential reduce by 29.7 kB

  • Original 34.3 kB
  • After minification 26.5 kB
  • After compression 4.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. Mobilecommerce.co.jp needs all CSS files to be minified and compressed as it can save up to 29.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (16%)

Requests Now

148

After Optimization

124

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobilecommerce.co.jp

mobilecommerce.co.jp

584 ms

style_top.css

style_top.css

323 ms

text.css

text.css

368 ms

content.css

content.css

370 ms

owl.theme.css

owl.theme.css

371 ms

owl.carousel.css

owl.carousel.css

385 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

7 ms

btn.js

btn.js

383 ms

topmove.js

topmove.js

659 ms

header.js

header.js

718 ms

owl.carousel.js

owl.carousel.js

703 ms

perfect-scrollbar.css

perfect-scrollbar.css

720 ms

jquery.mousewheel.js

jquery.mousewheel.js

736 ms

perfect-scrollbar.js

perfect-scrollbar.js

799 ms

right_nav.js

right_nav.js

873 ms

footer_nav.js

footer_nav.js

1018 ms

toplogo.png

toplogo.png

265 ms

gnav01.png

gnav01.png

263 ms

gnav02.png

gnav02.png

349 ms

gnav03.png

gnav03.png

339 ms

gnav04.png

gnav04.png

368 ms

gnav05.png

gnav05.png

526 ms

gnav06.png

gnav06.png

558 ms

gnav08.png

gnav08.png

611 ms

visual.png

visual.png

1332 ms

object.png

object.png

864 ms

mi_02.png

mi_02.png

690 ms

ichiran.png

ichiran.png

862 ms

mi_03.png

mi_03.png

876 ms

iino.png

iino.png

1090 ms

kuwashiku.png

kuwashiku.png

1041 ms

mi_01.png

mi_01.png

1195 ms

muji.png

muji.png

1215 ms

voice.png

voice.png

1226 ms

honda.png

honda.png

1394 ms

yamaha.png

yamaha.png

1442 ms

benesse.png

benesse.png

1516 ms

his.png

his.png

1566 ms

nichirei.png

nichirei.png

1610 ms

komehyo.png

komehyo.png

1666 ms

iris.png

iris.png

1714 ms

outsourcing.png

outsourcing.png

1760 ms

aprica.png

aprica.png

1883 ms

baycrews.png

baycrews.png

1926 ms

disco.png

disco.png

1940 ms

nisso.png

nisso.png

1984 ms

otokomae.png

otokomae.png

2065 ms

forest.png

forest.png

2111 ms

cozy.png

cozy.png

2244 ms

loreal.png

loreal.png

2292 ms

intelligence.png

intelligence.png

2237 ms

rb_muryou.png

rb_muryou.png

642 ms

rb_300.png

rb_300.png

481 ms

rb_minakul.png

rb_minakul.png

325 ms

rb_nethanbai.png

rb_nethanbai.png

705 ms

rb_eczine.png

rb_eczine.png

538 ms

rb_dvd.png

rb_dvd.png

533 ms

rb_irai.png

rb_irai.png

868 ms

rb_yokomine.png

rb_yokomine.png

962 ms

ga.js

ga.js

7 ms

mti.png

mti.png

2152 ms

__utm.gif

__utm.gif

14 ms

jwell.png

jwell.png

2194 ms

diana.png

diana.png

2192 ms

uniqlo.png

uniqlo.png

2267 ms

world.png

world.png

2302 ms

mac.png

mac.png

2284 ms

jrnishi.png

jrnishi.png

2179 ms

toyota.png

toyota.png

2229 ms

tvasahi.png

tvasahi.png

2229 ms

rinnai.png

rinnai.png

2269 ms

japanet.png

japanet.png

2170 ms

egao.png

egao.png

2173 ms

oaklawn.png

oaklawn.png

2151 ms

proactiv.png

proactiv.png

2074 ms

ropping.png

ropping.png

2136 ms

sekisui.png

sekisui.png

2124 ms

hitachi.png

hitachi.png

2144 ms

nipponrenta.png

nipponrenta.png

2160 ms

fujifilm.png

fujifilm.png

2089 ms

mori.png

mori.png

2049 ms

laforet.png

laforet.png

2133 ms

parco.png

parco.png

2153 ms

shiseido.png

shiseido.png

2176 ms

netoff.png

netoff.png

2128 ms

gurunabi.png

gurunabi.png

2135 ms

shidax.png

shidax.png

2081 ms

otto.png

otto.png

2133 ms

epos.png

epos.png

2106 ms

marusan.png

marusan.png

2163 ms

adidas.png

adidas.png

2163 ms

schick.png

schick.png

2175 ms

an.png

an.png

2094 ms

salida.png

salida.png

2264 ms

mainabi.png

mainabi.png

2157 ms

atype.png

atype.png

2284 ms

fujixerox.png

fujixerox.png

2326 ms

homes.png

homes.png

2266 ms

tostem.png

tostem.png

2188 ms

kerastase.png

kerastase.png

2304 ms

maybelline.png

maybelline.png

2174 ms

lparis.png

lparis.png

2253 ms

ysl.png

ysl.png

2311 ms

shu.png

shu.png

2261 ms

volvic.png

volvic.png

2227 ms

tag.png

tag.png

2274 ms

rana.png

rana.png

2206 ms

jupitar.png

jupitar.png

2236 ms

bestperson.png

bestperson.png

2266 ms

danone.png

danone.png

2278 ms

tabio.png

tabio.png

2219 ms

golf.png

golf.png

2215 ms

bf.png

bf.png

2180 ms

daiichisankyo.png

daiichisankyo.png

2236 ms

bayer.png

bayer.png

2237 ms

index.png

index.png

2223 ms

adpark.png

adpark.png

2221 ms

webcrew.png

webcrew.png

2245 ms

skaper.png

skaper.png

2213 ms

yokohamafc.png

yokohamafc.png

2224 ms

sendenkaigi.png

sendenkaigi.png

2234 ms

members.png

members.png

2183 ms

opt.png

opt.png

2187 ms

cyberagent.png

cyberagent.png

2276 ms

docomocom.png

docomocom.png

2229 ms

shinto.png

shinto.png

2224 ms

funaisoken.png

funaisoken.png

2240 ms

mccann.png

mccann.png

2200 ms

ficc.png

ficc.png

2190 ms

ogilvy.png

ogilvy.png

2136 ms

fraudia.png

fraudia.png

2201 ms

gmo.png

gmo.png

2057 ms

ghg.png

ghg.png

2062 ms

arts.png

arts.png

2084 ms

advantage.png

advantage.png

2092 ms

ordercheese.png

ordercheese.png

2080 ms

cstyle.png

cstyle.png

2185 ms

vone.png

vone.png

2119 ms

seeds.png

seeds.png

2077 ms

pantagraph.png

pantagraph.png

2064 ms

contact_mail.png

contact_mail.png

2074 ms

contact_tel.png

contact_tel.png

2072 ms

arrow_top.png

arrow_top.png

2166 ms

bg_footer.png

bg_footer.png

2095 ms

line_menu.png

line_menu.png

2108 ms

contact_tel.png

contact_tel.png

2102 ms

contact_mail.png

contact_mail.png

2073 ms

contact_btn.png

contact_btn.png

2128 ms

contact_adress.png

contact_adress.png

2159 ms

SEO Factors

mobilecommerce.co.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 Mobilecommerce.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 Mobilecommerce.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

mobilecommerce.co.jp

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