Tools & Wizards About Us
oeri.co.jp screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

oeri.co.jp

ベトナム経済研究所

Page Load Speed

6.4 sec in total

First Response

738 ms

Resources Loaded

5.3 sec

Page Rendered

322 ms

oeri.co.jp screenshot

About Website

Visit oeri.co.jp now to see the best up-to-date Oeri content for Japan and also check out these interesting facts you probably never knew about oeri.co.jp

ベトナム経済研究所は、1991年にアジア問題に関心を持つ有志の方達の発起により、当時の通産省（日本側）、外務省（日本側）、商業省（ベトナム側）、そしてベトナム共産党政治局が協力して設立されました。設立後は相互の提携を密にし、日本からの投資や貿易促進を推進しています。

Visit oeri.co.jp

Key Findings

We analyzed Oeri.co.jp page load time and found that the first response time was 738 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

oeri.co.jp performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

oeri.co.jp

738 ms

www.oeri.co.jp

1188 ms

main.css

523 ms

index.css

359 ms

analytics.js

44 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 91% of them (29 requests) were addressed to the original Oeri.co.jp, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Oeri.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.9 kB (4%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oeri.co.jp main page is 2.0 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. 20% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 25.7 kB

  • Original 45.8 kB
  • After minification 43.6 kB
  • After compression 20.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 25.7 kB or 56% of the original size.

Image Optimization

-1%

Potential reduce by 22.1 kB

  • Original 1.8 MB
  • After minification 1.8 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. Oeri images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-81%

Potential reduce by 7.2 kB

  • Original 8.9 kB
  • After minification 6.8 kB
  • After compression 1.7 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. Oeri.co.jp needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (20%)

Requests Now

30

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oeri.co.jp

oeri.co.jp

738 ms

www.oeri.co.jp

www.oeri.co.jp

1188 ms

main.css

main.css

523 ms

index.css

index.css

359 ms

analytics.js

analytics.js

44 ms

bg.gif

bg.gif

182 ms

header.gif

header.gif

576 ms

here_bg.gif

here_bg.gif

217 ms

global_navi_bg.gif

global_navi_bg.gif

339 ms

branch_top.gif

branch_top.gif

340 ms

branch_bg.gif

branch_bg.gif

533 ms

submenu_bg.gif

submenu_bg.gif

356 ms

submenu_btn.gif

submenu_btn.gif

411 ms

main.jpg

main.jpg

1009 ms

11.png

11.png

3401 ms

22.png

22.png

1385 ms

33.png

33.png

1549 ms

44.png

44.png

1638 ms

55.png

55.png

2122 ms

66.png

66.png

1687 ms

77.png

77.png

2241 ms

88.png

88.png

2120 ms

btn-veri.gif

btn-veri.gif

1818 ms

news10312.jpg

news10312.jpg

1863 ms

dotte.gif

dotte.gif

1968 ms

pr.png

pr.png

2002 ms

news_pointer.gif

news_pointer.gif

2148 ms

news_flash.gif

news_flash.gif

2167 ms

news.gif

news.gif

2280 ms

footer_bg.gif

footer_bg.gif

2261 ms

collect

collect

9 ms

collect

collect

71 ms

Accessibility Review

oeri.co.jp accessibility score

60

Accessibility Issues

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

Definition list items are not wrapped in <dl> elements

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.

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

Links do not have a discernible name

Best Practices

oeri.co.jp 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

oeri.co.jp SEO score

67

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

Image elements do not have [alt] attributes

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 Oeri.co.jp 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 Oeri.co.jp 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

oeri.co.jp

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