Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

centralpark.co.jp

セントラルパーク - Centralpark

Page Load Speed

10.7 sec in total

First Response

1.3 sec

Resources Loaded

9.1 sec

Page Rendered

302 ms

centralpark.co.jp screenshot

About Website

Welcome to centralpark.co.jp homepage info - get ready to check Centralpark best content for Japan right away, or after learning these important things about centralpark.co.jp

名古屋栄の地下街セントラルパークのオフィシャルウェブサイト。ショップやアクセス情報のほか、イベントなどの最新ニュースをお届けします。

Visit centralpark.co.jp

Key Findings

We analyzed Centralpark.co.jp page load time and found that the first response time was 1.3 sec and then it took 9.4 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

centralpark.co.jp performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value4,250 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value63.7 s

0/100

10%

Network Requests Diagram

centralpark.co.jp

1300 ms

main.css

1160 ms

main-responsive.css

518 ms

jquery-1.7.2.min.js

1033 ms

bootstrap.js

865 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 83% of them (70 requests) were addressed to the original Centralpark.co.jp, 8% (7 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Centralpark.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.2 kB (14%)

Content Size

4.0 MB

After Optimization

3.4 MB

In fact, the total size of Centralpark.co.jp main page is 4.0 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 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 26.0 kB

  • Original 30.9 kB
  • After minification 19.1 kB
  • After compression 5.0 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 11.9 kB, which is 38% 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 26.0 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 254.6 kB

  • Original 3.6 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. Centralpark images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 153.1 kB

  • Original 224.8 kB
  • After minification 190.6 kB
  • After compression 71.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 153.1 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 131.6 kB

  • Original 152.5 kB
  • After minification 112.9 kB
  • After compression 20.9 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. Centralpark.co.jp needs all CSS files to be minified and compressed as it can save up to 131.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (23%)

Requests Now

83

After Optimization

64

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

Accessibility Review

centralpark.co.jp accessibility score

71

Accessibility Issues

ARIA

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.

Impact

Issue

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 toggle fields do not have accessible names

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

Best Practices

centralpark.co.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

centralpark.co.jp SEO score

91

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 doesn't use 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 Centralpark.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 Centralpark.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

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