Access oimf.jp. 島ぜんぶでおーきな祭 -第16回沖縄国際映画祭-

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value58.0 s

0/100

25%

SI (Speed Index)

Value19.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.362

30/100

15%

TTI (Time to Interactive)

Value58.5 s

0/100

10%

oimf.jp

587 ms

common.css

806 ms

top.css

320 ms

slick-theme.css

338 ms

slick.css

356 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 58% of them (60 requests) were addressed to the original Oimf.jp, 27% (28 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Oimf.jp.

Content Size

3.7 MB

After Optimization

3.4 MB

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

HTML Optimization

-79%

Potential reduce by 24.8 kB

Original 31.6 kB
After minification 26.2 kB
After compression 6.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 17% 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 24.8 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 39.5 kB

Original 3.4 MB
After minification 3.3 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. Oimf images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 105.5 kB

Original 173.3 kB
After minification 166.5 kB
After compression 67.8 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 105.5 kB or 61% of the original size.

CSS Optimization

-85%

Potential reduce by 126.7 kB

Original 148.5 kB
After minification 117.0 kB
After compression 21.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. Oimf.jp needs all CSS files to be minified and compressed as it can save up to 126.7 kB or 85% of the original size.

Requests Now

101

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

robots.txt is not valid

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Oimf.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 Oimf.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

oimf.jp

Open Graph data is detected on the main page of Oimf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

島ぜんぶでおーきな祭 -第16回沖縄国際映画祭-

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

oimf.jp

common.css

top.css

slick-theme.css

slick.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

oimf.jp

common.css

top.css

slick-theme.css

slick.css

ochan.css

add.css

headerTitle.png

mainVisual.png

mainVisualSp.png

b_vote.jpg

b_superk.jpg

b_volunteer.jpg

b_cf.jpg

catch.jpg

catch.jpg

catch.jpg

catch.jpg

catch.jpg

catch.jpg

catch.jpg

catch.jpg

import.js

ochan_tab.js

loading.gif

b_nazotoki.jpg

b_ana.png

b_eatsmile.jpg

btnFb.png

btnTw.png

fbBtn.png

twBtn.png

pageTopBtn.png

font-awesome.min.css

sdk.js

headerMenuSp.png

bgGrade.png

iconNews02.png

iconCategory01.png

iconSankaku01.png

hukidasi.png

iconCategory02.png

iconSankaku04.png