Access sankeien.or.jp. 横浜三溪園 - Yokohama Sankeien Garden -

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value27.4 s

0/100

25%

SI (Speed Index)

Value20.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.46

19/100

15%

TTI (Time to Interactive)

Value37.1 s

0/100

10%

sankeien.or.jp

536 ms

www.sankeien.or.jp

1308 ms

css2

40 ms

common.css

180 ms

page.css

357 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 81% of them (100 requests) were addressed to the original Sankeien.or.jp, 4% (5 requests) were made to Lh3.googleusercontent.com and 3% (4 requests) were made to Cdn.trustindex.io. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Sankeien.or.jp.

Content Size

4.6 MB

After Optimization

4.4 MB

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

HTML Optimization

-84%

Potential reduce by 105.9 kB

Original 126.7 kB
After minification 116.5 kB
After compression 20.8 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 105.9 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 38.8 kB

Original 4.3 MB
After minification 4.2 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. Sankeien images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 57.1 kB

Original 181.3 kB
After minification 181.3 kB
After compression 124.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 57.1 kB or 32% of the original size.

CSS Optimization

-36%

Potential reduce by 18.7 kB

Original 52.1 kB
After minification 51.9 kB
After compression 33.4 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 18.7 kB or 36% of the original size.

Requests Now

118

After Optimization

The browser has sent 118 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 from 17 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

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

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

sankeien.or.jp

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:

Report Summary

Performance

Accessibility

Best Practices

SEO

横浜 三溪園 - Yokohama Sankeien Garden -

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

sankeien.or.jp

www.sankeien.or.jp

css2

common.css

page.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

sankeien.or.jp

www.sankeien.or.jp

css2

common.css

page.css

layout.css

gtranslate-style24.css

sbi-styles.min.css

pagenavi-css.css

lightbox.min.css

jquery-3.6.0.min.js

jquery.cookie.min.js

scroll-hint.css

scroll-hint.js

common.js

js

chatbotData.php

chatbot.js

chatbot.css

slick.js

slick.css

slick-theme.css

jquery.js

jquery.touchwipe.min.js

jquery.lightbox.min.js

wp-embed.min.js

loader.js

wp-emoji-release.min.js

0650parking_status.jpg

ACg8ocI1KcyM-EGp0D8SAeF_f7vtmRO7FIpZ-z5IeX1eEpwB7iVopQ=s120-c-rp-mo-br100

0650parking_status.jpg

ALV-UjXw0ya1nn08D165WhChJcxxPlo0BGP84JEV9Nt6Ss0OtkBADjg=s120-c-rp-mo-ba3-br100

ALV-UjXR-Af94YBDXXPkvmNuKgqCtZXxUmHAkF6u147WQUzRFLiwodQm_w=s120-c-rp-mo-ba8-br100

ACg8ocJTmDzQ3bL2K2u9a-LoW1RZckwoXQS-0XaXCKqDIzbNtet8dw=s120-c-rp-mo-ba6-br100

ALV-UjXmoG6JItayj1G83UKnJSQkeXW56sNQrytiACxKIRzUiJvyH4k=s120-c-rp-mo-ba3-br100

pg_header_logo.png

sp_nav_search.png

sp_nav_lang.png

sp_nav_menu_open.png

sp_icon_shiru.png

sp_icon_meguru.png

sp_icon_tudou.png

sp_icon_event.png

横浜三溪園 - Yokohama Sankeien Garden -