Tools & Wizards About Us
yokohamatriennale.jp screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

yokohamatriennale.jp

横浜トリエンナーレ

Page Load Speed

9.1 sec in total

First Response

791 ms

Resources Loaded

8 sec

Page Rendered

216 ms

yokohamatriennale.jp screenshot

About Website

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

3年に1度、横浜で開催される日本を代表する現代アートの国際展。2001年に開始して以来、みなとみらい地区をはじめとする横浜の都心臨海部の施設や屋外広場を会場に、2005年、2008年、2011年とこれまでに4回開催してきました。

Visit yokohamatriennale.jp

Key Findings

We analyzed Yokohamatriennale.jp page load time and found that the first response time was 791 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

yokohamatriennale.jp performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.531

14/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

yokohamatriennale.jp

791 ms

reset.css

393 ms

fonts-min.css

395 ms

default.css

394 ms

frame.css

589 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 78% of them (84 requests) were addressed to the original Yokohamatriennale.jp, 9% (10 requests) were made to Google.com and 4% (4 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Yokohamatriennale.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.3 kB (10%)

Content Size

2.5 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yokohamatriennale.jp main page is 2.5 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.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 38.9 kB

  • Original 47.0 kB
  • After minification 44.4 kB
  • After compression 8.1 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 38.9 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 80.4 kB

  • Original 2.2 MB
  • After minification 2.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. Yokohamatriennale images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 84.5 kB

  • Original 197.1 kB
  • After minification 187.6 kB
  • After compression 112.6 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 84.5 kB or 43% of the original size.

CSS Optimization

-84%

Potential reduce by 51.5 kB

  • Original 61.4 kB
  • After minification 49.3 kB
  • After compression 9.8 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. Yokohamatriennale.jp needs all CSS files to be minified and compressed as it can save up to 51.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (41%)

Requests Now

104

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yokohamatriennale.jp

yokohamatriennale.jp

791 ms

reset.css

reset.css

393 ms

fonts-min.css

fonts-min.css

395 ms

default.css

default.css

394 ms

frame.css

frame.css

589 ms

index.css

index.css

401 ms

jquery.min.js

jquery.min.js

13 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

576 ms

respond.min.js

respond.min.js

772 ms

jquery.protect.js

jquery.protect.js

775 ms

common.js

common.js

774 ms

index.js

index.js

790 ms

smindex.js

smindex.js

956 ms

jquery-fontsize-switcher.css

jquery-fontsize-switcher.css

979 ms

switch.js

switch.js

1164 ms

jquery.cookie.js

jquery.cookie.js

1165 ms

colorChange.js

colorChange.js

1173 ms

colorChange.css

colorChange.css

1185 ms

retina.js

retina.js

1194 ms

head_size_small_off.png

head_size_small_off.png

291 ms

head_size_small_on.png

head_size_small_on.png

404 ms

head_size_mid_off.png

head_size_mid_off.png

470 ms

head_size_mid_on.png

head_size_mid_on.png

468 ms

head_size_large_off.png

head_size_large_off.png

469 ms

head_size_large_on.png

head_size_large_on.png

575 ms

head_color_nomal_off.png

head_color_nomal_off.png

600 ms

head_color_nomal_on.png

head_color_nomal_on.png

772 ms

head_color_black_off.png

head_color_black_off.png

795 ms

head_color_black_on.png

head_color_black_on.png

794 ms

title_yokohamatriennale.png

title_yokohamatriennale.png

804 ms

sm_slide05.jpg

sm_slide05.jpg

1747 ms

sm_btn_arrow.png

sm_btn_arrow.png

988 ms

sm_text_2014.png

sm_text_2014.png

1152 ms

sm_slide01.jpg

sm_slide01.jpg

1591 ms

sm_slide02.jpg

sm_slide02.jpg

2394 ms

sm_slide03.jpg

sm_slide03.jpg

2406 ms

sm_slide04.jpg

sm_slide04.jpg

2394 ms

sm_text_2011.png

sm_text_2011.png

1550 ms

sm_text_2008.png

sm_text_2008.png

1950 ms

sm_text_2005.png

sm_text_2005.png

1980 ms

sm_text_2001.png

sm_text_2001.png

2135 ms

cse.js

cse.js

46 ms

background.jpg

background.jpg

3546 ms

btn_arrow.png

btn_arrow.png

2354 ms

topslideTitle05.png

topslideTitle05.png

2519 ms

topslideTitle04.gif

topslideTitle04.gif

2744 ms

topslideTitle03.png

topslideTitle03.png

2784 ms

topslideTitle02.png

topslideTitle02.png

2785 ms

topslideTitle01.png

topslideTitle01.png

2778 ms

topslideCPhoto05.png

topslideCPhoto05.png

3888 ms

topslideCPhoto01.png

topslideCPhoto01.png

4083 ms

topslideCPhoto02.png

topslideCPhoto02.png

3989 ms

topslideCPhoto03.png

topslideCPhoto03.png

4031 ms

topslideCPhoto04.png

topslideCPhoto04.png

4020 ms

cse.js

cse.js

48 ms

bg_head.jpg

bg_head.jpg

3890 ms

cse.js

cse.js

82 ms

widgets.js

widgets.js

98 ms

cse.js

cse.js

60 ms

jsapi

jsapi

143 ms

ga.js

ga.js

92 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

224 ms

bt_twitter.gif

bt_twitter.gif

4016 ms

default+ja.css

default+ja.css

32 ms

default.css

default.css

54 ms

default+ja.I.js

default+ja.I.js

58 ms

like.php

like.php

249 ms

bt_facebook.gif

bt_facebook.gif

4043 ms

__utm.gif

__utm.gif

27 ms

default.css

default.css

59 ms

async-ads.js

async-ads.js

94 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

70 ms

head_language_en.png

head_language_en.png

3941 ms

small-logo.png

small-logo.png

19 ms

search_box_icon.png

search_box_icon.png

15 ms

clear.png

clear.png

17 ms

head_language_ch.png

head_language_ch.png

3961 ms

head_language_hg.png

head_language_hg.png

3972 ms

head_size.png

head_size.png

4031 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

549 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

613 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

46 ms

head_color.png

head_color.png

4113 ms

sm_head_menu.png

sm_head_menu.png

4117 ms

jot

jot

83 ms

sm_head_home.png

sm_head_home.png

4027 ms

newstopics_title.png

newstopics_title.png

4032 ms

newsLinlBt.gif

newsLinlBt.gif

4034 ms

news_move_down_bt.gif

news_move_down_bt.gif

4094 ms

footer_icon_twitter.png

footer_icon_twitter.png

4080 ms

footer_icon_facebook.png

footer_icon_facebook.png

3944 ms

footer_icon_youtube.png

footer_icon_youtube.png

3636 ms

bnr_footer01.jpg

bnr_footer01.jpg

3820 ms

bnr_footer04.jpg

bnr_footer04.jpg

3480 ms

bnr_footer03.png

bnr_footer03.png

3345 ms

bnr_footer05.jpg

bnr_footer05.jpg

3484 ms

bnr_footer02.png

bnr_footer02.png

3356 ms

head_press.png

head_press.png

3203 ms

head_mailnews.png

head_mailnews.png

3234 ms

gnavi_logo.gif

gnavi_logo.gif

3292 ms

gnavi_news.gif

gnavi_news.gif

3395 ms

gnavi_about.gif

gnavi_about.gif

3319 ms

gnavi_archive.gif

gnavi_archive.gif

3130 ms

gnavi_support.gif

gnavi_support.gif

3169 ms

gnavi_international.gif

gnavi_international.gif

3222 ms

gnavi_contact.gif

gnavi_contact.gif

3273 ms

footer_logo.png

footer_logo.png

2627 ms

blank.gif

blank.gif

2349 ms

Accessibility Review

yokohamatriennale.jp accessibility score

85

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

yokohamatriennale.jp best practices score

67

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

SEO Factors

yokohamatriennale.jp SEO score

73

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

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

yokohamatriennale.jp

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