Tools & Wizards About Us
smapo.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

smapo.jp

来店ポイントアプリ スマポ | お店に行くだけ、あなたのスマホにポイント貯まる。

Page Load Speed

2.4 sec in total

First Response

326 ms

Resources Loaded

1.8 sec

Page Rendered

211 ms

smapo.jp screenshot

About Website

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

お店に行くだけ。あなたのスマホにポイント貯まる。あなたのお買い物、お出かけをもっと楽しく、お得に。スマポはお店に入るだけでポイントが貯まるiPhone/Androidアプリケーションです。

Visit smapo.jp

Key Findings

We analyzed Smapo.jp page load time and found that the first response time was 326 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

smapo.jp performance score

0

Network Requests Diagram

www.smapo.jp

326 ms

default_pc.css

438 ms

jquery-1.11.1.min.js

729 ms

jquery.biggerlink.min.js

293 ms

jquery.matchHeight-min.js

294 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that all of those requests were addressed to Smapo.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Smapo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.0 kB (42%)

Content Size

246.3 kB

After Optimization

142.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 8.8 kB

  • Original 11.9 kB
  • After minification 10.8 kB
  • After compression 3.1 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 8.8 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 6.6 kB

  • Original 105.7 kB
  • After minification 99.1 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. Smapo images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 68.1 kB

  • Original 103.7 kB
  • After minification 102.4 kB
  • After compression 35.6 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 68.1 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 20.5 kB

  • Original 25.0 kB
  • After minification 19.0 kB
  • After compression 4.5 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. Smapo.jp needs all CSS files to be minified and compressed as it can save up to 20.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (51%)

Requests Now

35

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.smapo.jp

www.smapo.jp

326 ms

default_pc.css

default_pc.css

438 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

729 ms

jquery.biggerlink.min.js

jquery.biggerlink.min.js

293 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

294 ms

default_new.js

default_new.js

293 ms

logo_smapo.png

logo_smapo.png

294 ms

btn_spmenu.png

btn_spmenu.png

487 ms

img_title_fun.png

img_title_fun.png

487 ms

img_roof.png

img_roof.png

487 ms

img_main_sp.png

img_main_sp.png

582 ms

btn_appstore.png

btn_appstore.png

576 ms

btn_googleplay.png

btn_googleplay.png

583 ms

img_main01.png

img_main01.png

582 ms

img_main02.png

img_main02.png

584 ms

img_main03.png

img_main03.png

866 ms

img_ribbon.png

img_ribbon.png

750 ms

img_logos.png

img_logos.png

750 ms

icn_ctgr_fashion_off.png

icn_ctgr_fashion_off.png

752 ms

icn_ctgr_mall_off.png

icn_ctgr_mall_off.png

751 ms

icn_ctgr_grocery_off.png

icn_ctgr_grocery_off.png

868 ms

icn_ctgr_electronics_off.png

icn_ctgr_electronics_off.png

873 ms

icn_ctgr_cosme_off.png

icn_ctgr_cosme_off.png

874 ms

icn_ctgr_service_off.png

icn_ctgr_service_off.png

875 ms

icn_ctgr_sports_off.png

icn_ctgr_sports_off.png

874 ms

icn_ctgr_stationery_off.png

icn_ctgr_stationery_off.png

1012 ms

icn_ctgr_interior_off.png

icn_ctgr_interior_off.png

1013 ms

btn_dl_appstore.png

btn_dl_appstore.png

1018 ms

btn_dl_googleplay.png

btn_dl_googleplay.png

1019 ms

icn_sns_facebook.png

icn_sns_facebook.png

1019 ms

icn_sns_twitter.png

icn_sns_twitter.png

1019 ms

icn_dl_free2.png

icn_dl_free2.png

725 ms

img_title_phone.png

img_title_phone.png

726 ms

icn_finder.png

icn_finder.png

731 ms

icn_arrow.png

icn_arrow.png

731 ms

icn_newpage.png

icn_newpage.png

732 ms

SEO Factors

smapo.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 Smapo.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 Smapo.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

smapo.jp

Open Graph data is detected on the main page of Smapo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: