5.3 sec in total
245 ms
4.2 sec
848 ms
Click here to check amazing Voice In Recovery content. Otherwise, check out these important facts you probably never knew about voiceinrecovery.com
Prevention, Advocacy, Intervention, Recovery (PAIR)™
Visit voiceinrecovery.comWe analyzed Voiceinrecovery.com page load time and found that the first response time was 245 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.
voiceinrecovery.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.4 s
20/100
25%
Value4.2 s
77/100
10%
Value380 ms
70/100
30%
Value0.078
95/100
15%
Value6.7 s
56/100
10%
245 ms
333 ms
1157 ms
136 ms
150 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 34% of them (42 requests) were addressed to the original Voiceinrecovery.com, 17% (21 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Voiceinrecovery.com.
Page size can be reduced by 399.3 kB (50%)
802.8 kB
403.5 kB
In fact, the total size of Voiceinrecovery.com main page is 802.8 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. 65% of websites need less resources to load. Javascripts take 363.7 kB which makes up the majority of the site volume.
Potential reduce by 53.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 53.0 kB or 76% of the original size.
Potential reduce by 4.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. Voice In Recovery images are well optimized though.
Potential reduce by 220.8 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 220.8 kB or 61% of the original size.
Potential reduce by 121.0 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. Voiceinrecovery.com needs all CSS files to be minified and compressed as it can save up to 121.0 kB or 84% of the original size.
Number of requests can be reduced by 79 (66%)
119
40
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voice In Recovery. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
voiceinrecovery.com
245 ms
blog
333 ms
1157 ms
wp-emoji-release.min.js
136 ms
style.css
150 ms
headway.css
153 ms
leafs.css
144 ms
custom.css
142 ms
icons.css
146 ms
lumebox.css
203 ms
wpp.css
209 ms
jetpack.css
241 ms
commentluv.css
241 ms
style.css
240 ms
blackbirdpie.css
239 ms
jquery.js
335 ms
jquery-migrate.min.js
275 ms
commentluv.js
322 ms
ajax-cart.js
318 ms
blackbirdpie.js
320 ms
functions.js
312 ms
js-mode.js
355 ms
external-tracking.min.js
381 ms
bubble.js
384 ms
style.css
387 ms
plusone.js
41 ms
all.js
269 ms
widget.js
20 ms
equal-columns.js
457 ms
devicepx-jetpack.js
5 ms
gprofiles.js
59 ms
wpgroho.js
457 ms
wp-embed.min.js
457 ms
e-201611.js
4 ms
ga.js
26 ms
analytics.js
102 ms
cb=gapi.loaded_0
147 ms
headshot-badge-1.jpg
474 ms
pixel.png
89 ms
grunge-and-japanese-foliagep38.jpg
548 ms
VIR.jpg
471 ms
rightsm.gif
145 ms
close.png
143 ms
twitter.png
141 ms
facebook.png
143 ms
rss.png
182 ms
followme_grab.gif
181 ms
__utm.gif
61 ms
get_custom_js
52 ms
collect
41 ms
412 ms
followme_top.gif
303 ms
followme_mid.gif
302 ms
followme_bottom.gif
329 ms
xd_arbiter.php
460 ms
xd_arbiter.php
665 ms
tc.js
265 ms
vglnk.js
262 ms
likebox.php
603 ms
widgets.js
286 ms
index.php
867 ms
hovercard.css
113 ms
services.css
137 ms
145 ms
cb=gapi.loaded_1
43 ms
fastbutton
111 ms
closeit.png
111 ms
g.gif
27 ms
pixel.gif
59 ms
p
104 ms
pixel.gif
54 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
155 ms
postmessageRelay
65 ms
cb=gapi.loaded_0
30 ms
cb=gapi.loaded_1
22 ms
like.php
109 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
16 ms
v2
46 ms
3193398744-postmessagerelay.js
26 ms
rpc:shindig_random.js
29 ms
cb=gapi.loaded_0
5 ms
dpx
11 ms
qeKvIRsJabD.js
512 ms
LVx-xkvaJ0b.png
385 ms
ca.png
166 ms
xrefid.xgi
13 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
43 ms
52154.gif
6 ms
ebiMDO3r-8l.css
332 ms
jGc-59L_9lo.css
335 ms
6qHpHChjY_J.css
341 ms
ztINr5qMqM_.css
401 ms
uVjHKJ0glvg.css
408 ms
q68gy-v_YMF.js
464 ms
FJmpeSpHpjS.js
534 ms
0wM5s1Khldu.js
406 ms
1bNoFZUdlYZ.js
461 ms
njO1TPvGzoR.js
484 ms
1QuX41zDRrx.js
483 ms
Oagsvfb4VWi.js
552 ms
LTv6ZK-5zxz.js
661 ms
1FCa-btixu2.js
551 ms
jot
96 ms
ping
15 ms
batch
48 ms
rss_icon.png
87 ms
1979483_10153907264125716_1466317723_n.jpg
298 ms
safe_image.php
301 ms
safe_image.php
358 ms
safe_image.php
428 ms
safe_image.php
493 ms
10712_10154825171400716_7887507237537651971_n.jpg
353 ms
12814765_10156553751390543_8959170487127849661_n.jpg
421 ms
996832_10151663337957692_636969011_n.jpg
488 ms
11204875_10154040990529050_472034050506407023_n.jpg
486 ms
10259850_10154072100503885_6551032328162838447_n.jpg
489 ms
580357_10207313221422873_7406411957214170903_n.jpg
487 ms
1545773_824851987590696_8223408037849279596_n.jpg
490 ms
wL6VQj7Ab77.png
119 ms
s7jcwEQH7Sx.png
119 ms
QDwYpIaRyfG.png
118 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
135 ms
voiceinrecovery.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
voiceinrecovery.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
voiceinrecovery.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voiceinrecovery.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Voiceinrecovery.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.
voiceinrecovery.com
Open Graph data is detected on the main page of Voice In Recovery. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: