9.1 sec in total
1.8 sec
4.3 sec
3 sec
Visit dounokouno.com now to see the best up-to-date Dounokouno content for Japan and also check out these interesting facts you probably never knew about dounokouno.com
名古屋市のWeb系プログラマーdounokounoのブログ。運営サービスの更新情報や技術メモ、趣味や生活の知恵など様々な情報を発信しています
Visit dounokouno.comWe analyzed Dounokouno.com page load time and found that the first response time was 1.8 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
dounokouno.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value12.6 s
0/100
25%
Value10.8 s
6/100
10%
Value530 ms
55/100
30%
Value0.075
95/100
15%
Value12.1 s
16/100
10%
1840 ms
480 ms
347 ms
555 ms
380 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 16% of them (16 requests) were addressed to the original Dounokouno.com, 44% (43 requests) were made to Ecx.images-amazon.com and 8% (8 requests) were made to Farm1.staticflickr.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Dounokouno.com.
Page size can be reduced by 383.7 kB (23%)
1.7 MB
1.3 MB
In fact, the total size of Dounokouno.com main page is 1.7 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 152.0 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 152.0 kB or 83% of the original size.
Potential reduce by 13.7 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. Dounokouno images are well optimized though.
Potential reduce by 153.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 153.4 kB or 52% of the original size.
Potential reduce by 64.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. Dounokouno.com needs all CSS files to be minified and compressed as it can save up to 64.6 kB or 84% of the original size.
Number of requests can be reduced by 25 (27%)
93
68
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dounokouno. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
dounokouno.com
1840 ms
wp-emoji-release.min.js
480 ms
widget.css
347 ms
crayon.min.css
555 ms
familiar.css
380 ms
monaco.css
398 ms
css
24 ms
style.css
915 ms
jquery.js
1136 ms
jquery-migrate.min.js
711 ms
crayon.min.js
917 ms
external-tracking.min.js
852 ms
adsbygoogle.js
4 ms
global.js
716 ms
wp-embed.min.js
897 ms
sdk.js
147 ms
analytics.js
145 ms
51sTuYFVYhL._SL160_.jpg
143 ms
22583411129_9855a6515c_z.jpg
832 ms
banner.jpg
1081 ms
cropped-01.jpg
1238 ms
buttons.png
910 ms
20121978899_a362761abe_z.jpg
718 ms
20314609291_b902d1c90a_z.jpg
811 ms
20120586980_309ea4a75e_z.jpg
1010 ms
20120587750_2cc92e80ec_z.jpg
808 ms
19687635013_5b17fefb5b_z.jpg
810 ms
20308612455_a66026e73a_z.jpg
908 ms
20300195022_1326c41f97_z.jpg
909 ms
41EIOdK8dBL._SL160_.jpg
119 ms
51McjcjRIGL._SL160_.jpg
121 ms
41KRHDqlaeL._SL160_.jpg
121 ms
41hyh6MQCHL._SL160_.jpg
119 ms
41b%2BYYXQrRL._SL160_.jpg
123 ms
51VskhTUWLL._SL160_.jpg
595 ms
51gUPmkIKVL._SL160_.jpg
121 ms
51T6uuBbOUL._SL160_.jpg
121 ms
518b3wDrh0L._SL160_.jpg
123 ms
31bmIterx6L._SL160_.jpg
123 ms
41wP%2Badt%2BOL._SL160_.jpg
124 ms
41pNvFcvnWL._SL160_.jpg
124 ms
51aEeRyEA-L._SL160_.jpg
123 ms
41RATYfT2RL._SL160_.jpg
124 ms
41VIQ4KrJ5L._SL160_.jpg
125 ms
41YurCgRmgL._SL160_.jpg
125 ms
41oZT12l75L._SL160_.jpg
125 ms
41gCHNGpmUL._SL160_.jpg
126 ms
51Vr9iPuslL._SL160_.jpg
592 ms
51TJ75M74ZL._SL160_.jpg
126 ms
41mjhi0oTGL._SL160_.jpg
125 ms
415Rpcjng2L._SL160_.jpg
126 ms
415OY0VSnJL._SL160_.jpg
590 ms
51nxlSDUA%2BL._SL160_.jpg
593 ms
511tsa%2Bea9L._SL160_.jpg
589 ms
51Lqe7ZGWHL._SL160_.jpg
590 ms
51g5tQ5mQRL._SL160_.jpg
594 ms
31o2iAK9dnL._SL160_.jpg
595 ms
41TDrksG2GL._SL160_.jpg
613 ms
51wDn1ccEyL._SL160_.jpg
594 ms
51neB7Mr0LL._SL160_.jpg
708 ms
31meGk9WU1L._SL160_.jpg
613 ms
41nSu56G8dL._SL160_.jpg
613 ms
41jELKceJHL._SL160_.jpg
613 ms
51XCKE2EEnL._SL160_.jpg
633 ms
412Gb3cxV4L._SL160_.jpg
598 ms
51S-u85CM8L._SL160_.jpg
522 ms
51rRhZDuCOL._SL160_.jpg
595 ms
41-1KKTtLGL._SL160_.jpg
594 ms
31PV0PLCodL._SL160_.jpg
560 ms
516BSORP0LL._SL160_.jpg
593 ms
41gashUMxKL._SL160_.jpg
686 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
584 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
679 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
776 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
776 ms
monaco-webfont.woff
1126 ms
645 ms
ca-pub-0137506408243442.js
635 ms
zrt_lookup.html
628 ms
show_ads_impl.js
504 ms
xd_arbiter.php
531 ms
xd_arbiter.php
723 ms
widgets.js
426 ms
collect
393 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
272 ms
ads
305 ms
osd.js
100 ms
5171746271700867932
43 ms
abg.js
52 ms
m_js_controller.js
63 ms
googlelogo_color_112x36dp.png
40 ms
syndication
133 ms
434848079221501953
191 ms
x_button_blue2.png
46 ms
s
26 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
6 ms
dounokouno.com 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
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
Form elements do not have associated labels
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>).
dounokouno.com 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
Browser errors were logged to the console
dounokouno.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 Dounokouno.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 Dounokouno.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.
dounokouno.com
Open Graph data is detected on the main page of Dounokouno. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: