Tools & Wizards About Us
age1116.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

age1116.com

age1116.com – このドメインはお名前.comで取得されています。

Page Load Speed

11.5 sec in total

First Response

2.6 sec

Resources Loaded

8.4 sec

Page Rendered

510 ms

age1116.com screenshot

About Website

Visit age1116.com now to see the best up-to-date Age 1116 content and also check out these interesting facts you probably never knew about age1116.com

MacintoshとかPCとかのニュースを斜めっぽく記事にしてるようなBlog

Visit age1116.com

Key Findings

We analyzed Age1116.com page load time and found that the first response time was 2.6 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

age1116.com performance score

0

Network Requests Diagram

www.age1116.com

2619 ms

ksq5yli.js

148 ms

d

153 ms

widget.css

352 ms

haiku-player.css

354 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 30% of them (38 requests) were addressed to the original Age1116.com, 12% (15 requests) were made to Pixel.wp.com and 8% (10 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source I2.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 370.1 kB (39%)

Content Size

944.7 kB

After Optimization

574.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Age1116.com main page is 944.7 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. 60% of websites need less resources to load. Javascripts take 385.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 61.9 kB

  • Original 76.5 kB
  • After minification 74.8 kB
  • After compression 14.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 61.9 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 5.8 kB

  • Original 357.4 kB
  • After minification 351.7 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. Age 1116 images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 210.7 kB

  • Original 385.1 kB
  • After minification 364.1 kB
  • After compression 174.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 210.7 kB or 55% of the original size.

CSS Optimization

-73%

Potential reduce by 91.7 kB

  • Original 125.8 kB
  • After minification 112.5 kB
  • After compression 34.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. Age1116.com needs all CSS files to be minified and compressed as it can save up to 91.7 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 82 (67%)

Requests Now

122

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.age1116.com

www.age1116.com

2619 ms

ksq5yli.js

ksq5yli.js

148 ms

d

d

153 ms

widget.css

widget.css

352 ms

haiku-player.css

haiku-player.css

354 ms

styles.css

styles.css

365 ms

twitter-feed.css

twitter-feed.css

366 ms

style.css

style.css

725 ms

black.css

black.css

526 ms

css

css

29 ms

wpp.css

wpp.css

529 ms

style.css

style.css

545 ms

amazonjs.css

amazonjs.css

546 ms

genericons.css

genericons.css

1048 ms

jetpack.css

jetpack.css

1057 ms

lightbox.css

lightbox.css

727 ms

jquery.js

jquery.js

1450 ms

jquery-migrate.min.js

jquery-migrate.min.js

732 ms

prototype.js

prototype.js

22 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

906 ms

scriptaculous.js

scriptaculous.js

24 ms

effects.js

effects.js

26 ms

builder.js

builder.js

27 ms

lightbox.js

lightbox.js

1087 ms

itunes_autolinkmaker.js

itunes_autolinkmaker.js

31 ms

ga.js

ga.js

13 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

784 ms

__utm.gif

__utm.gif

11 ms

px.gif

px.gif

5 ms

px.gif

px.gif

5 ms

adsbygoogle.js

adsbygoogle.js

4 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

721 ms

haiku-player.js

haiku-player.js

553 ms

photon.js

photon.js

674 ms

jquery.form.min.js

jquery.form.min.js

684 ms

scripts.js

scripts.js

721 ms

devicepx-jetpack.js

devicepx-jetpack.js

3 ms

wp-embed.min.js

wp-embed.min.js

736 ms

sharing.js

sharing.js

848 ms

e-201611.js

e-201611.js

3 ms

builder.js

builder.js

2 ms

effects.js

effects.js

4 ms

dragdrop.js

dragdrop.js

3 ms

controls.js

controls.js

7 ms

slider.js

slider.js

9 ms

sound.js

sound.js

8 ms

fbds.js

fbds.js

50 ms

background.png

background.png

286 ms

2015052101.png

2015052101.png

2053 ms

2015042302.png

2015042302.png

1513 ms

2015030601.png

2015030601.png

2175 ms

cover_s.jpg

cover_s.jpg

328 ms

header_bg.png

header_bg.png

274 ms

navi.png

navi.png

273 ms

cropped-CUR-TOP20130803031.jpg

cropped-CUR-TOP20130803031.jpg

399 ms

sidebar_bg.png

sidebar_bg.png

272 ms

Facebook.png

Facebook.png

272 ms

Twitter.png

Twitter.png

448 ms

Google_plus.png

Google_plus.png

435 ms

Tumblr.png

Tumblr.png

438 ms

RSS.png

RSS.png

446 ms

2015030601.png

2015030601.png

2092 ms

2015052101.png

2015052101.png

2249 ms

2015042301.png

2015042301.png

2222 ms

2015031301.png

2015031301.png

2339 ms

2013032401.png

2013032401.png

2659 ms

2013032401.png

2013032401.png

2580 ms

top-row-P2.jpg

top-row-P2.jpg

1157 ms

9017413206.jpg

9017413206.jpg

1349 ms

9017413206.jpg

9017413206.jpg

1550 ms

2015020501.png

2015020501.png

2915 ms

2015020501.png

2015020501.png

2987 ms

p.gif

p.gif

80 ms

zE33bAA==

zE33bAA==

16 ms

Genericons.svg

Genericons.svg

586 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

15 ms

ca-pub-2838539859831369.js

ca-pub-2838539859831369.js

120 ms

zrt_lookup.html

zrt_lookup.html

114 ms

show_ads_impl.js

show_ads_impl.js

74 ms

270 ms

sdk.js

sdk.js

193 ms

ads

ads

298 ms

share

share

117 ms

g.gif

g.gif

34 ms

graph.facebook.com

graph.facebook.com

153 ms

share

share

130 ms

graph.facebook.com

graph.facebook.com

262 ms

share

share

181 ms

graph.facebook.com

graph.facebook.com

263 ms

share

share

180 ms

graph.facebook.com

graph.facebook.com

261 ms

share

share

178 ms

graph.facebook.com

graph.facebook.com

260 ms

share

share

177 ms

graph.facebook.com

graph.facebook.com

267 ms

share

share

169 ms

graph.facebook.com

graph.facebook.com

259 ms

osd.js

osd.js

41 ms

loading.gif

loading.gif

318 ms

closelabel.gif

closelabel.gif

346 ms

g.gif

g.gif

9 ms

g.gif

g.gif

10 ms

g.gif

g.gif

9 ms

g.gif

g.gif

35 ms

g.gif

g.gif

35 ms

g.gif

g.gif

36 ms

g.gif

g.gif

37 ms

g.gif

g.gif

36 ms

g.gif

g.gif

36 ms

g.gif

g.gif

38 ms

g.gif

g.gif

38 ms

g.gif

g.gif

38 ms

g.gif

g.gif

37 ms

g.gif

g.gif

34 ms

43 ms

xd_arbiter.php

xd_arbiter.php

66 ms

xd_arbiter.php

xd_arbiter.php

119 ms

m_js_controller.js

m_js_controller.js

14 ms

abg.js

abg.js

26 ms

favicon

favicon

41 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

39 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

24 ms

s

s

20 ms

x_button_blue2.svg

x_button_blue2.svg

12 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

6 ms

activeview

activeview

12 ms

SEO Factors

age1116.com 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 Age1116.com 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 Age1116.com 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

age1116.com

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