Tools & Wizards About Us
haskapp.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

haskapp.co.jp

morimoto（もりもと）ーその美味しさは、北海道の恵みからー | 北海道千歳市の菓子工房 もりもとのウェブサイトへようこそ

Page Load Speed

4.8 sec in total

First Response

854 ms

Resources Loaded

3.8 sec

Page Rendered

193 ms

haskapp.co.jp screenshot

About Website

Click here to check amazing Haskapp content for Japan. Otherwise, check out these important facts you probably never knew about haskapp.co.jp

北海道千歳市の菓子工房 もりもとのウェブサイトです。北海道産素材を使用した、ハスカップジュエリー・トマトゼリー・ゆきむしスフレ・ケーキが人気です。

Visit haskapp.co.jp

Key Findings

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

Performance Metrics

haskapp.co.jp performance score

0

Network Requests Diagram

haskapp.co.jp

854 ms

master.css

376 ms

index.css

575 ms

rollover.js

598 ms

swfobject.js

989 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 59% of them (60 requests) were addressed to the original Haskapp.co.jp, 18% (18 requests) were made to Static.xx.fbcdn.net and 13% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Haskapp.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 372.8 kB (41%)

Content Size

917.0 kB

After Optimization

544.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 10.2 kB

  • Original 13.7 kB
  • After minification 11.5 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 16% 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 10.2 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 5.6 kB

  • Original 413.6 kB
  • After minification 408.0 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. Haskapp images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 147.6 kB

  • Original 236.4 kB
  • After minification 226.5 kB
  • After compression 88.8 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 147.6 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 209.5 kB

  • Original 253.3 kB
  • After minification 250.8 kB
  • After compression 43.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. Haskapp.co.jp needs all CSS files to be minified and compressed as it can save up to 209.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haskapp. 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

haskapp.co.jp

haskapp.co.jp

854 ms

master.css

master.css

376 ms

index.css

index.css

575 ms

rollover.js

rollover.js

598 ms

swfobject.js

swfobject.js

989 ms

navi.css

navi.css

192 ms

header.css

header.css

200 ms

footer.css

footer.css

383 ms

common.css

common.css

396 ms

header_btn_topics_o.gif

header_btn_topics_o.gif

193 ms

header_btn_shop02_o.gif

header_btn_shop02_o.gif

191 ms

header_btn_particular_o.gif

header_btn_particular_o.gif

382 ms

header_btn_campany02_o.gif

header_btn_campany02_o.gif

400 ms

header_btn_recruit_o.gif

header_btn_recruit_o.gif

385 ms

header_btn_nationwide_o.gif

header_btn_nationwide_o.gif

379 ms

bg_main.gif

bg_main.gif

195 ms

content_bg.gif

content_bg.gif

232 ms

titleimage_hokkaido_dorayaki.jpg

titleimage_hokkaido_dorayaki.jpg

1280 ms

002.png

002.png

1107 ms

003_2_.png

003_2_.png

1312 ms

content_bg_title.gif

content_bg_title.gif

370 ms

hd_topix.gif

hd_topix.gif

386 ms

arrow_list.gif

arrow_list.gif

408 ms

arrow_topix.gif

arrow_topix.gif

567 ms

hd_onlineinfo.gif

hd_onlineinfo.gif

578 ms

side_bg.gif

side_bg.gif

601 ms

side_bg_top.gif

side_bg_top.gif

761 ms

side_bn_online.jpg

side_bn_online.jpg

968 ms

side_bg_btn.gif

side_bg_btn.gif

958 ms

btn_eventinfo.jpg

btn_eventinfo.jpg

961 ms

bn_shopinfo.jpg

bn_shopinfo.jpg

1177 ms

bn_bussaninfo.jpg

bn_bussaninfo.jpg

1151 ms

bn_english_website2.gif

bn_english_website2.gif

1156 ms

bnr_morimoto_cake.jpg

bnr_morimoto_cake.jpg

1482 ms

bn_kodawari.jpg

bn_kodawari.jpg

1539 ms

bn_haskapp.jpg

bn_haskapp.jpg

1537 ms

bn_red.jpg

bn_red.jpg

1750 ms

bnr_an_brandbook.jpg

bnr_an_brandbook.jpg

1462 ms

bn_outline.gif

bn_outline.gif

1498 ms

bn_recruit.gif

bn_recruit.gif

1651 ms

side_bg_bottom.gif

side_bg_bottom.gif

1671 ms

bn_shinya.jpg

bn_shinya.jpg

2074 ms

content_bg_bottom.gif

content_bg_bottom.gif

1727 ms

footer_bg_menu.gif

footer_bg_menu.gif

1732 ms

header_logo.gif

header_logo.gif

378 ms

btn_online.gif

btn_online.gif

220 ms

btn_contact.gif

btn_contact.gif

397 ms

btn_sitemap.gif

btn_sitemap.gif

391 ms

btn_home.gif

btn_home.gif

385 ms

btn_allshop.gif

btn_allshop.gif

401 ms

btn_eachshop.gif

btn_eachshop.gif

398 ms

btn_kodawari.gif

btn_kodawari.gif

572 ms

btn_outline.gif

btn_outline.gif

575 ms

btn_recruit.gif

btn_recruit.gif

581 ms

btn_bussan.gif

btn_bussan.gif

586 ms

footer_btn_privacy.gif

footer_btn_privacy.gif

590 ms

footer_btn_usesite.gif

footer_btn_usesite.gif

591 ms

footer_btn_contactlist.gif

footer_btn_contactlist.gif

759 ms

footer_btn_sitemap.gif

footer_btn_sitemap.gif

945 ms

txt_copy.gif

txt_copy.gif

1149 ms

ga.js

ga.js

26 ms

likebox.php

likebox.php

235 ms

6w8IAl0e9HQ

6w8IAl0e9HQ

122 ms

__utm.gif

__utm.gif

11 ms

www-embed-player-vfl8xM8me.css

www-embed-player-vfl8xM8me.css

29 ms

www-embed-player.js

www-embed-player.js

59 ms

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

44 ms

ad_status.js

ad_status.js

70 ms

McLpmVM3wCm.css

McLpmVM3wCm.css

173 ms

r6Aw0SZFbhw.css

r6Aw0SZFbhw.css

213 ms

Czh0gDTFcBt.css

Czh0gDTFcBt.css

252 ms

hhn-1r1gAPt.css

hhn-1r1gAPt.css

328 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

326 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

377 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

297 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

297 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

297 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

375 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

401 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

493 ms

1FCa-btixu2.js

1FCa-btixu2.js

375 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

55 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

56 ms

11096708_996879210331714_8266243465472697685_n.jpg

11096708_996879210331714_8266243465472697685_n.jpg

168 ms

10849962_895315477154755_7629363514393434118_n.jpg

10849962_895315477154755_7629363514393434118_n.jpg

185 ms

1936395_1148951465124487_6389159051917240096_n.jpg

1936395_1148951465124487_6389159051917240096_n.jpg

377 ms

224680_1148951461791154_769891319816250473_n.jpg

224680_1148951461791154_769891319816250473_n.jpg

292 ms

12814512_1145691928783774_9078714187112831563_n.jpg

12814512_1145691928783774_9078714187112831563_n.jpg

260 ms

9179_1145691925450441_2043869301196049430_n.jpg

9179_1145691925450441_2043869301196049430_n.jpg

264 ms

1917648_1145692358783731_1591846316276293880_n.jpg

1917648_1145692358783731_1591846316276293880_n.jpg

265 ms

12800371_1140413222644978_8002556451287073660_n.jpg

12800371_1140413222644978_8002556451287073660_n.jpg

267 ms

12795509_1140413322644968_5306986209379791666_n.jpg

12795509_1140413322644968_5306986209379791666_n.jpg

296 ms

12806024_1140413259311641_8451043211376087149_n.jpg

12806024_1140413259311641_8451043211376087149_n.jpg

304 ms

12794460_1140413389311628_7496388089544346601_n.jpg

12794460_1140413389311628_7496388089544346601_n.jpg

303 ms

10391994_1017482468333768_6441763239795051202_n.jpg

10391994_1017482468333768_6441763239795051202_n.jpg

308 ms

12670934_1134011633285137_8702358611990180707_n.jpg

12670934_1134011633285137_8702358611990180707_n.jpg

326 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

97 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

98 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

97 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

38 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

80 ms

SEO Factors

haskapp.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haskapp.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 Haskapp.co.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

haskapp.co.jp

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