Tools & Wizards About Us
weeeple.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

weeeple.jp

欲求不満なエロい人妻とお尻のフェティシズムの動画サイトです。－尻軽な人妻と巨尻

Page Load Speed

4.7 sec in total

First Response

1.1 sec

Resources Loaded

3.4 sec

Page Rendered

180 ms

weeeple.jp screenshot

About Website

Visit weeeple.jp now to see the best up-to-date Weeeple content for Japan and also check out these interesting facts you probably never knew about weeeple.jp

無料オンラインゲームを提供するゲームポータルサイトWeeeple（ウィープル）。つぶやきやブログなどコミュニティ機能が充実しており、ゲーマーたちの声が集まっています。アカウントを作成して、SDガンダム カプセルファイター オンライン、真・三國無双 Online、LOST SAGA、ダイスdeリッチを今すぐプレイしましょう！

Visit weeeple.jp

Key Findings

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

Performance Metrics

weeeple.jp performance score

0

Network Requests Diagram

weeeple.jp

1051 ms

common.css

905 ms

jquery.min.js

1055 ms

yuga.js

666 ms

jquery.droppy.js

343 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 68% of them (70 requests) were addressed to the original Weeeple.jp, 14% (14 requests) were made to Pbs.twimg.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Weeeple.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (62%)

Content Size

2.4 MB

After Optimization

912.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weeeple.jp main page is 2.4 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 34.2 kB

  • Original 42.7 kB
  • After minification 37.4 kB
  • After compression 8.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 5.3 kB, which is 12% 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 34.2 kB or 80% of the original size.

Image Optimization

-47%

Potential reduce by 579.0 kB

  • Original 1.2 MB
  • After minification 656.3 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, Weeeple needs image optimization as it can save up to 579.0 kB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 651.2 kB

  • Original 849.0 kB
  • After minification 669.1 kB
  • After compression 197.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 651.2 kB or 77% of the original size.

CSS Optimization

-83%

Potential reduce by 253.2 kB

  • Original 303.5 kB
  • After minification 291.4 kB
  • After compression 50.4 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. Weeeple.jp needs all CSS files to be minified and compressed as it can save up to 253.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (30%)

Requests Now

99

After Optimization

69

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weeeple.jp

weeeple.jp

1051 ms

common.css

common.css

905 ms

jquery.min.js

jquery.min.js

1055 ms

yuga.js

yuga.js

666 ms

jquery.droppy.js

jquery.droppy.js

343 ms

mainrollover.js

mainrollover.js

349 ms

heightLine.js

heightLine.js

512 ms

dragdealer.js

dragdealer.js

869 ms

dragdealer-main.js

dragdealer-main.js

673 ms

WebResource.axd

WebResource.axd

694 ms

ScriptResource.axd

ScriptResource.axd

1002 ms

ScriptResource.axd

ScriptResource.axd

686 ms

visual.css

visual.css

855 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

696 ms

slider.js

slider.js

885 ms

jquery.bxSlider.min.4.1.js

jquery.bxSlider.min.4.1.js

760 ms

googleAnalytics.js

googleAnalytics.js

690 ms

jsbn.js

jsbn.js

699 ms

jsbn2.js

jsbn2.js

706 ms

prng4.js

prng4.js

707 ms

rng.js

rng.js

834 ms

rsa.js

rsa.js

918 ms

rsa2.js

rsa2.js

959 ms

btnXSLogin.gif

btnXSLogin.gif

599 ms

head_back.gif

head_back.gif

334 ms

gnav_top.gif

gnav_top.gif

329 ms

gnav_about.gif

gnav_about.gif

414 ms

gnav_info.gif

gnav_info.gif

420 ms

gnav_acunt.gif

gnav_acunt.gif

432 ms

gnav_help.gif

gnav_help.gif

432 ms

login_pickup_tit02.jpg

login_pickup_tit02.jpg

627 ms

login_form_tit.png

login_form_tit.png

510 ms

login_btn_acount.jpg

login_btn_acount.jpg

654 ms

login_mail.gif

login_mail.gif

595 ms

login_pass.gif

login_pass.gif

593 ms

login_btn_login.jpg

login_btn_login.jpg

594 ms

open_id_tit.png

open_id_tit.png

631 ms

openid_twitter_icon.png

openid_twitter_icon.png

732 ms

openid_facebook_icon.png

openid_facebook_icon.png

732 ms

openid_mixi_icon.png

openid_mixi_icon.png

751 ms

openid_google_icon.png

openid_google_icon.png

788 ms

icon_info.gif

icon_info.gif

803 ms

icon_maintenance.gif

icon_maintenance.gif

1042 ms

foot_cjij_logo.gif

foot_cjij_logo.gif

1121 ms

head_logo.gif

head_logo.gif

1025 ms

arrow_grey.gif

arrow_grey.gif

494 ms

EsJxgGquO8M

EsJxgGquO8M

93 ms

7OOwds1iw74

7OOwds1iw74

236 ms

rAbDr0cpQy0

rAbDr0cpQy0

271 ms

top_area.jpg

top_area.jpg

1143 ms

load-indicator.gif

load-indicator.gif

983 ms

login_pickup_bg.jpg

login_pickup_bg.jpg

1165 ms

game_line_bg.jpg

game_line_bg.jpg

981 ms

arrow-l.png

arrow-l.png

1126 ms

arrow-r.png

arrow-r.png

1126 ms

top_pickup_bg.jpg

top_pickup_bg.jpg

1299 ms

hl_pickup_top.jpg

hl_pickup_top.jpg

1320 ms

top_info_bg.jpg

top_info_bg.jpg

1427 ms

hl_info_top.jpg

hl_info_top.jpg

1278 ms

top_infotab02_off.jpg

top_infotab02_off.jpg

1306 ms

arrow_black.gif

arrow_black.gif

481 ms

top_frame_bottom.gif

top_frame_bottom.gif

770 ms

hl_comment.jpg

hl_comment.jpg

974 ms

widgets.js

widgets.js

147 ms

top_infotab01_on.jpg

top_infotab01_on.jpg

1311 ms

foot_back.gif

foot_back.gif

482 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

12 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

24 ms

www-embed-player.js

www-embed-player.js

52 ms

top_infotab01_off.jpg

top_infotab01_off.jpg

1332 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

110 ms

ad_status.js

ad_status.js

113 ms

top_info_bg2.jpg

top_info_bg2.jpg

1282 ms

hl_info_top2.jpg

hl_info_top2.jpg

1290 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

172 ms

gnav_top_on.gif

gnav_top_on.gif

1244 ms

gnav_about_on.gif

gnav_about_on.gif

1251 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

95 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

95 ms

gnav_info_on.gif

gnav_info_on.gif

1319 ms

gnav_acunt_on.gif

gnav_acunt_on.gif

1314 ms

gnav_help_on.gif

gnav_help_on.gif

1349 ms

top_infotab02_on.jpg

top_infotab02_on.jpg

1360 ms

syndication

syndication

94 ms

608869237529006080

608869237529006080

164 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

29 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

159 ms

brsubfsN_normal.png

brsubfsN_normal.png

331 ms

ESvE7TRa_normal.jpg

ESvE7TRa_normal.jpg

369 ms

CPE5Xu8UYAAEaVl.jpg:small

CPE5Xu8UYAAEaVl.jpg:small

420 ms

CPE4nEmUwAEMHF3.jpg:small

CPE4nEmUwAEMHF3.jpg:small

409 ms

CN9EtCXU8AAXHiJ.jpg:small

CN9EtCXU8AAXHiJ.jpg:small

411 ms

CNYmAebUkAAthjT.jpg:small

CNYmAebUkAAthjT.jpg:small

485 ms

CM1J_qRVAAADvNW.jpg:small

CM1J_qRVAAADvNW.jpg:small

414 ms

CM1JuDSUkAAkUx9.jpg:small

CM1JuDSUkAAkUx9.jpg:small

458 ms

CLNQa1BUkAA539_.jpg:small

CLNQa1BUkAA539_.jpg:small

545 ms

CKqQIoFUkAE4H8e.jpg:small

CKqQIoFUkAE4H8e.jpg:small

503 ms

CKqLUaZUcAAHh3l.jpg:small

CKqLUaZUcAAHh3l.jpg:small

438 ms

CJcu_atUsAAlqEr.jpg:small

CJcu_atUsAAlqEr.jpg:small

510 ms

CIyomXhUYAAF_OZ.jpg:small

CIyomXhUYAAF_OZ.jpg:small

463 ms

CHxBv19UEAA7CV4.jpg:small

CHxBv19UEAA7CV4.jpg:small

546 ms

jot

jot

25 ms

SEO Factors

weeeple.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 Weeeple.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 Weeeple.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

weeeple.jp

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