Tools & Wizards About Us
trendy.nikkei.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

trendy.nikkei.co.jp

日経トレンディネット - トレンドウォッチポータル

Page Load Speed

7 sec in total

First Response

566 ms

Resources Loaded

6.1 sec

Page Rendered

346 ms

trendy.nikkei.co.jp screenshot

About Website

Welcome to trendy.nikkei.co.jp homepage info - get ready to check Trendy Nikkei best content for Japan right away, or after learning these important things about trendy.nikkei.co.jp

日経BP社のトレンドウォッチポータルサイト。PC、薄型テレビ、デジカメなどのデジタル機器から、クルマ、住宅、日用品、健康情報、ファッション、エンターテインメントにいたるまで、あらゆる分野のトレンド情報をお届けします。

Visit trendy.nikkei.co.jp

Key Findings

We analyzed Trendy.nikkei.co.jp page load time and found that the first response time was 566 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

trendy.nikkei.co.jp performance score

0

Network Requests Diagram

trendy.nikkei.co.jp

566 ms

trendy.nikkeibp.co.jp

1027 ms

reset.css

308 ms

trnhome_201407.css

311 ms

base_201407.css

329 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Trendy.nikkei.co.jp, 41% (50 requests) were made to Trendy.nikkeibp.co.jp and 7% (8 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Trendy.nikkeibp.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 688.8 kB (53%)

Content Size

1.3 MB

After Optimization

602.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trendy.nikkei.co.jp main page is 1.3 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. Javascripts take 581.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 144.9 kB

  • Original 185.4 kB
  • After minification 175.7 kB
  • After compression 40.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. 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 144.9 kB or 78% of the original size.

Image Optimization

-31%

Potential reduce by 148.0 kB

  • Original 481.2 kB
  • After minification 333.1 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, Trendy Nikkei needs image optimization as it can save up to 148.0 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 362.1 kB

  • Original 581.5 kB
  • After minification 576.3 kB
  • After compression 219.4 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 362.1 kB or 62% of the original size.

CSS Optimization

-78%

Potential reduce by 33.8 kB

  • Original 43.1 kB
  • After minification 32.7 kB
  • After compression 9.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. Trendy.nikkei.co.jp needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (62%)

Requests Now

116

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trendy.nikkei.co.jp

trendy.nikkei.co.jp

566 ms

trendy.nikkeibp.co.jp

trendy.nikkeibp.co.jp

1027 ms

reset.css

reset.css

308 ms

trnhome_201407.css

trnhome_201407.css

311 ms

base_201407.css

base_201407.css

329 ms

trendynavi_201407.css

trendynavi_201407.css

326 ms

common_parts_201407.css

common_parts_201407.css

331 ms

index_parts_201407.css

index_parts_201407.css

465 ms

style_201407.css

style_201407.css

470 ms

201601.js

201601.js

483 ms

201601.css

201601.css

489 ms

jquery-1.12.1.min.js

jquery-1.12.1.min.js

823 ms

jquery-1.11.1.utilities.js

jquery-1.11.1.utilities.js

501 ms

trnmobile.js

trnmobile.js

617 ms

jquery.common.js

jquery.common.js

621 ms

welcome2011_schedule.js

welcome2011_schedule.js

642 ms

welcome2011.js

welcome2011.js

650 ms

bprttrn.js

bprttrn.js

665 ms

nikkei_bp.js

nikkei_bp.js

68 ms

s_code2015.js

s_code2015.js

778 ms

trendy_welcome_schedule.js

trendy_welcome_schedule.js

527 ms

gpt.js

gpt.js

4 ms

pubads_impl_82.js

pubads_impl_82.js

6 ms

container.html

container.html

73 ms

cx.js

cx.js

12 ms

segment

segment

134 ms

trendy_logo.png

trendy_logo.png

164 ms

trdmag.jpg

trdmag.jpg

330 ms

r_mail_icon.jpg

r_mail_icon.jpg

162 ms

r_twitter_icon.jpg

r_twitter_icon.jpg

154 ms

r_fb_icon.jpg

r_fb_icon.jpg

164 ms

r_rss_icon.jpg

r_rss_icon.jpg

156 ms

koshien.jpg

koshien.jpg

310 ms

top70.jpg

top70.jpg

313 ms

top70.jpg

top70.jpg

327 ms

top70.jpg

top70.jpg

325 ms

top70.jpg

top70.jpg

330 ms

top70.jpg

top70.jpg

465 ms

top70.jpg

top70.jpg

469 ms

top70.jpg

top70.jpg

488 ms

douga.jpg

douga.jpg

486 ms

top70.jpg

top70.jpg

493 ms

top70.jpg

top70.jpg

506 ms

feature_ent_1604.jpg

feature_ent_1604.jpg

618 ms

feature_off_1604.jpg

feature_off_1604.jpg

625 ms

feature_woman_1604.jpg

feature_woman_1604.jpg

649 ms

feature_health_1604.jpg

feature_health_1604.jpg

652 ms

feature_pc21_1604.jpg

feature_pc21_1604.jpg

658 ms

feature_ent_zoukan_1604.jpg

feature_ent_zoukan_1604.jpg

670 ms

lmbn_s.jpg

lmbn_s.jpg

768 ms

gooday_201507_300_42.jpg

gooday_201507_300_42.jpg

776 ms

recommend_banner_02.jpg

recommend_banner_02.jpg

807 ms

podcast_300_42.jpg

podcast_300_42.jpg

812 ms

p1.html

p1.html

50 ms

ads

ads

266 ms

p1.js

p1.js

56 ms

rep.gif

rep.gif

47 ms

s33778974383603

s33778974383603

127 ms

dag_trn_pickup_text_r.html

dag_trn_pickup_text_r.html

521 ms

yads.js

yads.js

702 ms

osd.js

osd.js

5 ms

container.html

container.html

25 ms

ads

ads

72 ms

yads_vimps-1.4.1.js

yads_vimps-1.4.1.js

589 ms

tag

tag

694 ms

top_triangle.png

top_triangle.png

164 ms

imgad

imgad

28 ms

jload

jload

75 ms

dag_trn_pickup_vb_r.html

dag_trn_pickup_vb_r.html

194 ms

nmedianet.js

nmedianet.js

43 ms

px.gif

px.gif

9 ms

bping.php

bping.php

30 ms

fcmdynet.js

fcmdynet.js

157 ms

px.gif

px.gif

29 ms

mon

mon

28 ms

dt

dt

709 ms

activeview

activeview

12 ms

activeview

activeview

16 ms

activeview

activeview

19 ms

activeview

activeview

19 ms

activeview

activeview

14 ms

ads

ads

79 ms

mediamain.html

mediamain.html

42 ms

11388.js

11388.js

69 ms

imgad

imgad

87 ms

imgad

imgad

66 ms

imgad

imgad

65 ms

imgad

imgad

69 ms

tran.png

tran.png

35 ms

nrr.js

nrr.js

36 ms

sync

sync

36 ms

bql.php

bql.php

8 ms

px.gif

px.gif

183 ms

240016-10.js

240016-10.js

90 ms

sync

sync

11 ms

195078-15.js

195078-15.js

86 ms

activeview

activeview

13 ms

imp

imp

25 ms

hiro_dynamic_player.js

hiro_dynamic_player.js

60 ms

match

match

17 ms

pixel

pixel

19 ms

cmadnx

cmadnx

183 ms

google_sync_status

google_sync_status

173 ms

PublisherEventServlet

PublisherEventServlet

555 ms

video-js.css

video-js.css

75 ms

CaliforniaGurls-logo.png

CaliforniaGurls-logo.png

142 ms

new_play.png

new_play.png

89 ms

theuppercut

theuppercut

198 ms

beacon.js

beacon.js

85 ms

CaliforniaGurls-Poster.jpg

CaliforniaGurls-Poster.jpg

87 ms

mTJ8QLQRVRWgA=

mTJ8QLQRVRWgA=

2 ms

emily.html

emily.html

62 ms

jload

jload

50 ms

bp_logo.png

bp_logo.png

163 ms

382 ms

tap.php

tap.php

4 ms

ElectricSheep_4.xml

ElectricSheep_4.xml

29 ms

mon

mon

26 ms

dt

dt

23 ms

combo

combo

152 ms

count_r.gif

count_r.gif

164 ms

SEO Factors

trendy.nikkei.co.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 Trendy.nikkei.co.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 Trendy.nikkei.co.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

trendy.nikkei.co.jp

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