Tools & Wizards About Us
oreore.red screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

oreore.red

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

Page Load Speed

6 sec in total

First Response

1.3 sec

Resources Loaded

4.2 sec

Page Rendered

585 ms

oreore.red screenshot

About Website

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

ゲーム、アニメ、キャラクターグッズ、ダイスなどについて記事を書いています。

Visit oreore.red

Key Findings

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.

Performance Metrics

oreore.red performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

oreore.red

1310 ms

ga.js

52 ms

wp-emoji-release.min.js

471 ms

jss-style.css,qver=4.2.7.pagespeed.ce.PIptmlF7Ur.css

345 ms

style.css,qver=4.2.7.pagespeed.ce.Nlf8LJhnwp.css

515 ms

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.6 kB (47%)

Content Size

499.7 kB

After Optimization

265.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 39.0 kB

  • Original 49.4 kB
  • After minification 44.5 kB
  • After compression 10.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 39.0 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 8.7 kB

  • Original 168.5 kB
  • After minification 159.8 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. Oreore images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 130.2 kB

  • Original 211.7 kB
  • After minification 210.6 kB
  • After compression 81.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 130.2 kB or 62% of the original size.

CSS Optimization

-81%

Potential reduce by 56.7 kB

  • Original 70.1 kB
  • After minification 52.1 kB
  • After compression 13.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. 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.

Requests Breakdown

Number of requests can be reduced by 25 (48%)

Requests Now

52

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

oreore.red

oreore.red

1310 ms

ga.js

ga.js

52 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

471 ms

jss-style.css,qver=4.2.7.pagespeed.ce.PIptmlF7Ur.css

jss-style.css,qver=4.2.7.pagespeed.ce.PIptmlF7Ur.css

345 ms

style.css,qver=4.2.7.pagespeed.ce.Nlf8LJhnwp.css

style.css,qver=4.2.7.pagespeed.ce.Nlf8LJhnwp.css

515 ms

camera.css,qver=4.2.7.pagespeed.ce.4f9DodRbI6.css

camera.css,qver=4.2.7.pagespeed.ce.4f9DodRbI6.css

366 ms

skeleton.css,qver=4.2.7.pagespeed.ce.ii2ZASYUwx.css

skeleton.css,qver=4.2.7.pagespeed.ce.ii2ZASYUwx.css

375 ms

css

css

58 ms

wpp.css,qver=3.3.3.pagespeed.ce.ZUwz9rjzGg.css

wpp.css,qver=3.3.3.pagespeed.ce.ZUwz9rjzGg.css

376 ms

jquery.js,qver=1.11.2.pagespeed.jm.0kUhGt7Mm3.js

jquery.js,qver=1.11.2.pagespeed.jm.0kUhGt7Mm3.js

1030 ms

jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js

jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js

542 ms

jquery.mobilemenu.min.js,qver=4.2.7.pagespeed.ce.OzMMmO1X1k.js

jquery.mobilemenu.min.js,qver=4.2.7.pagespeed.ce.OzMMmO1X1k.js

556 ms

jquery.easing.1.3.js,qver=4.2.7.pagespeed.jm.mATJmZT0x4.js

jquery.easing.1.3.js,qver=4.2.7.pagespeed.jm.mATJmZT0x4.js

552 ms

style.css.pagespeed.ce.Hzweu4B69b.css

style.css.pagespeed.ce.Hzweu4B69b.css

625 ms

__utm.gif

__utm.gif

14 ms

bookmark_button.js

bookmark_button.js

686 ms

camera.min.js,qver=2.0.pagespeed.jm.Ulmm1ErjWC.js

camera.min.js,qver=2.0.pagespeed.jm.Ulmm1ErjWC.js

717 ms

jquery.mobile.customized.min.js,qver=2.0.pagespeed.jm.-TfCSu4aCS.js

jquery.mobile.customized.min.js,qver=2.0.pagespeed.jm.-TfCSu4aCS.js

775 ms

widget.min.js,qver=1.11.4.pagespeed.jm.rgIfiVIxvQ.js

widget.min.js,qver=1.11.4.pagespeed.jm.rgIfiVIxvQ.js

610 ms

feedly-follow-rectangle-volume-medium_2x.png

feedly-follow-rectangle-volume-medium_2x.png

63 ms

button-only@2x.png

button-only@2x.png

243 ms

bg1.png

bg1.png

334 ms

oreorelogo2.png.pagespeed.ce.ep9wGTT7W0.png

oreorelogo2.png.pagespeed.ce.ep9wGTT7W0.png

375 ms

bg-stripe.png

bg-stripe.png

242 ms

%E3%83%9C%E3%82%AB%E3%83%AD%E5%90%8D%E6%9B%B21200-630-340x160.jpg

%E3%83%9C%E3%82%AB%E3%83%AD%E5%90%8D%E6%9B%B21200-630-340x160.jpg

684 ms

%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

%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

411 ms

xpv-up10times1200-630-340x160.jpg.pagespeed.ic.52whGtICZ1.jpg

xpv-up10times1200-630-340x160.jpg.pagespeed.ic.52whGtICZ1.jpg

242 ms

%E3%82%81%E3%83%BC%E3%82%8A%E3%82%931200-630-340x160.jpg

%E3%82%81%E3%83%BC%E3%82%8A%E3%82%931200-630-340x160.jpg

797 ms

%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

%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

578 ms

%E6%A2%93%E5%B7%9D%E6%9C%88%E4%B9%83%E3%83%85%E3%83%A91200-630-340x160.jpg

%E6%A2%93%E5%B7%9D%E6%9C%88%E4%B9%83%E3%83%85%E3%83%A91200-630-340x160.jpg

828 ms

%E6%9F%94%E9%81%93%E3%82%A2%E3%83%8B%E3%83%A11200-630-340x160.jpg

%E6%9F%94%E9%81%93%E3%82%A2%E3%83%8B%E3%83%A11200-630-340x160.jpg

909 ms

%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

%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

782 ms

%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

%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

1089 ms

xpsp1200-630-340x160.jpg.pagespeed.ic.oRrnat04W7.jpg

xpsp1200-630-340x160.jpg.pagespeed.ic.oRrnat04W7.jpg

1022 ms

200x200xprofile.jpeg.pagespeed.ic.odjDLVb2Qp.jpg

200x200xprofile.jpeg.pagespeed.ic.odjDLVb2Qp.jpg

970 ms

widgets.js

widgets.js

7 ms

comment_r.png

comment_r.png

917 ms

252 ms

plusone.js

plusone.js

141 ms

btn.js

btn.js

141 ms

arrow.png

arrow.png

891 ms

like.php

like.php

181 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

button

button

28 ms

button.css

button.css

54 ms

shared.js

shared.js

57 ms

button.js

button.js

59 ms

pocket_button.png

pocket_button.png

6 ms

reset.css

reset.css

10 ms

entry-button.css

entry-button.css

9 ms

bbtn-l_v3.png

bbtn-l_v3.png

3 ms

rU2ubZ6l1Q5.js

rU2ubZ6l1Q5.js

290 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

323 ms

undefined

undefined

820 ms

Accessibility Review

oreore.red accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

oreore.red best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

oreore.red SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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

Social Sharing Optimization

oreore.red

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: