8.6 sec in total
425 ms
7.9 sec
239 ms
Visit jaot.or.jp now to see the best up-to-date Jaot content for Japan and also check out these interesting facts you probably never knew about jaot.or.jp
一般社団法人日本作業療法士協会は、作業療法士の学術・技能の研鑽及び人格の陶冶に努め、作業療法の普及発展を図り、もって国民の健康と福祉の向上に資することを目的とした事業を行っています。
Visit jaot.or.jpWe analyzed Jaot.or.jp page load time and found that the first response time was 425 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jaot.or.jp performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value27.1 s
0/100
25%
Value15.7 s
0/100
10%
Value350 ms
73/100
30%
Value0.591
11/100
15%
Value16.3 s
5/100
10%
425 ms
859 ms
1145 ms
58 ms
1256 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 70% of them (49 requests) were addressed to the original Jaot.or.jp, 9% (6 requests) were made to Google.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Jaot.or.jp.
Page size can be reduced by 870.6 kB (24%)
3.6 MB
2.7 MB
In fact, the total size of Jaot.or.jp main page is 3.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. 65% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 37.7 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 7.3 kB, which is 15% 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 37.7 kB or 78% of the original size.
Potential reduce by 168.9 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. Jaot images are well optimized though.
Potential reduce by 301.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 301.8 kB or 52% of the original size.
Potential reduce by 362.3 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. Jaot.or.jp needs all CSS files to be minified and compressed as it can save up to 362.3 kB or 83% of the original size.
Number of requests can be reduced by 27 (42%)
65
38
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jaot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
jaot.or.jp
425 ms
jaot.or.jp
859 ms
www.jaot.or.jp
1145 ms
gtm.js
58 ms
styles.css
1256 ms
index.css
609 ms
import.js
630 ms
cse.js
48 ms
widgets.js
93 ms
font-awesome.min.css
32 ms
jquery-ui.min.css
28 ms
console.js
219 ms
jquery-3.3.1.min.js
608 ms
jquery.matchHeight-min.js
217 ms
jquery.resizeend.min.js
432 ms
slick.min.js
438 ms
jquery-ui.min.js
1623 ms
jquery.ui.datepicker-ja.min.js
620 ms
jquery.jpostal.js
822 ms
modules.js
641 ms
common.js
650 ms
header_logo.png
237 ms
ot%20web_sk2_nintisyo_banner_top_up_240319.jpg
1012 ms
notosaigai.jpg
846 ms
OT_Rotation_Banner.gif
622 ms
ot_day_2022.jpg
1033 ms
ot_web-ah-02_200810.jpg
1638 ms
mainImage01.jpg
859 ms
ot-web_line_banner_top_kaitei_up_220202.jpg
1463 ms
%E3%82%AA%E3%83%BC%E3%83%86%E3%82%A3%E3%81%8F%E3%82%93%E3%81%A8%E5%AD%A6%E3%81%B6%E4%BD%9C%E6%A5%AD%E7%99%82%E6%B3%95%E8%A6%8B%E5%AD%A6%E3%83%84%E3%82%A2%E3%83%BC%EF%BD%971200-%EF%BD%88265.jpg
1470 ms
topNews_icon01.png
1077 ms
topNews_icon02.png
1218 ms
topNews_icon03.png
1238 ms
news_ot-web_srh_thumbnail_w780-h585_up_220711_jpg_w200px_h150px.jpg
1290 ms
news_kouhou_ot_otikun_p_hyo1_50_png_w94px_h200px.png
1423 ms
news_kouhou_OT_PR2024_Thumbnail_gif_w200px_h150px.gif
1445 ms
%E3%82%AA%E3%83%BC%E3%83%86%E3%82%A3%E3%81%8F%E3%82%93%E3%81%AE%E3%81%8E%E3%82%82%E3%82%93_w780-h585_up_221128_jpg_w200px_h150px.jpg
1500 ms
ot-web_sk2_nintisyo_thumbnail_up_240319_jpg_w200px_h150px.jpg
1626 ms
footer_logo.png
1649 ms
footer_sns01.png
1668 ms
footer_sns02.png
1683 ms
footer_sns03.png
1712 ms
pageTop.png
1831 ms
cse_element__ja.js
24 ms
default+ja.css
48 ms
default.css
49 ms
fix_icon.png
1780 ms
mainImage_bg.png
1791 ms
topHr_titleBg.png
1813 ms
topNews_icon01on.png
1829 ms
topNews_icon02on.png
1861 ms
topNews_icon03on.png
1972 ms
topHr_titleBg02.png
1989 ms
share_button.php
119 ms
async-ads.js
90 ms
branding.png
86 ms
clear.png
55 ms
nav_logo114.png
54 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
98 ms
ajax-loader.gif
1847 ms
arrow_prev.png
1873 ms
arrow_next.png
1892 ms
fontawesome-webfont.woff
16 ms
slick.woff
1920 ms
V0uGDvjjhVE.js
43 ms
Lqbp5nhLL1h.png
39 ms
settings
74 ms
button.856debeac157d9669cf51e73a08fbc93.js
23 ms
embeds
21 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html
33 ms
jaot.or.jp 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-hidden="true"] elements contain focusable descendents
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
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
jaot.or.jp 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
jaot.or.jp 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 Jaot.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 Jaot.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.
jaot.or.jp
Open Graph data is detected on the main page of Jaot. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: