Tools & Wizards About Us
oeia.or.jp screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

oeia.or.jp

独立行政法人 空港周辺整備機構｜福岡空港周辺地域

Page Load Speed

6.6 sec in total

First Response

558 ms

Resources Loaded

5.8 sec

Page Rendered

179 ms

oeia.or.jp screenshot

About Website

Visit oeia.or.jp now to see the best up-to-date Oeia content and also check out these interesting facts you probably never knew about oeia.or.jp

独立行政法人 空港周辺整備機構は、福岡空港周辺地域で騒音軽減と生活環境改善に努めています。

Visit oeia.or.jp

Key Findings

We analyzed Oeia.or.jp page load time and found that the first response time was 558 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

oeia.or.jp performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

oeia.or.jp

558 ms

www.oeia.or.jp

1150 ms

default.css

204 ms

common.css

408 ms

header.css

517 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 79% of them (26 requests) were addressed to the original Oeia.or.jp, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 61.0 kB (11%)

Content Size

531.9 kB

After Optimization

470.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 14.0 kB

  • Original 18.4 kB
  • After minification 15.8 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 2.5 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 14.0 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 3.5 kB

  • Original 409.7 kB
  • After minification 406.2 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. Oeia images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 12.3 kB

  • Original 65.0 kB
  • After minification 62.9 kB
  • After compression 52.7 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 12.3 kB or 19% of the original size.

CSS Optimization

-80%

Potential reduce by 31.3 kB

  • Original 38.8 kB
  • After minification 30.3 kB
  • After compression 7.6 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. Oeia.or.jp needs all CSS files to be minified and compressed as it can save up to 31.3 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (47%)

Requests Now

30

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oeia.or.jp

oeia.or.jp

558 ms

www.oeia.or.jp

www.oeia.or.jp

1150 ms

default.css

default.css

204 ms

common.css

common.css

408 ms

header.css

header.css

517 ms

index.css

index.css

774 ms

css

css

38 ms

jquery-3.1.0.min.js

jquery-3.1.0.min.js

20 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

24 ms

drawernav.js

drawernav.js

575 ms

callink.js

callink.js

571 ms

current.js

current.js

573 ms

switchimages.js

switchimages.js

607 ms

ga.js

ga.js

699 ms

analytics.js

analytics.js

106 ms

topics.cgi

topics.cgi

228 ms

top_bg.png

top_bg.png

214 ms

hero_pc.png

hero_pc.png

866 ms

hrline.png

hrline.png

215 ms

navicon_bouon.png

navicon_bouon.png

213 ms

navicon_iten.png

navicon_iten.png

235 ms

navicon_kaihatsu.png

navicon_kaihatsu.png

381 ms

navicon_ryokuchi.png

navicon_ryokuchi.png

410 ms

navicon_nyusatsu.png

navicon_nyusatsu.png

410 ms

mark_bouon.png

mark_bouon.png

422 ms

mark_iten.png

mark_iten.png

436 ms

bnr_for_kids.gif

bnr_for_kids.gif

585 ms

navicon_kuiki.png

navicon_kuiki.png

612 ms

font

font

3208 ms

collect

collect

13 ms

js

js

60 ms

function.js

function.js

390 ms

osirase.css

osirase.css

402 ms

Accessibility Review

oeia.or.jp accessibility score

90

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

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

Best Practices

oeia.or.jp 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

oeia.or.jp SEO score

99

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oeia.or.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 Oeia.or.jp main page’s claimed encoding is shift_jis. 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

oeia.or.jp

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