2.3 sec in total
185 ms
2 sec
136 ms
Click here to check amazing My Vocalocity content for India. Otherwise, check out these important facts you probably never knew about my.vocalocity.com
For Vonage Business customers, sign into your account here!
Visit my.vocalocity.comWe analyzed My.vocalocity.com page load time and found that the first response time was 185 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
my.vocalocity.com performance score
name
value
score
weighting
Value11.5 s
0/100
10%
Value15.8 s
0/100
25%
Value11.5 s
5/100
10%
Value490 ms
59/100
30%
Value0.068
96/100
15%
Value18.5 s
3/100
10%
185 ms
60 ms
169 ms
89 ms
89 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original My.vocalocity.com, 13% (15 requests) were made to Business.vonage.com and 3% (3 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (807 ms) relates to the external source Business.vonage.com.
Page size can be reduced by 1.4 MB (74%)
1.9 MB
494.6 kB
In fact, the total size of My.vocalocity.com main page is 1.9 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. 55% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 19.3 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 2.8 kB, which is 12% 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 19.3 kB or 82% of the original size.
Potential reduce by 12.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. My Vocalocity images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 80% of the original size.
Potential reduce by 254.1 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. My.vocalocity.com needs all CSS files to be minified and compressed as it can save up to 254.1 kB or 83% of the original size.
Number of requests can be reduced by 94 (83%)
113
19
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Vocalocity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
185 ms
login.css
60 ms
log4javascript.js
169 ms
main.js
89 ms
loginStart.js
89 ms
token-input-facebook.css
75 ms
jquery.loadmask.css
75 ms
apprise.min.css
77 ms
main.css
106 ms
youtube_css.jsp
93 ms
growl.css
107 ms
jquery.min.js
179 ms
jquery-ui.min.js
80 ms
jquery.ui.widget.js
119 ms
jquery.easing.1.3.js
125 ms
jquery-settings.js
121 ms
toogle.js
123 ms
profile.js
152 ms
jquery.tipsy.js
139 ms
jquery.uniform.min.js
141 ms
ui.dropdownchecklist.js
232 ms
jquery.wysiwyg.js
232 ms
jquery.tablesorter.min.js
236 ms
jquery.ui.totop.js
174 ms
fullcalendar.min.js
239 ms
jquery.ui.core.js
247 ms
jquery.ui.mouse.js
247 ms
jquery.ui.dialog.js
246 ms
jquery.ui.tabs.js
247 ms
jquery.tokeninput.js
248 ms
jquery.ui.accordion.js
247 ms
jsapi
71 ms
reset.css
272 ms
root.css
305 ms
grid.css
252 ms
typography.css
244 ms
jquery-ui.css
246 ms
jquery-plugin-base.css
247 ms
satelliteLib-84f88d7e472ee7c92eb6e95d6c85fa05f8684e16-staging.js
49 ms
validationEngine.jquery.css
291 ms
callblocking.css
255 ms
slidingtabs-vertical.css
209 ms
jquery.dataTables.js
330 ms
dataTables.customSort.js
234 ms
table-functions.js
235 ms
ColVis.js
236 ms
jquery.countdown.js
233 ms
ui.dropdownchecklist.js
224 ms
date.js
223 ms
jquery.loadmask.js
208 ms
growl.js
204 ms
apprise-1.5.min.js
211 ms
common.js
234 ms
reportscommon.js
217 ms
dataTables.export.js
221 ms
jquery.validationEngine-en.js
213 ms
ga.js
107 ms
jquery.validationEngine.js
202 ms
systemmaintenance.js
161 ms
jquery.slidingtabs.pack.js
142 ms
login.js;jsessionid=hPxqsgHRUIjJKc3XFexCE+QR.undefined
165 ms
jquery.ui.base.css
113 ms
jquery.ui.theme.css
128 ms
tipsy-style.css
132 ms
uniform.default.css
136 ms
jquery.wysiwyg.css
143 ms
prettyphoto-style.css
148 ms
tableshorter-theme.css
150 ms
fullcalendar.css
147 ms
jquery.ibutton.css
151 ms
datatable_jui.css
152 ms
jquery.miniColors.css
155 ms
jquery.media.player.css
161 ms
jplayer.css
161 ms
__utm.gif
20 ms
jquery.ui.core.css
50 ms
jquery.ui.resizable.css
56 ms
jquery.ui.selectable.css
57 ms
jquery.ui.accordion.css
59 ms
jquery.ui.autocomplete.css
64 ms
jquery.ui.dialog.css
67 ms
jquery.ui.slider.css
64 ms
jquery.ui.tabs.css
65 ms
jquery.ui.datepicker.css
67 ms
jquery.ui.progressbar.css
73 ms
1441837760670;jsessionid=hPxqsgHRUIjJKc3XFexCE+QR.undefined
151 ms
wave.png
152 ms
login-bg.png
151 ms
174 ms
st-forminput-bg.png
145 ms
satellite-563b980b64746d3f7d003fae-staging.js
21 ms
s-code-contents-cd1084b090407b9ba231d7addd743b1e1823e208-staging.js
38 ms
ui-bg_flat_75_ffffff_40x100.png
23 ms
ui-icons_222222_256x240.png
22 ms
ui.totop.png
32 ms
rd
10 ms
id
57 ms
807 ms
s27761453425046
7 ms
jquery.min.js
13 ms
jquery.themepunch.revolution.min.js
30 ms
settings.min.css
12 ms
activityi;src=5111659;type=acctlog;cat=vonag000;u2=[Account%20ID];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=8563065722119.063
52 ms
vmt-bkgd.jpg
6 ms
vmt-email.png
8 ms
vmt-phone.png
10 ms
mobile-bkgd.jpg
11 ms
referal-tablet.png
17 ms
loader.gif
12 ms
timer.png
13 ms
vmt-thumb.jpg
6 ms
mobile-thumb.jpg
6 ms
referral-thumb.jpg
9 ms
small_left.png
6 ms
small_right.png
7 ms
my.vocalocity.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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
my.vocalocity.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
Page has valid source maps
my.vocalocity.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My.vocalocity.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that My.vocalocity.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.
my.vocalocity.com
Open Graph description is not detected on the main page of My Vocalocity. 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: