Tools & Wizards About Us
lifedesign.okwave.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lifedesign.okwave.jp

質問・疑問に答えるQ&AサイトOKWAVE

Page Load Speed

4.7 sec in total

First Response

520 ms

Resources Loaded

3.9 sec

Page Rendered

224 ms

lifedesign.okwave.jp screenshot

About Website

Click here to check amazing Lifedesign Okwave content for Japan. Otherwise, check out these important facts you probably never knew about lifedesign.okwave.jp

OKWAVE(オウケイウェイヴ)は毎月3,100万人が利用する日本発、最大級のQ＆Aサイト。あなたの質問にみんなが回答をしてくれるため、疑問や悩みをすばやく解決することができます。

Visit lifedesign.okwave.jp

Key Findings

We analyzed Lifedesign.okwave.jp page load time and found that the first response time was 520 ms and then it took 4.1 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

lifedesign.okwave.jp performance score

0

Network Requests Diagram

lifedesign.okwave.jp

520 ms

okwave.jp

871 ms

okw_base.css

207 ms

okw_top_contents.css

293 ms

okwave_ui.css

203 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lifedesign.okwave.jp, 60% (37 requests) were made to Cdn.gazo.okwave.jp and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (871 ms) relates to the external source Okwave.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 558.7 kB (61%)

Content Size

918.1 kB

After Optimization

359.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lifedesign.okwave.jp main page is 918.1 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. Javascripts take 351.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 200.7 kB

  • Original 233.1 kB
  • After minification 181.7 kB
  • After compression 32.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 51.4 kB, which is 22% 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 200.7 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 21.3 kB

  • Original 198.2 kB
  • After minification 176.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. Obviously, Lifedesign Okwave needs image optimization as it can save up to 21.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 223.7 kB

  • Original 351.8 kB
  • After minification 346.7 kB
  • After compression 128.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 223.7 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 113.0 kB

  • Original 134.9 kB
  • After minification 128.0 kB
  • After compression 22.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. Lifedesign.okwave.jp needs all CSS files to be minified and compressed as it can save up to 113.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (57%)

Requests Now

58

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lifedesign.okwave.jp

lifedesign.okwave.jp

520 ms

okwave.jp

okwave.jp

871 ms

okw_base.css

okw_base.css

207 ms

okw_top_contents.css

okw_top_contents.css

293 ms

okwave_ui.css

okwave_ui.css

203 ms

all_gbnav.css

all_gbnav.css

216 ms

bannerToSp.js

bannerToSp.js

217 ms

tracker.js

tracker.js

748 ms

ga.js

ga.js

57 ms

gpt.js

gpt.js

57 ms

sprite_gnavi.gif

sprite_gnavi.gif

55 ms

OKWAVE_logo.svg

OKWAVE_logo.svg

53 ms

sprite_icon.gif

sprite_icon.gif

54 ms

av_nophoto_60_6.gif

av_nophoto_60_6.gif

52 ms

avatar_s.jpg

avatar_s.jpg

357 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

32 ms

jquery.cookie.js

jquery.cookie.js

35 ms

jquery-ui-1.7.2.custom.min.js

jquery-ui-1.7.2.custom.min.js

33 ms

okwave_ui.js

okwave_ui.js

33 ms

namespace.js

namespace.js

32 ms

jumplist.js

jumplist.js

33 ms

elemfilter.js

elemfilter.js

34 ms

outerClick.js

outerClick.js

35 ms

util.js

util.js

33 ms

okw_common.js

okw_common.js

34 ms

jackAd.js

jackAd.js

35 ms

suggest.js

suggest.js

34 ms

navigationModal.js

navigationModal.js

37 ms

top.js

top.js

38 ms

cate_201304_01.jpg

cate_201304_01.jpg

34 ms

cate_201304_02.jpg

cate_201304_02.jpg

35 ms

cate_201404_03.jpg

cate_201404_03.jpg

36 ms

vol510.jpg

vol510.jpg

35 ms

vol511.jpg

vol511.jpg

40 ms

professional_bnr_rev03.jpg

professional_bnr_rev03.jpg

37 ms

premium_bnr_rev03.jpg

premium_bnr_rev03.jpg

39 ms

70_70_minna.jpg

70_70_minna.jpg

36 ms

70_70_pro.jpg

70_70_pro.jpg

69 ms

70_70_prem.jpg

70_70_prem.jpg

38 ms

__utm.gif

__utm.gif

14 ms

pubads_impl_81.js

pubads_impl_81.js

42 ms

ajs.php

ajs.php

339 ms

collect

collect

67 ms

container.html

container.html

8 ms

7565ce368f6c530024b213931e73c51c.jpg

7565ce368f6c530024b213931e73c51c.jpg

525 ms

sprite_sidearea.gif

sprite_sidearea.gif

56 ms

lg.php

lg.php

169 ms

widgets.js

widgets.js

83 ms

_

_

482 ms

sprite_leaf_2.gif

sprite_leaf_2.gif

12 ms

cojp_logo.svg

cojp_logo.svg

11 ms

l

l

366 ms

cs

cs

321 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

134 ms

syndication

syndication

86 ms

514987580358529024

514987580358529024

160 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

29 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

110 ms

KJxisp3y_normal.png

KJxisp3y_normal.png

141 ms

GrMd3UxE_normal.jpg

GrMd3UxE_normal.jpg

167 ms

acs

acs

355 ms

jot

jot

22 ms

SEO Factors

lifedesign.okwave.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 Lifedesign.okwave.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 Lifedesign.okwave.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

lifedesign.okwave.jp

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