Analyze

oreore.red: オレオレ日記 | ゲーム、アニメ、キャラクターグッズ、ダイスなどについて記事を書いています。

ゲーム、アニメ、ダイスなど気になった事や好きな事について書いています。

Page load speed analysis

  • 72/100

    Good result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    1.3 sec

  • Resources loaded

    4.2 sec

  • Page rendered

    585 ms

  • Total page load time

    6 sec

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

We analyzed Oreore.red page load time and found that the first response time was 1.3 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Page optimization

  • HTML 49.4 kB
    Images 168.8 kB
    Javascripts 267.3 kB
    CSS 70.1 kB

    In fact, the total size of Oreore.red main page is 555.6 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. 35% of websites need less resources to load. Javascripts take 267.3 kB which makes up the majority of the site volume.

    • Original 49.4 kB
    • After minification 44.5 kB
    • After compression 10.5 kB

    HTML optimization

    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 39.0 kB or 79% of the original size.

    • Original 168.8 kB
    • After optimization 163.9 kB

    Image optimization

    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. Oreore images are well optimized though.

    • Original 267.3 kB
    • After minification 256.3 kB
    • After compression 84.6 kB

    JavaScript optimization

    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 182.7 kB or 68% of the original size.

    • Original 70.1 kB
    • After minification 52.1 kB
    • After compression 13.4 kB

    CSS optimization

    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. Oreore.red needs all CSS files to be minified and compressed as it can save up to 56.7 kB or 81% of the original size.

Network requests diagram

  • oreore.red
  • ga.js
  • wp-emoji-release.min.js
  • jss-style.css,qver=4.2.7.pagespeed.ce.PIptmlF7Ur.css
  • style.css,qver=4.2.7.pagespeed.ce.Nlf8LJhnwp.css
  • camera.css,qver=4.2.7.pagespeed.ce.4f9DodRbI6.css
  • skeleton.css,qver=4.2.7.pagespeed.ce.ii2ZASYUwx.css
  • css
  • wpp.css,qver=3.3.3.pagespeed.ce.ZUwz9rjzGg.css
  • jquery.js,qver=1.11.2.pagespeed.jm.0kUhGt7Mm3.js
  • jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js
  • jquery.mobilemenu.min.js,qver=4.2.7.pagespeed.ce.OzMMmO1X1k.js
  • jquery.easing.1.3.js,qver=4.2.7.pagespeed.jm.mATJmZT0x4.js
  • style.css.pagespeed.ce.Hzweu4B69b.css
  • __utm.gif
  • bookmark_button.js
  • camera.min.js,qver=2.0.pagespeed.jm.Ulmm1ErjWC.js
  • jquery.mobile.customized.min.js,qver=2.0.pagespeed.jm.-TfCSu4aCS.js
  • widget.min.js,qver=1.11.4.pagespeed.jm.rgIfiVIxvQ.js
  • feedly-follow-rectangle-volume-medium_2x.png
  • button-only@2x.png
  • bg1.png
  • oreorelogo2.png.pagespeed.ce.ep9wGTT7W0.png
  • bg-stripe.png
  • %E3%83%9C%E3%82%AB%E3%83%AD%E5%90%8D%E6%9B%B21200-630-340x160.jpg
  • %E3%82%B7%E3%83%AB%E3%83%B4%E3%82%A3%E3%83%BB%E3%83%90%E3%83%AB%E3%82%BF%E3%83%B3-340x160.jpg
  • xpv-up10times1200-630-340x160.jpg.pagespeed.ic.52whGtICZ1.jpg
  • %E3%82%81%E3%83%BC%E3%82%8A%E3%82%931200-630-340x160.jpg
  • %E3%82%B2%E3%83%BC%E3%83%A0%E9%9F%B3%E6%A5%BD%E3%83%99%E3%82%B9%E3%83%88140-340x160.gif
  • %E6%A2%93%E5%B7%9D%E6%9C%88%E4%B9%83%E3%83%85%E3%83%A91200-630-340x160.jpg
  • %E6%9F%94%E9%81%93%E3%82%A2%E3%83%8B%E3%83%A11200-630-340x160.jpg
  • %E3%83%90%E3%83%B3%E3%83%96%E3%83%BC%E3%83%96%E3%83%AC%E3%83%BC%E3%83%891200-630-340x160.jpg
  • %E6%9C%89%E6%96%99%E5%8B%95%E7%94%BB%E3%83%AD%E3%82%B4%E3%81%BE%E3%81%A8%E3%82%812-340x160.jpg
  • xpsp1200-630-340x160.jpg.pagespeed.ic.oRrnat04W7.jpg
  • 200x200xprofile.jpeg.pagespeed.ic.odjDLVb2Qp.jpg
  • widgets.js
  • comment_r.png
  • plusone.js
  • btn.js
  • arrow.png
  • like.php
  • cb=gapi.loaded_0
  • button
  • button.css
  • shared.js
  • button.js
  • pocket_button.png
  • reset.css
  • entry-button.css
  • bbtn-l_v3.png
  • rU2ubZ6l1Q5.js
  • LVx-xkvaJ0b.png
  • undefined

Our browser made a total of 54 requests to load all elements on the main page. We found that 59% of them (32 requests) were addressed to the original Oreore.red, 7% (4 requests) were made to D7x5nblzs94me.cloudfront.net and 6% (3 requests) were made to Cdn-ak.b.st-hatena.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Oreore.red.

Additional info on oreore.red

Requests

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

17

Javascripts

22

Images

10

CSS

3

AJAX

52

All

Possible request optimization

1

Javascripts

22

Images

1

CSS

3

AJAX

25

Optimized

27

All

Normal result

IP address

Oreore.red uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

oreore.red

adventure-guides.co.jp

ashiyasebihada.com

dyzo.jp

tacli.com

183.90.228.38

DNS records

Type Host Target/ip TTL Other
A

oreore.red

183.90.228.38 86390
NS

oreore.red

ns4.xserver.jp 86400
NS

oreore.red

ns3.xserver.jp 86400
NS

oreore.red

ns5.xserver.jp 86400
NS

oreore.red

ns1.xserver.jp 86400

Language and encoding

Good result

Language

JA ja language flag

Detected

JA ja language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oreore.red 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 Oreore.red 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.

HTTPS certificate

SSL Certificate

Oreore.red has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 100% of all visits is Japan. It’s good for Oreore.red that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Good result

Social Sharing Optimization

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

oreore.red

Share this report in social media

Analyze another website

Analyze