Tools & Wizards About Us
onokoro.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

onokoro.jp

★休日は淡路島へ！淡路島の観光-★淡路ワールドパークＯＮＯＫＯＲＯ【公式ＨＰ】淡路島　観光

Page Load Speed

13.2 sec in total

First Response

1.9 sec

Resources Loaded

11 sec

Page Rendered

334 ms

onokoro.jp screenshot

About Website

Click here to check amazing Onokoro content for Japan. Otherwise, check out these important facts you probably never knew about onokoro.jp

世界を遊ぼう。淡路ワールドパークＯＮＯＫＯＲＯ

Visit onokoro.jp

Key Findings

We analyzed Onokoro.jp page load time and found that the first response time was 1.9 sec and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

onokoro.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value31.8 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.494

17/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

onokoro.jp

1891 ms

reset.css

428 ms

style.css

441 ms

jquery-1.10.2.min.js

871 ms

jquery.easing.1.3.js

478 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 82% of them (94 requests) were addressed to the original Onokoro.jp, 9% (10 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (8.4 sec) belongs to the original domain Onokoro.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 219.3 kB (8%)

Content Size

2.7 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 18.3 kB

  • Original 24.0 kB
  • After minification 22.8 kB
  • After compression 5.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. 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 18.3 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 83.8 kB

  • Original 2.6 MB
  • After minification 2.5 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. Onokoro images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 98.3 kB

  • Original 137.4 kB
  • After minification 118.0 kB
  • After compression 39.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 98.3 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 19.0 kB

  • Original 23.1 kB
  • After minification 18.5 kB
  • After compression 4.1 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. Onokoro.jp needs all CSS files to be minified and compressed as it can save up to 19.0 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

112

After Optimization

76

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onokoro.jp

onokoro.jp

1891 ms

reset.css

reset.css

428 ms

style.css

style.css

441 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

871 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

478 ms

menu.js

menu.js

486 ms

gotop.js

gotop.js

501 ms

onorin.js

onorin.js

647 ms

jquery.flexslider.js

jquery.flexslider.js

651 ms

snowfall.jquery_sakura.js

snowfall.jquery_sakura.js

690 ms

slide09.jpg

slide09.jpg

3282 ms

cloud_03.png

cloud_03.png

1651 ms

cloud_02.png

cloud_02.png

1651 ms

cloud_01.png

cloud_01.png

1646 ms

onorin_banzai_l.png

onorin_banzai_l.png

1683 ms

kororin_banzai_r.png

kororin_banzai_r.png

1651 ms

balloon01.png

balloon01.png

1650 ms

balloon02.png

balloon02.png

1651 ms

slide01.jpg

slide01.jpg

4564 ms

slide02.jpg

slide02.jpg

3278 ms

slide03.jpg

slide03.jpg

2639 ms

slide04.jpg

slide04.jpg

2832 ms

slide05.jpg

slide05.jpg

3727 ms

t_news_bn.gif

t_news_bn.gif

1919 ms

side_bn_groupplan.jpg

side_bn_groupplan.jpg

3276 ms

side_bn_tokutoku.jpg

side_bn_tokutoku.jpg

3498 ms

side_bn_event.jpg

side_bn_event.jpg

3686 ms

side_bn_kyouryu.jpg

side_bn_kyouryu.jpg

3690 ms

side_bn_awajiinfo.jpg

side_bn_awajiinfo.jpg

3553 ms

side_bn_weather.jpg

side_bn_weather.jpg

3755 ms

pagetop_bn.gif

pagetop_bn.gif

3769 ms

f_iimg01.png

f_iimg01.png

3904 ms

f_iimg02.png

f_iimg02.png

3904 ms

f_iimg03.png

f_iimg03.png

3946 ms

f_iimg04.png

f_iimg04.png

3969 ms

f_iimg05.png

f_iimg05.png

3980 ms

f_iimg06.png

f_iimg06.png

4119 ms

f_iimg07.png

f_iimg07.png

4112 ms

f_iimg08.png

f_iimg08.png

4163 ms

f_iimg09.png

f_iimg09.png

4178 ms

f_iimg10.png

f_iimg10.png

4191 ms

f_iimg11.png

f_iimg11.png

4317 ms

f_iimg12.png

f_iimg12.png

4330 ms

slide003.jpg

slide003.jpg

3635 ms

slide01.jpg

slide01.jpg

8406 ms

slide02.jpg

slide02.jpg

3209 ms

slide04.jpg

slide04.jpg

4558 ms

001001.jpg

001001.jpg

4600 ms

kyouryuu201602.jpg

kyouryuu201602.jpg

5231 ms

gakuseiouen.jpg

gakuseiouen.jpg

3989 ms

4f08db6b1decfe529ca2559538e8b101.jpg

4f08db6b1decfe529ca2559538e8b101.jpg

5749 ms

slide01.jpg

slide01.jpg

4611 ms

gtm.js

gtm.js

55 ms

header_bk_alberobello.png

header_bk_alberobello.png

4993 ms

alberobello_front.png

alberobello_front.png

4657 ms

h_bk.jpg

h_bk.jpg

4387 ms

hnav01.jpg

hnav01.jpg

4565 ms

likebox.php

likebox.php

80 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

30 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

39 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

45 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

64 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

37 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

62 ms

486050_349530501823665_486771549_n.jpg

486050_349530501823665_486771549_n.jpg

1450 ms

735186_348371878606194_1676404269_n.jpg

735186_348371878606194_1676404269_n.jpg

30 ms

970751_1382937021918438_988623078_n.jpg

970751_1382937021918438_988623078_n.jpg

94 ms

10478586_1004800819599280_8010951332024375867_n.jpg

10478586_1004800819599280_8010951332024375867_n.jpg

32 ms

10388205_1411242935826860_6530136039335521734_n.jpg

10388205_1411242935826860_6530136039335521734_n.jpg

96 ms

533531_107997942702890_1459631902_n.jpg

533531_107997942702890_1459631902_n.jpg

30 ms

12208635_660067330799907_8205518818215039758_n.jpg

12208635_660067330799907_8205518818215039758_n.jpg

33 ms

1900103_3882510716478_1899704773_n.jpg

1900103_3882510716478_1899704773_n.jpg

31 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

25 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

23 ms

h_logo.png

h_logo.png

3102 ms

hnav02.jpg

hnav02.jpg

3003 ms

gnav_bk.png

gnav_bk.png

3131 ms

gnav_on.jpg

gnav_on.jpg

3375 ms

gnav.jpg

gnav.jpg

3635 ms

gnavi_img_01.png

gnavi_img_01.png

3243 ms

gnavi_img_02.png

gnavi_img_02.png

3280 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

5 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

7 ms

gnavi_img_03.png

gnavi_img_03.png

3081 ms

gnavi_img_04.png

gnavi_img_04.png

2465 ms

gnavi_img_05.png

gnavi_img_05.png

2342 ms

gnavi_img_06.png

gnavi_img_06.png

1943 ms

gnavi_img_07.png

gnavi_img_07.png

1954 ms

gnavi_img_08.png

gnavi_img_08.png

1735 ms

bk.png

bk.png

1760 ms

top_dateboard.png

top_dateboard.png

1733 ms

bk01.jpg

bk01.jpg

1758 ms

t_slide_bk.gif

t_slide_bk.gif

2156 ms

t_tv_bk.gif

t_tv_bk.gif

1768 ms

top_youtube_tv.png

top_youtube_tv.png

1927 ms

t_news_bk.jpg

t_news_bk.jpg

1701 ms

t_news_kyara.png

t_news_kyara.png

1928 ms

t_news_tit.png

t_news_tit.png

1727 ms

t_news_border.gif

t_news_border.gif

1762 ms

t_news_no_photo.jpg

t_news_no_photo.jpg

1833 ms

f_bk.png

f_bk.png

1776 ms

f_logo.png

f_logo.png

1793 ms

f_add.png

f_add.png

1783 ms

f_line.gif

f_line.gif

1844 ms

f_link_icon.gif

f_link_icon.gif

1853 ms

bg_control_nav.png

bg_control_nav.png

1812 ms

bg_direction_nav.png

bg_direction_nav.png

1795 ms

sakura_05.png

sakura_05.png

1764 ms

sakura_02.png

sakura_02.png

1606 ms

sakura_01.png

sakura_01.png

2073 ms

sakura_04.png

sakura_04.png

1611 ms

sakura_03.png

sakura_03.png

1670 ms

sakura_07.png

sakura_07.png

1606 ms

sakura_06.png

sakura_06.png

1599 ms

Accessibility Review

onokoro.jp accessibility score

71

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

onokoro.jp 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

onokoro.jp SEO score

91

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

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

    UTF-8

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

onokoro.jp

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