6.3 sec in total
339 ms
5.7 sec
258 ms
Click here to check amazing Ocha content for Japan. Otherwise, check out these important facts you probably never knew about ocha.tv
お茶百科-お茶と歩む文化、お茶と暮らす場所、お茶を楽しむ人のために。お茶に関する情報を提供。
Visit ocha.tvWe analyzed Ocha.tv page load time and found that the first response time was 339 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ocha.tv performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value12.2 s
0/100
25%
Value13.4 s
2/100
10%
Value2,260 ms
6/100
30%
Value1.719
0/100
15%
Value22.9 s
1/100
10%
339 ms
674 ms
859 ms
169 ms
337 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 95% of them (88 requests) were addressed to the original Ocha.tv, 2% (2 requests) were made to Connect.facebook.net and 1% (1 request) were made to Rsv.dga.jp. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ocha.tv.
Page size can be reduced by 323.8 kB (11%)
2.9 MB
2.5 MB
In fact, the total size of Ocha.tv main page is 2.9 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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 24.3 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 6.7 kB, which is 22% 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 24.3 kB or 81% of the original size.
Potential reduce by 54.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. Ocha images are well optimized though.
Potential reduce by 165.8 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 165.8 kB or 77% of the original size.
Potential reduce by 79.5 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. Ocha.tv needs all CSS files to be minified and compressed as it can save up to 79.5 kB or 90% of the original size.
Number of requests can be reduced by 15 (17%)
90
75
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ocha. 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 5 to 1 for CSS and as a result speed up the page load time.
ocha.tv
339 ms
ocha.tv
674 ms
www.ocha.tv
859 ms
reset.css
169 ms
common.css
337 ms
layout.css
662 ms
index.css
665 ms
logo.png
498 ms
logo-itoen.co.jp.png
500 ms
nav-1.png
501 ms
nav-2.png
502 ms
nav-3.png
686 ms
nav-4.png
687 ms
nav-5.png
686 ms
nav-6.png
687 ms
visual-logo.png
822 ms
visual-logo-itoen.co.jp.png
828 ms
visual-scrolldown.png
831 ms
visual-1-pc.jpg
1328 ms
visual-1-sp.jpg
1167 ms
visual-2-pc.jpg
1337 ms
visual-2-sp.jpg
1315 ms
visual-3-pc.jpg
1492 ms
visual-3-sp.jpg
1494 ms
category-1-1-pc.png
1500 ms
category-1-1-sp.png
1809 ms
category-1-2-pc.png
1661 ms
category-1-2-sp.png
1673 ms
category-1-3-pc.png
1661 ms
category-1-3-sp.png
1991 ms
category-2-1.jpg
1666 ms
category-2-2.jpg
1830 ms
category-2-3.jpg
1827 ms
category-2-4.jpg
1833 ms
category-2-5.jpg
1841 ms
category-2-6.jpg
1975 ms
category-2-7.jpg
1995 ms
category-2-8.jpg
1996 ms
slick.css
1999 ms
jquery-1.7.2.min.js
1854 ms
jquery.easing.1.3.js
1814 ms
device.js
1667 ms
jquery-match-height.js
1668 ms
drawermenu.js
1670 ms
class-control.js
1674 ms
hash.scroll.js
1527 ms
slick.js
1793 ms
category-2-9.jpg
1645 ms
category-2-10.jpg
1648 ms
category-3-1.png
1649 ms
category-3-2.png
1656 ms
category-3-3.png
1531 ms
category-3-4.png
1685 ms
category-3-5.png
1682 ms
category-7.jpg
1345 ms
category-4.jpg
1199 ms
category-5.jpg
1193 ms
category-6.jpg
1305 ms
icon-facebook.png
1173 ms
icon-twitter.png
1173 ms
icon-line.png
1169 ms
menu-1.png
1020 ms
menu-2.png
1026 ms
menu-3.png
1139 ms
menu-4.png
1160 ms
menu-5.png
1023 ms
menu-6.png
1007 ms
menu-7.png
1019 ms
visual-search-button.png
1023 ms
category-header-top-2.png
1128 ms
category-header-bottom-2.png
1024 ms
bg-1.jpg
1172 ms
bg-2.jpg
1006 ms
bg-3.jpg
1020 ms
icon-category-2.png
1024 ms
icon-category-2.png
1114 ms
icon-category-2.png
1025 ms
icon-category-2.png
1012 ms
icon-arrow-2-up.png
1021 ms
icon-blank-1.png
1031 ms
icon-blank-2.png
1127 ms
icon-arrow-2-right.png
1150 ms
search_tool_n3.js
1325 ms
nav-1.png
835 ms
nav-1-current.png
843 ms
nav-2.png
857 ms
nav-2-current.png
867 ms
nav-3.png
968 ms
sdk.js
18 ms
gtm.js
74 ms
nav-3-current.png
990 ms
sdk.js
6 ms
36 ms
ocha.tv accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
Form elements do not have associated labels
ocha.tv best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
ocha.tv SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Ocha.tv 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 Ocha.tv 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.
ocha.tv
Open Graph data is detected on the main page of Ocha. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: