5.7 sec in total
547 ms
4.9 sec
257 ms
Welcome to sodo.or.jp homepage info - get ready to check Sodo best content right away, or after learning these important things about sodo.or.jp
着付けを装道では着装と言います。着付け教室の一歩先をいく装道礼法きもの学院は東京本校をはじめ、仙台校・名古屋校・大阪校・広島校・福岡校・認可教室など全国各地で、きもの・礼法を学ぶことができ、公益社団法人発行の資格取得も可能です。お稽古・習い事・社員研修等にもご活用下さい。
Visit sodo.or.jpWe analyzed Sodo.or.jp page load time and found that the first response time was 547 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sodo.or.jp performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value23.0 s
0/100
25%
Value21.1 s
0/100
10%
Value140 ms
96/100
30%
Value0.346
32/100
15%
Value24.1 s
0/100
10%
547 ms
1269 ms
344 ms
24 ms
359 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 66% of them (73 requests) were addressed to the original Sodo.or.jp, 13% (14 requests) were made to Static.xx.fbcdn.net and 10% (11 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Sodo.or.jp.
Page size can be reduced by 190.9 kB (12%)
1.6 MB
1.4 MB
In fact, the total size of Sodo.or.jp main page is 1.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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 17.9 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 4.0 kB, which is 17% 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 17.9 kB or 76% of the original size.
Potential reduce by 116.5 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. Sodo images are well optimized though.
Potential reduce by 47.4 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 47.4 kB or 48% of the original size.
Potential reduce by 9.1 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. Sodo.or.jp needs all CSS files to be minified and compressed as it can save up to 9.1 kB or 76% of the original size.
Number of requests can be reduced by 27 (25%)
106
79
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sodo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
sodo.or.jp
547 ms
www.sodo.or.jp
1269 ms
import.css
344 ms
jquery.min.js
24 ms
rollover.js
359 ms
scrollsmoothly.js
547 ms
scrolltopcontrol.js
370 ms
fancybox.js
963 ms
function.js
510 ms
jquery.easing.1.3.js
521 ms
jquery.bxSlider.min.js
711 ms
base.css
215 ms
common.css
341 ms
fancybox.css
357 ms
style.css
388 ms
clear.css
400 ms
kkp_client.js
507 ms
conversion.js
18 ms
logo.png
179 ms
header_tel.png
187 ms
header_btn04.png
172 ms
header_btn05.png
195 ms
header_btn01.png
183 ms
side_nav01.png
356 ms
side_nav02.png
510 ms
side_nav03.png
355 ms
side_nav04.png
552 ms
side_nav06.png
555 ms
side_nav07.png
386 ms
side_nav08.png
530 ms
side_nav09.png
534 ms
side_nav10.png
617 ms
side_banner01.png
849 ms
side_banner02.png
881 ms
side_banner03.png
889 ms
main.png
1454 ms
ttl01.png
742 ms
top_btn01.png
770 ms
top_btn02.png
925 ms
top_btn03.png
963 ms
top_btn05.png
1018 ms
top_btn06.png
1056 ms
top_btn07.png
1065 ms
ttl02.png
1111 ms
camp_banner_n20160210-1.png
1346 ms
camp_banner_n20160210-2.png
1355 ms
ttl03.png
1232 ms
sub01.png
1242 ms
th01.png
1296 ms
sub02.png
1408 ms
th02.png
1420 ms
sub03.png
1481 ms
th03.png
1633 ms
sdk.js
272 ms
sub04.png
1558 ms
ga.js
8 ms
kkp_S001041_client.js
189 ms
__utm.gif
13 ms
th04.png
1470 ms
sub05.png
1465 ms
th05.png
1461 ms
sub06.png
1490 ms
th06.png
1514 ms
66 ms
xd_arbiter.php
235 ms
xd_arbiter.php
439 ms
ttl04.png
1386 ms
more.png
1417 ms
fot_banner01.png
1398 ms
fot_banner02.png
1314 ms
fot_banner03.png
1330 ms
fot_banner04.png
1342 ms
footer_ttl.png
1380 ms
footer_nav01.png
1391 ms
50 ms
footer_nav03.png
1345 ms
41 ms
page.php
281 ms
footer_nav04.png
1260 ms
footer_nav05.png
1275 ms
footer_nav06.png
1200 ms
footer_nav07.png
1242 ms
footer_nav08.png
1233 ms
KHRiJR32lob.css
286 ms
tnnkjvk5cNK.css
357 ms
q68gy-v_YMF.js
557 ms
k19Xse48j5I.js
620 ms
ihptErjAmMX.js
577 ms
3So47A9WcrL.js
492 ms
cUsKAwzqrQw.js
636 ms
arrow.png
1212 ms
pagetop.png
1221 ms
76327_476562142391970_2044589352_n.png
489 ms
11040635_880478678666979_962347617814811354_n.jpg
550 ms
10888511_583392418464369_2752521994816178954_n.jpg
620 ms
12814704_119156218478055_8439093720830629747_n.jpg
692 ms
12650914_708973829239138_4208100821958709920_n.jpg
768 ms
12400498_1672406222999620_4891243732737737571_n.jpg
689 ms
11143725_880475942000586_4724876533724720252_n.jpg
688 ms
11403494_880472075334306_8993880188044091781_n.jpg
685 ms
11665714_880464095335104_401495338067193806_n.jpg
690 ms
10298912_879965265384987_1410417412622994479_n.jpg
755 ms
11040635_880478678666979_962347617814811354_n.jpg
754 ms
wL6VQj7Ab77.png
73 ms
s7jcwEQH7Sx.png
72 ms
GtIpNnEyqq_.png
73 ms
R9a_DtVRZgv.js
70 ms
cUDgRFxaoIk.js
71 ms
0JBr1QHp8Gi.js
74 ms
kDOzhTr2W91.js
72 ms
sodo.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.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
sodo.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
sodo.or.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sodo.or.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Sodo.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.
sodo.or.jp
Open Graph description is not detected on the main page of Sodo. 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: