Tools & Wizards About Us
ootaya.info screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ootaya.info

大多屋

Page Load Speed

9.4 sec in total

First Response

575 ms

Resources Loaded

7.3 sec

Page Rendered

1.4 sec

ootaya.info screenshot

About Website

Click here to check amazing Ootaya content. Otherwise, check out these important facts you probably never knew about ootaya.info

DESCRIPTION_INDEX

Visit ootaya.info

Key Findings

We analyzed Ootaya.info page load time and found that the first response time was 575 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ootaya.info performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value49.4 s

0/100

25%

SI (Speed Index)

Value18.8 s

0/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.43

22/100

15%

TTI (Time to Interactive)

Value55.0 s

0/100

10%

Network Requests Diagram

ootaya.info

575 ms

ootaya.info

1153 ms

common.css

384 ms

slider.css

527 ms

fontello.css

528 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original Ootaya.info, 3% (2 requests) were made to Use.fontawesome.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Ootaya.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 597.2 kB (3%)

Content Size

17.2 MB

After Optimization

16.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ootaya.info main page is 17.2 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. 50% of websites need less resources to load. Images take 16.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 147.7 kB

  • Original 185.9 kB
  • After minification 179.7 kB
  • After compression 38.2 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 147.7 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 84.4 kB

  • Original 16.5 MB
  • After minification 16.4 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. Ootaya images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 284.5 kB

  • Original 390.3 kB
  • After minification 346.0 kB
  • After compression 105.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 284.5 kB or 73% of the original size.

CSS Optimization

-73%

Potential reduce by 80.7 kB

  • Original 111.0 kB
  • After minification 88.4 kB
  • After compression 30.3 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. Ootaya.info needs all CSS files to be minified and compressed as it can save up to 80.7 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (27%)

Requests Now

66

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ootaya. 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 from 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ootaya.info

ootaya.info

575 ms

ootaya.info

ootaya.info

1153 ms

common.css

common.css

384 ms

slider.css

slider.css

527 ms

fontello.css

fontello.css

528 ms

all.css

all.css

27 ms

nav.css

nav.css

749 ms

shared.css

shared.css

567 ms

FCCalendar.css

FCCalendar.css

566 ms

index.css

index.css

570 ms

logo1.png

logo1.png

701 ms

tel.png

tel.png

697 ms

fax.png

fax.png

838 ms

logo2.png

logo2.png

938 ms

sec1-h2.png

sec1-h2.png

939 ms

sec1-photo.png

sec1-photo.png

2966 ms

sec2-h2.png

sec2-h2.png

1045 ms

sp-sec2-photo.jpg

sp-sec2-photo.jpg

2426 ms

sec3-h2.jpg

sec3-h2.jpg

1307 ms

sp-sec3-photo1.jpg

sp-sec3-photo1.jpg

2636 ms

sec3-dt1.png

sec3-dt1.png

1125 ms

sp-sec3-photo2.jpg

sp-sec3-photo2.jpg

2270 ms

sec3-dt2.png

sec3-dt2.png

1313 ms

sp-sec3-photo3.jpg

sp-sec3-photo3.jpg

2619 ms

sec3-dt3.png

sec3-dt3.png

1500 ms

sp-sec3-photo4.jpg

sp-sec3-photo4.jpg

2436 ms

sec3-dt4.png

sec3-dt4.png

2445 ms

sec4-h2.png

sec4-h2.png

2612 ms

news-link.png

news-link.png

2624 ms

news-photo2.png

news-photo2.png

2790 ms

sec4-photo1.png

sec4-photo1.png

3000 ms

news-photo3.png

news-photo3.png

2820 ms

sec5-logo.png

sec5-logo.png

2637 ms

sec5-h2.png

sec5-h2.png

2650 ms

sp-sec5-photo.jpg

sp-sec5-photo.jpg

2971 ms

embed

embed

171 ms

autoload.js

autoload.js

3001 ms

common.js

common.js

3143 ms

FCCalendar.js

FCCalendar.js

2954 ms

logo-footer.png

logo-footer.png

2996 ms

js

js

63 ms

header-line.jpg

header-line.jpg

2584 ms

nav-bg.png

nav-bg.png

2584 ms

005.jpg

005.jpg

3735 ms

004.jpg

004.jpg

3556 ms

003.jpg

003.jpg

3000 ms

002.jpg

002.jpg

3019 ms

001.jpg

001.jpg

3265 ms

footer-line.jpg

footer-line.jpg

2746 ms

sec2-bg.jpg

sec2-bg.jpg

3372 ms

sec3-bg.png

sec3-bg.png

3664 ms

Hannari.otf

Hannari.otf

4554 ms

TrajanPro.otf

TrajanPro.otf

3256 ms

KozGoPr6N.otf

KozGoPr6N.otf

4723 ms

sec3-bg-rpx.jpg

sec3-bg-rpx.jpg

3253 ms

sec3-bg1.png

sec3-bg1.png

3564 ms

sec3-bg2.png

sec3-bg2.png

3593 ms

sec3-bg3.png

sec3-bg3.png

3548 ms

sec3-bg4.png

sec3-bg4.png

2424 ms

sec4-bg.png

sec4-bg.png

2460 ms

sec5-bg.png

sec5-bg.png

3207 ms

sec5-line.png

sec5-line.png

2627 ms

sec5-h2-bg.png

sec5-h2-bg.png

2470 ms

common.css

common.css

1911 ms

slider.css

slider.css

1940 ms

fontello.css

fontello.css

1952 ms

all.css

all.css

93 ms

nav.css

nav.css

2098 ms

shared.css

shared.css

2140 ms

FCCalendar.css

FCCalendar.css

2121 ms

index.css

index.css

2285 ms

Accessibility Review

ootaya.info accessibility score

83

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.

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

Links do not have a discernible name

Best Practices

ootaya.info best practices score

75

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

SEO Factors

ootaya.info SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ootaya.info 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 Ootaya.info 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

ootaya.info

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