Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

sankeien.or.jp

横浜 三溪園 - Yokohama Sankeien Garden -

Page Load Speed

2.4 sec in total

First Response

544 ms

Resources Loaded

1.7 sec

Page Rendered

195 ms

sankeien.or.jp screenshot

About Website

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

三溪園は横浜市中区本牧三之谷にあり、実業家で茶人の原三溪によって作られた日本庭園です。国の重要文化財建造物10棟、横浜市指定有形文化財建造物3棟を含め、17棟の建築物を有し、広大な敷地の起伏を生かした庭園との調和がはかられています。

Visit sankeien.or.jp

Key Findings

We analyzed Sankeien.or.jp page load time and found that the first response time was 544 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

sankeien.or.jp performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value41.2 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value1.152

1/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

sankeien.or.jp

544 ms

style.css

175 ms

jquery-1.9.1.min.js

4 ms

ga.js

77 ms

bg-common.gif

175 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 71% of them (17 requests) were addressed to the original Sankeien.or.jp, 8% (2 requests) were made to Google-analytics.com and 8% (2 requests) were made to Tripadvisor.jp. The less responsive or slowest element that took the longest time to load (900 ms) belongs to the original domain Sankeien.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.1 kB (46%)

Content Size

282.8 kB

After Optimization

151.8 kB

In fact, the total size of Sankeien.or.jp main page is 282.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 150.1 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 5.7 kB

  • Original 9.3 kB
  • After minification 8.0 kB
  • After compression 3.6 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 1.3 kB, which is 14% 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 5.7 kB or 61% of the original size.

Image Optimization

-2%

Potential reduce by 1.9 kB

  • Original 85.0 kB
  • After minification 83.2 kB

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. Sankeien images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 91.2 kB

  • Original 150.1 kB
  • After minification 150.1 kB
  • After compression 58.9 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 91.2 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 32.3 kB

  • Original 38.4 kB
  • After minification 30.5 kB
  • After compression 6.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. Sankeien.or.jp needs all CSS files to be minified and compressed as it can save up to 32.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (22%)

Requests Now

23

After Optimization

18

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

Accessibility Review

sankeien.or.jp accessibility score

76

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-hidden="true"] elements contain focusable descendents

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

sankeien.or.jp best practices score

58

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

sankeien.or.jp SEO score

79

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sankeien.or.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 Sankeien.or.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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