38 sec in total
634 ms
24.1 sec
13.2 sec
Visit psychodoc.eek.jp now to see the best up-to-date Psychodoc Eek content for Japan and also check out these interesting facts you probably never knew about psychodoc.eek.jp
精神科医のほのぼの日記(嘘)
Visit psychodoc.eek.jpWe analyzed Psychodoc.eek.jp page load time and found that the first response time was 634 ms and then it took 37.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
psychodoc.eek.jp performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value4.4 s
40/100
25%
Value14.5 s
1/100
10%
Value140 ms
96/100
30%
Value0.014
100/100
15%
Value19.4 s
3/100
10%
634 ms
2258 ms
509 ms
911 ms
1035 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 20% of them (31 requests) were addressed to the original Psychodoc.eek.jp, 12% (19 requests) were made to Ecx.images-amazon.com and 10% (15 requests) were made to Lh4.ggpht.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Bloglines.com.
Page size can be reduced by 222.0 kB (77%)
289.1 kB
67.1 kB
In fact, the total size of Psychodoc.eek.jp main page is 289.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 168.7 kB which makes up the majority of the site volume.
Potential reduce by 79.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. 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 79.7 kB or 72% of the original size.
Potential reduce by 101 B
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. Psychodoc Eek images are well optimized though.
Potential reduce by 142.1 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 142.1 kB or 84% of the original size.
Number of requests can be reduced by 36 (25%)
142
106
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Psychodoc Eek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
psychodoc.eek.jp
634 ms
2258 ms
base.css
509 ms
blue-dash.css
911 ms
HatenaStar.js
1035 ms
badge.js
25 ms
410459802X.09.TZZZZZZZ.jpg
391 ms
go-button.gif
386 ms
sub_modern5.gif
20191 ms
recenttracks_regular_blue.png
1626 ms
b_entry_de.gif
587 ms
513J6fp86TL._SL75_.jpg
359 ms
maps
353 ms
R0010774.JPG
364 ms
R0010397.JPG
359 ms
R0010399.JPG
372 ms
R0010459.JPG
392 ms
R0010667.JPG
366 ms
R0010555.JPG
531 ms
R0010550.JPG
397 ms
R0010635.JPG
477 ms
R0010641.JPG
502 ms
blue.png
1267 ms
blue.png
1376 ms
jp_searchbox.gif
792 ms
rss.gif
758 ms
append.gif
503 ms
ha_b.png
1770 ms
20100928_0.jpg
1530 ms
20100928_1.jpg
2375 ms
20100928_2.jpg
6568 ms
20100928_3.jpg
4186 ms
20100928_4.jpg
10424 ms
20100928_5.jpg
1991 ms
20100928_6.jpg
2910 ms
20100928_7.jpg
3672 ms
20100928_8.jpg
2947 ms
20100928_9.jpg
7088 ms
20100928_10.jpg
3186 ms
20100925_0.jpg
3372 ms
20100925_1.jpg
3531 ms
20100925_2.jpg
3699 ms
20100925_3.jpg
4270 ms
20100925_4.jpg
4456 ms
20100925_5.jpg
7095 ms
20100925_6.jpg
4845 ms
20100925_7.jpg
6865 ms
20100925_8.jpg
5290 ms
20100925_9.jpg
7247 ms
20100921_0.jpg
8890 ms
51HP5Y7FNZL._SL75_.jpg
309 ms
513uXMFhPFL._SL75_.jpg
310 ms
51VYMWNZ6GL.jpg
315 ms
41YX9TSHCHL.jpg
310 ms
51LDL7eJqtL.jpg
318 ms
512JQCBGT5L.jpg
314 ms
51PFu6SgfYL.jpg
319 ms
51U1p2Amu5L.jpg
309 ms
51YM7FXC78L.jpg
340 ms
51BPDM9A97L.jpg
525 ms
51GrS-xV30L.jpg
339 ms
51R4585BFDL.jpg
318 ms
51yfVSnXwbL.jpg
353 ms
51wbOqfz47L.jpg
349 ms
51SzDDaD3DL.jpg
342 ms
51cUgIszAfL.jpg
360 ms
51ZZgG8XVML.jpg
365 ms
51MdLmrVAYL.jpg
428 ms
R0010406.JPG
321 ms
R0010661.JPG
648 ms
R0010670.JPG
348 ms
R0010547.JPG
334 ms
R0010580.JPG
374 ms
R0010573.JPG
503 ms
R0010476.JPG
614 ms
R0010401.JPG
312 ms
R0010438.JPG
304 ms
R0010971.JPG
313 ms
R0010970.JPG
332 ms
R0010655.JPG
367 ms
R0010676.JPG
515 ms
R0010680.JPG
497 ms
R0010557.JPG
544 ms
R0010558.JPG
491 ms
R0010565.JPG
640 ms
R0010587.JPG
595 ms
R0010632.JPG
764 ms
R0010636.JPG
935 ms
R0010639.JPG
712 ms
R0010457.JPG
309 ms
R0010446.JPG
305 ms
R0010445.JPG
513 ms
R0010974.JPG
414 ms
R0010672.JPG
415 ms
R0010527.JPG
440 ms
R0010538.JPG
555 ms
R0010540.JPG
603 ms
R0010578.JPG
527 ms
R0010551.JPG
703 ms
R0010574.JPG
835 ms
embed
736 ms
00020.gif
34 ms
00084.gif
419 ms
00007.gif
11 ms
00004.gif
35 ms
00008.gif
40 ms
00004.gif
29 ms
00001.gif
13 ms
00001.gif
25 ms
js
78 ms
init_embed.js
48 ms
00000.gif
9 ms
00001.gif
17 ms
common.js
78 ms
map.js
150 ms
google4.png
93 ms
overlay.js
90 ms
util.js
193 ms
onion.js
191 ms
search_impl.js
194 ms
StaticMapService.GetMapImage
410 ms
stats.js
80 ms
openhand_8_8.cur
112 ms
ViewportInfoService.GetViewportInfo
112 ms
ViewportInfoService.GetViewportInfo
110 ms
kh
101 ms
transparent.png
55 ms
kh
187 ms
controls.js
80 ms
kh
74 ms
kh
126 ms
kh
183 ms
kh
221 ms
kh
221 ms
vt
305 ms
vt
308 ms
vt
160 ms
vt
296 ms
vt
306 ms
vt
296 ms
vt
294 ms
vt
485 ms
vt
751 ms
css
228 ms
entity11.png
97 ms
mapcnt6.png
100 ms
tmapctrl.png
134 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
368 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
399 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
430 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
459 ms
AuthenticationService.Authenticate
55 ms
QuotaService.RecordEvent
35 ms
add.gif
475 ms
entries.json
578 ms
comment.gif
464 ms
psychodoc.eek.jp accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
<object> elements do not have [alt] text
psychodoc.eek.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
psychodoc.eek.jp SEO score
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
Document uses plugins
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Psychodoc.eek.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 Psychodoc.eek.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
psychodoc.eek.jp
Open Graph description is not detected on the main page of Psychodoc Eek. 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: