Tools & Wizards About Us
oinknote.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

oinknote.jp

無料家計簿　Oink Note

Page Load Speed

11.9 sec in total

First Response

2.1 sec

Resources Loaded

9.5 sec

Page Rendered

386 ms

oinknote.jp screenshot

About Website

Click here to check amazing Oink Note content for Japan. Otherwise, check out these important facts you probably never knew about oinknote.jp

Oink Noteは無料クラウド家計簿です。ゲーミフィケーションで楽しく家計簿管理！AndroidやiPhoneからもご利用できます。

Visit oinknote.jp

Key Findings

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

Performance Metrics

oinknote.jp performance score

0

Network Requests Diagram

2064 ms

jquery-ui.css

897 ms

style.css

922 ms

jquery.js

1849 ms

jquery-ui.js

1740 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 36% of them (38 requests) were addressed to the original Oinknote.jp, 12% (13 requests) were made to Scontent.xx.fbcdn.net and 11% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Oinknote.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.6 MB

After Optimization

949.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 19.1 kB

  • Original 25.8 kB
  • After minification 22.1 kB
  • After compression 6.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 3.7 kB, which is 14% 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 19.1 kB or 74% of the original size.

Image Optimization

-18%

Potential reduce by 165.1 kB

  • Original 909.7 kB
  • After minification 744.7 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. Obviously, Oink Note needs image optimization as it can save up to 165.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 420.6 kB

  • Original 607.3 kB
  • After minification 433.9 kB
  • After compression 186.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 420.6 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 73.3 kB

  • Original 84.4 kB
  • After minification 50.6 kB
  • After compression 11.0 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. Oinknote.jp needs all CSS files to be minified and compressed as it can save up to 73.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (46%)

Requests Now

103

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2064 ms

jquery-ui.css

jquery-ui.css

897 ms

style.css

style.css

922 ms

jquery.js

jquery.js

1849 ms

jquery-ui.js

jquery-ui.js

1740 ms

style.js

style.js

758 ms

footerFixed.js

footerFixed.js

730 ms

pagetop.js

pagetop.js

1087 ms

news.css

news.css

1141 ms

toppage.css

toppage.css

1249 ms

show_ads.js

show_ads.js

6 ms

widgets.js

widgets.js

5 ms

bookmark_button.js

bookmark_button.js

343 ms

plusone.js

plusone.js

103 ms

adsbygoogle.js

adsbygoogle.js

4 ms

ga.js

ga.js

41 ms

web_stripe.png

web_stripe.png

1002 ms

web_header.png

web_header.png

414 ms

title_logo.png

title_logo.png

579 ms

ca-pub-8798852253347885.js

ca-pub-8798852253347885.js

75 ms

zrt_lookup.html

zrt_lookup.html

100 ms

show_ads_impl.js

show_ads_impl.js

101 ms

like.php

like.php

259 ms

top_touroku.gif

top_touroku.gif

401 ms

top_login.gif

top_login.gif

396 ms

main.png

main.png

1766 ms

button_market.png

button_market.png

922 ms

button_appstore.png

button_appstore.png

928 ms

button-only.gif

button-only.gif

186 ms

tokutyou1.png

tokutyou1.png

1513 ms

tokutyou2.png

tokutyou2.png

1608 ms

tokutyou3.png

tokutyou3.png

1595 ms

button_oinktoha.png

button_oinktoha.png

1482 ms

premium5.png

premium5.png

1905 ms

premium3.png

premium3.png

2224 ms

premium1.png

premium1.png

2393 ms

premium_hana.png

premium_hana.png

2295 ms

premium2.png

premium2.png

2298 ms

premium4.png

premium4.png

2883 ms

premium_hana2.png

premium_hana2.png

2632 ms

button_premium.png

button_premium.png

2976 ms

botton_newentry.png

botton_newentry.png

2823 ms

feed-icon.png

feed-icon.png

2662 ms

arrow_right.png

arrow_right.png

2780 ms

yasagoshi_b.woff

yasagoshi_b.woff

5274 ms

__utm.gif

__utm.gif

105 ms

223 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

147 ms

top_oinktoha_title.png

top_oinktoha_title.png

2968 ms

top_premium_title.png

top_premium_title.png

3521 ms

ads

ads

228 ms

ads

ads

218 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

62 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

39 ms

fastbutton

fastbutton

143 ms

osd.js

osd.js

46 ms

pagetop.png

pagetop.png

3020 ms

icon_sns.png

icon_sns.png

3257 ms

postmessageRelay

postmessageRelay

53 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

15 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

392 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

289 ms

likebox.php

likebox.php

87 ms

reset.css

reset.css

9 ms

entry-button.css

entry-button.css

9 ms

button-counter.gif

button-counter.gif

4 ms

api.js

api.js

61 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

138 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

88 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

42 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

61 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

146 ms

xYm_UD1pmAz.css

xYm_UD1pmAz.css

213 ms

TGpOWuX6Pv8.css

TGpOWuX6Pv8.css

207 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

275 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

305 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

241 ms

TTCre3391I0.js

TTCre3391I0.js

242 ms

6375185669924714728

6375185669924714728

39 ms

abg.js

abg.js

44 ms

m_js_controller.js

m_js_controller.js

65 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

100 ms

5171746271700867932

5171746271700867932

40 ms

jot

jot

129 ms

s

s

52 ms

x_button_blue2.png

x_button_blue2.png

61 ms

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

12 ms

3570_676475532394317_1080123133_n.png

3570_676475532394317_1080123133_n.png

328 ms

1450313_647089975332873_641978260_n.jpg

1450313_647089975332873_641978260_n.jpg

381 ms

12033108_833943496720017_2483110781312246534_n.jpg

12033108_833943496720017_2483110781312246534_n.jpg

422 ms

424207_219067561552362_2009012072_n.jpg

424207_219067561552362_2009012072_n.jpg

437 ms

11891122_947677565298169_6644397544726328939_n.jpg

11891122_947677565298169_6644397544726328939_n.jpg

438 ms

12278982_918687111554593_7675619696152265472_n.jpg

12278982_918687111554593_7675619696152265472_n.jpg

449 ms

12509586_891711297603822_4723489449252824200_n.jpg

12509586_891711297603822_4723489449252824200_n.jpg

448 ms

1044915_531726933562984_968975899_n.jpg

1044915_531726933562984_968975899_n.jpg

446 ms

12745626_1567349176922118_7451150064680216826_n.jpg

12745626_1567349176922118_7451150064680216826_n.jpg

461 ms

283260_215097675205396_688546_n.jpg

283260_215097675205396_688546_n.jpg

473 ms

12321411_236783106657543_2131622044143825823_n.jpg

12321411_236783106657543_2131622044143825823_n.jpg

473 ms

12118780_103056163386123_6716936518351648404_n.jpg

12118780_103056163386123_6716936518351648404_n.jpg

486 ms

1560694_602513993150228_722191336_n.jpg

1560694_602513993150228_722191336_n.jpg

485 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

43 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

42 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

43 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

75 ms

activeview

activeview

11 ms

SEO Factors

oinknote.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 Oinknote.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 Oinknote.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

oinknote.jp

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