Tools & Wizards About Us
central-park.co.jp screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

central-park.co.jp

サファリリゾート姫路セントラルパーク

Page Load Speed

8.9 sec in total

First Response

532 ms

Resources Loaded

7.8 sec

Page Rendered

489 ms

central-park.co.jp screenshot

About Website

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

サファリと遊園地、夏はプール、冬はアイススケートが楽しめる姫路セントラルパークの公式ホームページ。

Visit central-park.co.jp

Key Findings

We analyzed Central-park.co.jp page load time and found that the first response time was 532 ms and then it took 8.3 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

central-park.co.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value19.4 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.391

26/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

central-park.co.jp

532 ms

central-park.co.jp

728 ms

www.central-park.co.jp

529 ms

www.central-park.co.jp

1440 ms

gtm.js

70 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 69% of them (89 requests) were addressed to the original Central-park.co.jp, 9% (11 requests) were made to Platform.twitter.com and 5% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Central-park.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (12%)

Content Size

10.7 MB

After Optimization

9.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Central-park.co.jp main page is 10.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 10.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 57.4 kB

  • Original 69.7 kB
  • After minification 53.5 kB
  • After compression 12.3 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 16.2 kB, which is 23% 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 57.4 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 1.1 MB

  • Original 10.3 MB
  • After minification 9.1 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. Obviously, Central Park needs image optimization as it can save up to 1.1 MB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-22%

Potential reduce by 71.2 kB

  • Original 319.3 kB
  • After minification 318.3 kB
  • After compression 248.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 71.2 kB or 22% of the original size.

CSS Optimization

-30%

Potential reduce by 31.4 kB

  • Original 104.4 kB
  • After minification 94.2 kB
  • After compression 73.0 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. Central-park.co.jp needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (39%)

Requests Now

123

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

central-park.co.jp

central-park.co.jp

532 ms

central-park.co.jp

central-park.co.jp

728 ms

www.central-park.co.jp

www.central-park.co.jp

529 ms

www.central-park.co.jp

www.central-park.co.jp

1440 ms

gtm.js

gtm.js

70 ms

reset.css

reset.css

495 ms

common.css

common.css

660 ms

index.css

index.css

527 ms

all.css

all.css

39 ms

jquery.min.js

jquery.min.js

30 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

757 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

757 ms

jquery.cookie.js

jquery.cookie.js

42 ms

js

js

55 ms

analytics.js

analytics.js

18 ms

collect

collect

12 ms

collect

collect

91 ms

ga-audiences

ga-audiences

26 ms

widgets.js

widgets.js

76 ms

jquery.bxslider.css

jquery.bxslider.css

267 ms

flexslider.css

flexslider.css

311 ms

common.js

common.js

357 ms

top.js

top.js

519 ms

conversion.js

conversion.js

85 ms

hd-logo.png

hd-logo.png

180 ms

top-mv_himesyunnho_bg.png

top-mv_himesyunnho_bg.png

684 ms

top-mv_himesyunnho_all.png

top-mv_himesyunnho_all.png

1648 ms

top_mv_mofumofu_bg

top_mv_mofumofu_bg

536 ms

top_mv_mofumofu.png

top_mv_mofumofu.png

1608 ms

top_mv_ride_pc_bg.jpg

top_mv_ride_pc_bg.jpg

1363 ms

top_mv_ride_pc.png

top_mv_ride_pc.png

1802 ms

top-mv_premiumnenpass_new_pc_bg.jpg

top-mv_premiumnenpass_new_pc_bg.jpg

1393 ms

top-mv_premiumnenpass_new_pc.png

top-mv_premiumnenpass_new_pc.png

2637 ms

top-mainvisual-nav_01.png

top-mainvisual-nav_01.png

1553 ms

top-mainvisual-nav_02.png

top-mainvisual-nav_02.png

1568 ms

top-mainvisual-nav_online.png

top-mainvisual-nav_online.png

1742 ms

top-mainvisual-sns_01.png

top-mainvisual-sns_01.png

1743 ms

top-mainvisual-sns_02.png

top-mainvisual-sns_02.png

1783 ms

top-mainvisual-sns_03.png

top-mainvisual-sns_03.png

1811 ms

top-mainvisual-sns_04.png

top-mainvisual-sns_04.png

1932 ms

top-mainvisual-sns_05.png

top-mainvisual-sns_05.png

1919 ms

insta_title.png

insta_title.png

2965 ms

top-ttl_01.png

top-ttl_01.png

1978 ms

enjoy_img_bouken_ride.jpg

enjoy_img_bouken_ride.jpg

1973 ms

enjoy_img_safaritheride.jpg

enjoy_img_safaritheride.jpg

2095 ms

enjoy_img_01.jpg

enjoy_img_01.jpg

2121 ms

enjoy_img_digitalmap_hp.jpg

enjoy_img_digitalmap_hp.jpg

2299 ms

enjoy_img_appli.gif

enjoy_img_appli.gif

2154 ms

enjoy_img_card_money.gif

enjoy_img_card_money.gif

2271 ms

enjoy_img_03.jpg

enjoy_img_03.jpg

2309 ms

enjoy_img_wifi.gif

enjoy_img_wifi.gif

2340 ms

bnr_750x90.jpg

bnr_750x90.jpg

2450 ms

top-ttl_02.png

top-ttl_02.png

2471 ms

463_1.jpg

463_1.jpg

2686 ms

enjoy-slide-icon_01.png

enjoy-slide-icon_01.png

2516 ms

342_1.png

342_1.png

2800 ms

467_1.jpg

467_1.jpg

2635 ms

369_1.jpg

369_1.jpg

2694 ms

sdk.js

sdk.js

99 ms

1-CYLXxl63c

1-CYLXxl63c

195 ms

447_1.jpg

447_1.jpg

2793 ms

63 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

54 ms

420_1.jpg

420_1.jpg

2699 ms

sdk.js

sdk.js

9 ms

15 ms

settings

settings

97 ms

448_1.jpg

448_1.jpg

2700 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

23 ms

base.js

base.js

60 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

261 ms

ad_status.js

ad_status.js

118 ms

vTEfc-jlr9e_tfMt-BR8Zcc1_6XGLRk25TFtjqWuknE.js

vTEfc-jlr9e_tfMt-BR8Zcc1_6XGLRk25TFtjqWuknE.js

66 ms

embed.js

embed.js

21 ms

id

id

18 ms

enjoy-slide-icon_02.png

enjoy-slide-icon_02.png

2342 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

137 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

138 ms

Create

Create

133 ms

HcpSafari

HcpSafari

964 ms

top-ttl_03.png

top-ttl_03.png

2291 ms

GenerateIT

GenerateIT

14 ms

452_1.jpg

452_1.jpg

1617 ms

453_1.jpg

453_1.jpg

1613 ms

456_1.jpg

456_1.jpg

1502 ms

451_1.jpg

451_1.jpg

1502 ms

436_1.jpg

436_1.jpg

1881 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

19 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

37 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

55 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

71 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

74 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

76 ms

_buildManifest.js

_buildManifest.js

79 ms

_ssgManifest.js

_ssgManifest.js

78 ms

426_1.jpg

426_1.jpg

1492 ms

381_1.jpg

381_1.jpg

1416 ms

383_1.png

383_1.png

1426 ms

364_1.jpg

364_1.jpg

1449 ms

367_1.png

367_1.png

1648 ms

242_1.jpg

242_1.jpg

1495 ms

226_1.png

226_1.png

1417 ms

188_1.jpg

188_1.jpg

1404 ms

147_1.jpg

147_1.jpg

1785 ms

top-bnr_panorama.jpg

top-bnr_panorama.jpg

1491 ms

top-bnr_smartphone.gif

top-bnr_smartphone.gif

1404 ms

top-ttl_04.png

top-ttl_04.png

1391 ms

totop.png

totop.png

1483 ms

ft-ttl_01.png

ft-ttl_01.png

1360 ms

ft-ttl_02.png

ft-ttl_02.png

1363 ms

ft-ttl_03.png

ft-ttl_03.png

1354 ms

ft-ttl_04.png

ft-ttl_04.png

1341 ms

ft-ttl_05.png

ft-ttl_05.png

1344 ms

bg-cmn_01.jpg

bg-cmn_01.jpg

1356 ms

gnavi.png

gnavi.png

1321 ms

top-bg_01.jpg

top-bg_01.jpg

1195 ms

enjoy-slide-bg_01.png

enjoy-slide-bg_01.png

1227 ms

top-bg_02.jpg

top-bg_02.jpg

1249 ms

icon-cmn_01.png

icon-cmn_01.png

1263 ms

log_event

log_event

16 ms

top-bg_03.jpg

top-bg_03.jpg

1216 ms

top-mainvisual-pager_on.png

top-mainvisual-pager_on.png

1195 ms

top-mainvisual-pager.png

top-mainvisual-pager.png

1212 ms

bx_loader.gif

bx_loader.gif

1165 ms

enjoy-slide-prev.png

enjoy-slide-prev.png

1236 ms

enjoy-slide-next.png

enjoy-slide-next.png

1158 ms

event-news-slide-prev.png

event-news-slide-prev.png

1189 ms

event-news-slide-next.png

event-news-slide-next.png

1211 ms

Accessibility Review

central-park.co.jp accessibility score

78

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

central-park.co.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

central-park.co.jp SEO score

77

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

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 Central-park.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 Central-park.co.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

central-park.co.jp

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