Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

observation.jp

observation

Page Load Speed

22.8 sec in total

First Response

1.4 sec

Resources Loaded

20.9 sec

Page Rendered

428 ms

observation.jp screenshot

About Website

Welcome to observation.jp homepage info - get ready to check Observation best content right away, or after learning these important things about observation.jp

Visit observation.jp

Key Findings

We analyzed Observation.jp page load time and found that the first response time was 1.4 sec and then it took 21.4 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

observation.jp performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

observation.jp

1440 ms

styles.css

378 ms

aq_tag.js

211 ms

play_for_japan.gif

1059 ms

itunes_promocodes_1-thumb-220xauto.png

1437 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 47% of them (41 requests) were addressed to the original Observation.jp, 6% (5 requests) were made to Static.affiliate.rakuten.co.jp and 5% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Static.bloglines.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.5 kB (19%)

Content Size

672.0 kB

After Optimization

541.5 kB

In fact, the total size of Observation.jp main page is 672.0 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. 40% of websites need less resources to load. Images take 456.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 41.2 kB

  • Original 52.5 kB
  • After minification 49.3 kB
  • After compression 11.4 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 41.2 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 3.8 kB

  • Original 456.8 kB
  • After minification 453.1 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. Observation images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 73.8 kB

  • Original 147.9 kB
  • After minification 146.9 kB
  • After compression 74.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 73.8 kB or 50% of the original size.

CSS Optimization

-80%

Potential reduce by 11.8 kB

  • Original 14.7 kB
  • After minification 9.8 kB
  • After compression 2.9 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. Observation.jp needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (32%)

Requests Now

81

After Optimization

55

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

Accessibility Review

observation.jp accessibility score

62

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

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

observation.jp best practices score

67

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

observation.jp SEO score

62

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document uses plugins

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 Observation.jp 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 Observation.jp 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 Observation. 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: