4.6 sec in total
479 ms
4 sec
112 ms
Click here to check amazing Yebizo content for Japan. Otherwise, check out these important facts you probably never knew about yebizo.com
恵比寿映像祭は約2週間にわたり、展示、上映、ライヴ・パフォーマンス、関連イヴェントなどによって複合的に構成する、映像とアートの国際フェスティヴァルです。
Visit yebizo.comWe analyzed Yebizo.com page load time and found that the first response time was 479 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
yebizo.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value13.6 s
0/100
25%
Value14.4 s
1/100
10%
Value2,810 ms
3/100
30%
Value0
100/100
15%
Value13.0 s
13/100
10%
479 ms
729 ms
25 ms
37 ms
692 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 91% of them (41 requests) were addressed to the original Yebizo.com, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Yebizo.com.
Page size can be reduced by 165.5 kB (52%)
319.2 kB
153.7 kB
In fact, the total size of Yebizo.com main page is 319.2 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. Only 10% of websites need less resources to load. Javascripts take 161.5 kB which makes up the majority of the site volume.
Potential reduce by 6.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. 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 6.6 kB or 66% of the original size.
Potential reduce by 38.3 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. Obviously, Yebizo needs image optimization as it can save up to 38.3 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 101.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 101.9 kB or 63% of the original size.
Potential reduce by 18.6 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. Yebizo.com needs all CSS files to be minified and compressed as it can save up to 18.6 kB or 82% of the original size.
Number of requests can be reduced by 20 (47%)
43
23
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yebizo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
yebizo.com
479 ms
www.yebizo.com
729 ms
css
25 ms
css
37 ms
common.css
692 ms
2016.css
353 ms
jquery-ui-1.8.5.custom.css
537 ms
jquery-1.4.2.min.js
1365 ms
jquery-ui-1.8.5.custom.min.js
937 ms
jquery.easing.1.3.js
576 ms
jquery.history.js
707 ms
base.js
713 ms
menus.js
955 ms
main.js
1034 ms
swfobject-2.2.js
1061 ms
ga.js
5 ms
ymenu_0.png
204 ms
hmenu.xml
198 ms
ymenu.xml
195 ms
xhtml_top.xml
175 ms
ymenu_1.png
198 ms
ymenu_3.png
198 ms
ymenu_5.png
347 ms
ymenu_7.png
355 ms
arrow.png
356 ms
ymenu_9.png
378 ms
ymenu_10.png
379 ms
ymenu_12.png
387 ms
omenu_5.png
518 ms
omenu_0.png
530 ms
omenu_1.png
535 ms
omenu_2.png
566 ms
omenu_3.png
567 ms
smenu_2.png
581 ms
smenu_3.png
689 ms
smenu_4.png
707 ms
smenu_0.png
715 ms
smenu_1.png
755 ms
englishTitle.gif
756 ms
__utm.gif
10 ms
8th.png
606 ms
teaser-info.png
1382 ms
btn-info.png
876 ms
spacer.gif
707 ms
diagonal_blk.gif
757 ms
yebizo.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yebizo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
yebizo.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yebizo.com 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 Yebizo.com 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.
yebizo.com
Open Graph data is detected on the main page of Yebizo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: