Tools & Wizards About Us
fastpic.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fastpic.jp

FASTPIC（ファストピック） - 写真などの画像を無料アップロード出来る画像共有サイト

Page Load Speed

1.8 sec in total

First Response

208 ms

Resources Loaded

1.5 sec

Page Rendered

149 ms

fastpic.jp screenshot

About Website

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

登録不要（匿名）で写真などあらゆる画像を「無料」かつ「無制限」にアップロードする事が出来ます。また写真、画像を共有する事が出来る無料のフォトアルバムも利用出来ます。

Visit fastpic.jp

Key Findings

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

Performance Metrics

fastpic.jp performance score

0

Network Requests Diagram

fastpic.jp

208 ms

www.fastpic.jp

235 ms

reset.min.css

96 ms

style.min.css

190 ms

gen_validatorv4.min.js

215 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 49% of them (37 requests) were addressed to the original Fastpic.jp, 9% (7 requests) were made to Apis.google.com and 7% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (495 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.0 kB (30%)

Content Size

407.4 kB

After Optimization

284.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 25.7 kB

  • Original 34.1 kB
  • After minification 30.2 kB
  • After compression 8.3 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.9 kB, which is 11% 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 25.7 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 1.4 kB

  • Original 148.3 kB
  • After minification 146.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. FASTPIC images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 85.1 kB

  • Original 210.3 kB
  • After minification 209.7 kB
  • After compression 125.2 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 85.1 kB or 40% of the original size.

CSS Optimization

-73%

Potential reduce by 10.7 kB

  • Original 14.8 kB
  • After minification 14.7 kB
  • After compression 4.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. Fastpic.jp needs all CSS files to be minified and compressed as it can save up to 10.7 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (69%)

Requests Now

71

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fastpic.jp

fastpic.jp

208 ms

www.fastpic.jp

www.fastpic.jp

235 ms

reset.min.css

reset.min.css

96 ms

style.min.css

style.min.css

190 ms

gen_validatorv4.min.js

gen_validatorv4.min.js

215 ms

socialbuttons.js

socialbuttons.js

277 ms

modalDialog.min.js

modalDialog.min.js

276 ms

genjscript.min.js

genjscript.min.js

277 ms

buttonsMenu.js

buttonsMenu.js

276 ms

jquery.form.min.js

jquery.form.min.js

289 ms

adsbygoogle.js

adsbygoogle.js

7 ms

all.js

all.js

495 ms

plusone.js

plusone.js

94 ms

uploadJs.min.js

uploadJs.min.js

286 ms

jquery.js

jquery.js

376 ms

none.gif

none.gif

114 ms

header.png

header.png

115 ms

logo.png

logo.png

203 ms

photos.png

photos.png

459 ms

tabact.png

tabact.png

204 ms

tab.png

tab.png

219 ms

input_bg.gif

input_bg.gif

219 ms

optbt.png

optbt.png

270 ms

optexp.png

optexp.png

278 ms

upload.png

upload.png

289 ms

bottom.png

bottom.png

350 ms

rightbt.png

rightbt.png

350 ms

righttp.png

righttp.png

359 ms

fastpic.png

fastpic.png

364 ms

star.png

star.png

383 ms

footer.png

footer.png

408 ms

ca-pub-4232097185309361.js

ca-pub-4232097185309361.js

156 ms

zrt_lookup.html

zrt_lookup.html

154 ms

show_ads_impl.js

show_ads_impl.js

115 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

27 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

53 ms

fastbutton

fastbutton

225 ms

postmessageRelay

postmessageRelay

81 ms

ads

ads

401 ms

osd.js

osd.js

32 ms

ga.js

ga.js

42 ms

widgets.js

widgets.js

36 ms

lbtl.png

lbtl.png

222 ms

lbtr.png

lbtr.png

267 ms

lbt.png

lbt.png

273 ms

lbbl.png

lbbl.png

292 ms

lbbr.png

lbbr.png

319 ms

lbb.png

lbb.png

321 ms

lbl.png

lbl.png

380 ms

lbr.png

lbr.png

392 ms

loading.gif

loading.gif

392 ms

ads

ads

332 ms

api.js

api.js

57 ms

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

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

137 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

87 ms

__utm.gif

__utm.gif

31 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

10 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

65 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

64 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

64 ms

100 ms

xd_arbiter.php

xd_arbiter.php

221 ms

xd_arbiter.php

xd_arbiter.php

428 ms

jot

jot

125 ms

css

css

102 ms

m_js_controller.js

m_js_controller.js

56 ms

abg.js

abg.js

67 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

100 ms

2402616860347343913

2402616860347343913

38 ms

x_button_blue2.png

x_button_blue2.png

47 ms

s

s

45 ms

favicon

favicon

87 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

5 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

10 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

57 ms

SEO Factors

fastpic.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 Fastpic.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 Fastpic.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

fastpic.jp

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