8.8 sec in total
128 ms
8 sec
668 ms
Click here to check amazing Depressionrecover content for Japan. Otherwise, check out these important facts you probably never knew about depressionrecover.com
Visit depressionrecover.comWe analyzed Depressionrecover.com page load time and found that the first response time was 128 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
depressionrecover.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value5.2 s
24/100
25%
Value5.5 s
55/100
10%
Value1,040 ms
26/100
30%
Value0.104
89/100
15%
Value6.3 s
61/100
10%
128 ms
273 ms
225 ms
302 ms
104 ms
Our browser made a total of 214 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Depressionrecover.com, 7% (14 requests) were made to Ds.serving-sys.com and 6% (13 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Ajax-proxy.shinobi.jp.
Page size can be reduced by 327.3 kB (52%)
627.3 kB
300.0 kB
In fact, the total size of Depressionrecover.com main page is 627.3 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 367.5 kB which makes up the majority of the site volume.
Potential reduce by 73.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. 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 73.2 kB or 77% of the original size.
Potential reduce by 14.2 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, Depressionrecover needs image optimization as it can save up to 14.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 209.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 209.4 kB or 57% of the original size.
Potential reduce by 30.5 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. Depressionrecover.com needs all CSS files to be minified and compressed as it can save up to 30.5 kB or 67% of the original size.
Number of requests can be reduced by 133 (70%)
190
57
The browser has sent 190 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Depressionrecover. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
depressionrecover.com
128 ms
www.depressionrecover.com
273 ms
3375562265-css_bundle_v2.css
225 ms
authorization.css
302 ms
adsbygoogle.js
104 ms
4d354ad3e8041cadb78905d8014f4592
615 ms
jquery.min.js
59 ms
jquery.related-posts-widget-2.0.min.js
108 ms
5c743ad76f02093960aec92d19616b35
464 ms
57f09f57e732daf1d3d7259ee3ef02f0
474 ms
nendAdLoader.js
262 ms
1976504288-widgets.js
317 ms
plusone.js
315 ms
gradients_light.png
151 ms
icon18_wrench_allbkg.png
147 ms
-shared-img-thumb-0I9A853115070150spk_TP_V.jpg
260 ms
lex_a_0000002252.jpg
149 ms
%25E3%2583%2598%25E3%2583%25AB%25E3%2582%25B7%25E3%2583%25BC%25E3%2583%25AF%25E3%2583%25B3%2B%2B%2B%2B%25E6%25A0%2584%25E9%25A4%258A%25E7%25B4%25A0%25E3%2582%25AB%25E3%2582%25A6%25E3%2583%25B3%25E3%2582%25BB%25E3%2583%25AA%25E3%2583%25B3%25E3%2582%25B0.jpeg
148 ms
059493.jpg
259 ms
aikon.jpeg
263 ms
250px-Pension_handbook_(Japan).jpg
169 ms
syougaisya.jpg
256 ms
9f8c0b0a.gif
169 ms
OZPA_ikidaoreiine500-thumb-746x500-3188.jpg
257 ms
PAK99_tewotunaidadanjyo20140301500.jpg
141 ms
news_20100416_1.jpg
157 ms
b6b57603.png
168 ms
a0003_001886.jpg
142 ms
body_gradient_tile_light.png
142 ms
ca-pub-9051787828314566.js
270 ms
zrt_lookup.html
250 ms
show_ads_impl.js
135 ms
ads
407 ms
osd.js
136 ms
ninja_onetag.css
740 ms
trac.js
600 ms
2510145422372050369
563 ms
abg.js
728 ms
m_js_controller.js
775 ms
googlelogo_color_112x36dp.png
223 ms
ads
328 ms
platform.js
130 ms
ga.js
397 ms
cb=gapi.loaded_0
263 ms
cb=gapi.loaded_1
306 ms
follow
356 ms
button-only@2x.png
1067 ms
rss_button_l.png
232 ms
feedly-follow-rectangle-flat-small_2x.png
427 ms
feed
1527 ms
widgets.js
181 ms
bookmark_button.js
1071 ms
btn.js
360 ms
fastbutton
362 ms
x_button_blue2.svg
100 ms
s
107 ms
redir.html
377 ms
1.0.1.js
557 ms
css
379 ms
like.php
520 ms
cookiesync
243 ms
button.71000885400e222c3c0eec823f8f93f0.js
285 ms
postmessageRelay
508 ms
rs=AGLTcCO2PppkrIxNFDnxom7Vp2ZnVc-UEA
94 ms
rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A
120 ms
rs=AGLTcCPxwVaHKIimPoq-iFVUc7_x57t_BA
218 ms
__utm.gif
79 ms
cb=gapi.loaded_0
322 ms
cb=gapi.loaded_1
151 ms
button
136 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
465 ms
iframe.html
257 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
237 ms
JcQUq3K39RZrUxrrs7pjpwLUuEpTyoUstqEm5AMlJo4.ttf
496 ms
IhuqmeHx65TaW6CiR2l0VALUuEpTyoUstqEm5AMlJo4.ttf
476 ms
button.css
456 ms
shared.js
458 ms
button.js
475 ms
favicon
441 ms
follow_button.fd774b599f565016d763dd860cb31c79.ja.html
155 ms
tweet_button.fd774b599f565016d763dd860cb31c79.en.html
221 ms
3XaI8mzWBSs.js
426 ms
LVx-xkvaJ0b.png
421 ms
PuwvqkdbcqU-fCZ9Ed-b7cDdSZkkecOE1hvV7ZHvhyU.ttf
224 ms
push
327 ms
1077434459-postmessagerelay.js
196 ms
rpc:shindig_random.js
112 ms
info.json
282 ms
ga-audiences
211 ms
pocket_button.png
29 ms
1.0.0.js
267 ms
cb=gapi.loaded_0
69 ms
285 ms
pixel
57 ms
reset.css
29 ms
entry-button.css
40 ms
5c743ad76f02093960aec92d19616b35
219 ms
57f09f57e732daf1d3d7259ee3ef02f0
219 ms
sync
394 ms
bbtn-l_v3.png
21 ms
activeview
36 ms
jot.html
25 ms
js1
591 ms
ib
198 ms
ib
370 ms
sync
339 ms
sync
431 ms
push_sync
324 ms
1.1.0.js
181 ms
cookiesync
199 ms
js
506 ms
js
511 ms
sync
196 ms
receive_sync
158 ms
jstag
92 ms
acj
43 ms
imp
349 ms
ri
31 ms
ADTECH;cfp=1;rndc=1460146192;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1460146192960
344 ms
a1033892.js
378 ms
js
60 ms
moatad.js
262 ms
sync
48 ms
pixel
26 ms
generic
27 ms
mapuser
316 ms
mapuser
317 ms
generic
34 ms
mapuser
307 ms
adServer.bs
215 ms
4448
115 ms
mapuser
820 ms
mapuser
308 ms
mapuser
562 ms
mapuser
19 ms
ebPreServing.js
37 ms
adServer.bs
92 ms
0.gif
48 ms
sync
87 ms
eg
1041 ms
mapuser
8 ms
ebHtml5Banner.js
47 ms
index.html
106 ms
id.js
136 ms
usermatch
68 ms
pixel.htm
133 ms
css
50 ms
style.css
49 ms
TweenMax.min.js
246 ms
jquery.min.js
241 ms
MASN.js
110 ms
usermatch
191 ms
ddc.htm
386 ms
adkit.js
124 ms
gr
292 ms
VwgQEsAoJWwAAAaQS-AAAAAj%26929
282 ms
pixel
289 ms
casale
289 ms
cse
440 ms
mapuser
442 ms
Pug
195 ms
sd
172 ms
rtset
187 ms
rum
207 ms
u.php
161 ms
303 ms
mapuser
157 ms
um
202 ms
pixel
182 ms
crum
253 ms
pixel
211 ms
crum
248 ms
config.js
192 ms
bd
227 ms
side_left.png
206 ms
side_right.png
206 ms
bottom_bar.png
207 ms
sync
193 ms
xrefid.xgi
167 ms
m
182 ms
jsk
562 ms
rum
112 ms
merge
112 ms
pixel.gif
145 ms
tap.php
125 ms
nationals_300x250.xml
294 ms
lr.gif
186 ms
rum
101 ms
NAX8720102453459995145
113 ms
bd
59 ms
bH7276GfdCjMjApa_dkG6SZ2oysoEQEeKwjgmXLRnTc.ttf
41 ms
0XxGQsSc1g4rdRdjJKZrNMDdSZkkecOE1hvV7ZHvhyU.ttf
42 ms
EBLoader.js
45 ms
ck-confirm
119 ms
crum
59 ms
EBCMD.js
45 ms
Rendon-300x250.jpg
372 ms
score_n.png
26 ms
masnn.png
24 ms
300x250_nationals.png
370 ms
300x250_marlins.png
409 ms
ads.js
245 ms
gl3
184 ms
mapuser
165 ms
adcomp_pc.js
26 ms
sspcore_spot.js
71 ms
ssp_spot.ashx
330 ms
push_sync
164 ms
acs
208 ms
cs
228 ms
sync
163 ms
pixel
87 ms
sync
65 ms
sync
25 ms
depressionrecover.com 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
depressionrecover.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
depressionrecover.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Depressionrecover.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Depressionrecover.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.
depressionrecover.com
Open Graph description is not detected on the main page of Depressionrecover. 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: