20.7 sec in total
4.5 sec
15.8 sec
299 ms
Click here to check amazing COMMU DE content for Israel. Otherwise, check out these important facts you probably never knew about commude.co.jp
コミュニケーション・デザインを略して、コムデ。「思いを伝え、受け取ること」を「最も適した形で表現」します。コムデは東京のWeb制作会社です。
Visit commude.co.jpWe analyzed Commude.co.jp page load time and found that the first response time was 4.5 sec and then it took 16.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
commude.co.jp performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value22.2 s
0/100
25%
Value19.9 s
0/100
10%
Value760 ms
39/100
30%
Value1
2/100
15%
Value21.2 s
1/100
10%
4539 ms
1226 ms
1164 ms
1241 ms
708 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 72% of them (44 requests) were addressed to the original Commude.co.jp, 23% (14 requests) were made to Wp-tech.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.5 sec) belongs to the original domain Commude.co.jp.
Page size can be reduced by 901.7 kB (28%)
3.2 MB
2.3 MB
In fact, the total size of Commude.co.jp main page is 3.2 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. 30% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 35.2 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 10.0 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 35.2 kB or 79% of the original size.
Potential reduce by 580.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. Obviously, COMMU DE needs image optimization as it can save up to 580.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 157.0 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 157.0 kB or 65% of the original size.
Potential reduce by 128.9 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. Commude.co.jp needs all CSS files to be minified and compressed as it can save up to 128.9 kB or 90% of the original size.
Number of requests can be reduced by 13 (22%)
60
47
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of COMMU DE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.commude.co.jp
4539 ms
style.css
1226 ms
animate.css
1164 ms
jquery-1.11.1.min.js
1241 ms
jquery.textarea-autosize.js
708 ms
common.js
756 ms
heightLine.js
1011 ms
jquery.cookie.min.js
48 ms
placeholder.js
1405 ms
owl.carousel.min.js
1767 ms
owl.carousel.css
1674 ms
jquery.lazyload.min.js
1746 ms
slick.css
1379 ms
slick.min.js
1918 ms
wp-emoji-release.min.js
791 ms
icat_editor1.png
1303 ms
editor01.png
1050 ms
editor02.png
1057 ms
thmbnail-tablepress.png
1252 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-02-08-10.46.591-e1454896513117-300x213.png
1082 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-02-08-9.50.411.png
1886 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-01-14.50.12.png
1744 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-01-15.19.52.png
1609 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-01-15.23.55.png
2199 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-01-17.22.50.png
1803 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-01-17.31.05.png
1617 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-01-17.54.38.png
1969 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-01-17.58.43.png
2097 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-01-18.04.03.png
2091 ms
header_logo_commude.png
649 ms
commude_education.svg
549 ms
commude_original.svg
557 ms
commude_application.svg
555 ms
commude_web.svg
992 ms
thumb_wptech.png
1409 ms
thumb_okilabo.png
1430 ms
tvos.png
1623 ms
case_rakuden.png
1809 ms
case_entameZukan.png
2111 ms
case_ar.png
2279 ms
case_leadaLIfe.png
2611 ms
case_shujoPrime.png
2854 ms
case_tsumugiViewer.png
2794 ms
case_premiumJapan.png
3396 ms
bnr_okirabo.png
3048 ms
bnr_wptech.png
3115 ms
bnr_tsumugi.png
3477 ms
bnr_some.png
3672 ms
logo_commude.svg
3374 ms
sitemap_arrow.png
3950 ms
sp_footer_pagetop.png
3666 ms
NotoSansCJKjp-Light.woff
5336 ms
NotoSansCJKjp-Thin.woff
5656 ms
NotoSansCJKjp-DemiLight.woff
5536 ms
NotoSansCJKjp-Regular.woff
5702 ms
NotoSansCJKjp-Medium.woff
5889 ms
NotoSansCJKjp-Bold.woff
5965 ms
NotoSansCJKjp-Black.woff
7533 ms
myfont.woff
6112 ms
analytics.js
68 ms
collect
43 ms
commude.co.jp accessibility score
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
commude.co.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
commude.co.jp 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
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 Commude.co.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 Commude.co.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.
commude.co.jp
Open Graph description is not detected on the main page of COMMU DE. 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: