Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

blog.negau.org

NEGAU.ORG 活動報告

Page Load Speed

19.9 sec in total

First Response

1.8 sec

Resources Loaded

13.4 sec

Page Rendered

4.7 sec

blog.negau.org screenshot

About Website

Click here to check amazing Blog NEGAU content. Otherwise, check out these important facts you probably never knew about blog.negau.org

東北・関東大震災被害者 支援プロジェクト

Visit blog.negau.org

Key Findings

We analyzed Blog.negau.org page load time and found that the first response time was 1.8 sec and then it took 18.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

blog.negau.org performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

blog.negau.org

1762 ms

style.css

656 ms

hd_h1_01.gif

326 ms

hd_tx_01.gif

334 ms

nv_bt_01.gif

356 ms

Our browser made a total of 144 requests to load all elements on the main page. We found that 85% of them (123 requests) were addressed to the original Blog.negau.org, 3% (5 requests) were made to Platform.twitter.com and 3% (5 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Blog.negau.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 197.4 kB (8%)

Content Size

2.4 MB

After Optimization

2.2 MB

In fact, the total size of Blog.negau.org main page is 2.4 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. 55% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 113.7 kB

  • Original 137.8 kB
  • After minification 137.4 kB
  • After compression 24.1 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 113.7 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 74.8 kB

  • Original 2.2 MB
  • After minification 2.1 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. Blog NEGAU images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-81%

Potential reduce by 8.9 kB

  • Original 11.0 kB
  • After minification 7.6 kB
  • After compression 2.1 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. Blog.negau.org needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (17%)

Requests Now

143

After Optimization

119

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

Accessibility Review

blog.negau.org accessibility score

73

Accessibility Issues

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

blog.negau.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

blog.negau.org SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.negau.org can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Blog.negau.org 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

Open Graph description is not detected on the main page of Blog NEGAU. 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: