Tools & Wizards About Us
user-contents-search.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

user-contents-search.net

コンテンツSEO 「元ネタ」「口コミ」自動リサーチ（収集）ツール｜User Contents Search（ユーザー・コンテンツ・サーチ）

Page Load Speed

21.8 sec in total

First Response

1.5 sec

Resources Loaded

12.3 sec

Page Rendered

8 sec

user-contents-search.net screenshot

About Website

Click here to check amazing User Contents Search content for Japan. Otherwise, check out these important facts you probably never knew about user-contents-search.net

商品名やキーワードを入力し、ワンクリックするだけで、自動的に口コミ・レビュー・Q&Aの記事をリサーチ（収集）してくれるソフトウェア・ツールです。コンテンツの元ネタ集めやキーワード・リサーチにも！｜User Contents Search（ユーザー・コンテンツ・サーチ）

Visit user-contents-search.net

Key Findings

We analyzed User-contents-search.net page load time and found that the first response time was 1.5 sec and then it took 20.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

user-contents-search.net performance score

0

Network Requests Diagram

user-contents-search.net

1548 ms

styles.css

719 ms

bullet01.png

1083 ms

p01.jpg

3705 ms

03mCnPKhbUU

111 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 88% of them (82 requests) were addressed to the original User-contents-search.net, 3% (3 requests) were made to S.ytimg.com and 3% (3 requests) were made to Web-culture-service.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain User-contents-search.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (15%)

Content Size

7.1 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of User-contents-search.net main page is 7.1 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. 60% of websites need less resources to load. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 95.5 kB

  • Original 123.4 kB
  • After minification 123.1 kB
  • After compression 27.9 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 95.5 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 540.2 kB

  • Original 6.4 MB
  • After minification 5.8 MB

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. User Contents Search images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 198.7 kB

  • Original 307.8 kB
  • After minification 307.6 kB
  • After compression 109.1 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 198.7 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 230.5 kB

  • Original 278.3 kB
  • After minification 271.3 kB
  • After compression 47.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. User-contents-search.net needs all CSS files to be minified and compressed as it can save up to 230.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (19%)

Requests Now

90

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

user-contents-search.net

user-contents-search.net

1548 ms

styles.css

styles.css

719 ms

bullet01.png

bullet01.png

1083 ms

p01.jpg

p01.jpg

3705 ms

03mCnPKhbUU

03mCnPKhbUU

111 ms

p08.jpg

p08.jpg

1437 ms

research-site.png

research-site.png

1478 ms

arrow_l_red.png

arrow_l_red.png

719 ms

bullet02.png

bullet02.png

1789 ms

chiebukuro_r_34_2x.png

chiebukuro_r_34_2x.png

931 ms

r2kan.png

r2kan.png

2526 ms

r002.png

r002.png

2725 ms

t01.png

t01.png

2511 ms

syasin.jpg

syasin.jpg

1661 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

76 ms

www-embed-player.js

www-embed-player.js

101 ms

base.js

base.js

175 ms

yanagus.png

yanagus.png

2228 ms

u09.png

u09.png

2363 ms

prof_mini.jpg

prof_mini.jpg

2595 ms

naga-no.jpg

naga-no.jpg

2994 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

39 ms

ad_status.js

ad_status.js

38 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

78 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

85 ms

taka-e1381987912505.jpg

taka-e1381987912505.jpg

2515 ms

t02.png

t02.png

3237 ms

kato.jpg

kato.jpg

2714 ms

ws000000.bmp

ws000000.bmp

4244 ms

amazon_ruikei.jpg

amazon_ruikei.jpg

3235 ms

a8_jiseki.png

a8_jiseki.png

3612 ms

ranking2kan.png

ranking2kan.png

3723 ms

kounyu_list02.bmp

kounyu_list02.bmp

5558 ms

ranking_sougou3.bmp

ranking_sougou3.bmp

5936 ms

i13.png

i13.png

4807 ms

i23.png

i23.png

5028 ms

ucs-name-yoko.png

ucs-name-yoko.png

4443 ms

t03.png

t03.png

4593 ms

point01.png

point01.png

4813 ms

point02.png

point02.png

4778 ms

point01-01.png

point01-01.png

5886 ms

point01-02.png

point01-02.png

6190 ms

point03.png

point03.png

5045 ms

point01-03.png

point01-03.png

6602 ms

tables.css

tables.css

5226 ms

624 ms

commonstyles.css

commonstyles.css

5236 ms

point01-04.png

point01-04.png

6165 ms

t04.png

t04.png

5417 ms

toku01.png

toku01.png

6459 ms

bullet03.png

bullet03.png

5955 ms

toku01-01.png

toku01-01.png

6330 ms

icon_1r_96.png

icon_1r_96.png

5400 ms

toku02.png

toku02.png

5717 ms

button-builder.png

button-builder.png

6348 ms

button_003.jpg

button_003.jpg

4819 ms

toku03.png

toku03.png

5185 ms

rakuten-api-register.png

rakuten-api-register.png

6840 ms

toku04.png

toku04.png

5819 ms

i08.jpg

i08.jpg

5128 ms

toku05.png

toku05.png

5587 ms

i12.jpg

i12.jpg

5314 ms

toku06.png

toku06.png

5120 ms

i13.jpg

i13.jpg

5150 ms

t05.png

t05.png

5905 ms

hamayohe.png

hamayohe.png

5820 ms

miki.png

miki.png

5088 ms

junta.png

junta.png

4979 ms

photo.jpg

photo.jpg

4971 ms

t06.png

t06.png

4589 ms

s09.png

s09.png

4876 ms

he01.png

he01.png

6282 ms

he02.png

he02.png

4928 ms

button_001.png

button_001.png

5555 ms

p8atr15s.bmp

p8atr15s.bmp

5555 ms

ld7y0mmd.bmp

ld7y0mmd.bmp

4851 ms

nagare.png

nagare.png

4292 ms

t07.png

t07.png

4327 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1297 ms

click.js

click.js

383 ms

t08.png

t08.png

4157 ms

sign.png

sign.png

4172 ms

cnt_bg.png

cnt_bg.png

4174 ms

header.png

header.png

4950 ms

dec1_body.gif

dec1_body.gif

3928 ms

decbox1.gif

decbox1.gif

3746 ms

li.gif

li.gif

3786 ms

dott.gif

dott.gif

3698 ms

arrow_orange.gif

arrow_orange.gif

3773 ms

q1.png

q1.png

3624 ms

a1.png

a1.png

3653 ms

line.gif

line.gif

3648 ms

footer.gif

footer.gif

3478 ms

SEO Factors

user-contents-search.net SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise User-contents-search.net 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 User-contents-search.net main page’s claimed encoding is shift_jis. 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

user-contents-search.net

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