Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

reinobasyo.livedoor.biz

例の場所BLOG

Page Load Speed

10.6 sec in total

First Response

872 ms

Resources Loaded

4.5 sec

Page Rendered

5.3 sec

reinobasyo.livedoor.biz screenshot

About Website

Welcome to reinobasyo.livedoor.biz homepage info - get ready to check Reinobasyo Livedoor best content for Japan right away, or after learning these important things about reinobasyo.livedoor.biz

とりあえずゲームや日々の戯言やIT関係のいろんな事を書きます

Visit reinobasyo.livedoor.biz

Key Findings

We analyzed Reinobasyo.livedoor.biz page load time and found that the first response time was 872 ms and then it took 9.7 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

reinobasyo.livedoor.biz performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

reinobasyo.livedoor.biz

872 ms

template.css

396 ms

site.css

325 ms

c2.js

492 ms

smartphone.js

509 ms

Our browser made a total of 232 requests to load all elements on the main page. We found that 2% of them (5 requests) were addressed to the original Reinobasyo.livedoor.biz, 12% (27 requests) were made to Ecx.images-amazon.com and 9% (21 requests) were made to S0.2mdn.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Livedoor.blogimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (22%)

Content Size

5.3 MB

After Optimization

4.1 MB

In fact, the total size of Reinobasyo.livedoor.biz main page is 5.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 117.9 kB

  • Original 142.7 kB
  • After minification 131.6 kB
  • After compression 24.7 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 117.9 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 238.8 kB

  • Original 3.9 MB
  • After minification 3.7 MB

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

JavaScript Optimization

-63%

Potential reduce by 564.4 kB

  • Original 899.3 kB
  • After minification 846.7 kB
  • After compression 335.0 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 564.4 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 234.8 kB

  • Original 282.6 kB
  • After minification 271.8 kB
  • After compression 47.8 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. Reinobasyo.livedoor.biz needs all CSS files to be minified and compressed as it can save up to 234.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (42%)

Requests Now

226

After Optimization

131

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

Accessibility Review

reinobasyo.livedoor.biz accessibility score

45

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

reinobasyo.livedoor.biz best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

reinobasyo.livedoor.biz SEO score

85

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

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reinobasyo.livedoor.biz 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 Reinobasyo.livedoor.biz main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Reinobasyo Livedoor. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: