6.5 sec in total
1.8 sec
3.9 sec
728 ms
Click here to check amazing Lifecall content. Otherwise, check out these important facts you probably never knew about lifecall.com
LifeCall Medical Alert Systems with FallAlert™ Call 866-220-1212 TODAY A+ BBB RATED & 40 YEARS IN THE INDUSTRY. Affordable Medical Alert Systems with FallAlert™
Visit lifecall.comWe analyzed Lifecall.com page load time and found that the first response time was 1.8 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lifecall.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.2 s
23/100
25%
Value12.0 s
4/100
10%
Value2,540 ms
4/100
30%
Value0.031
100/100
15%
Value19.8 s
2/100
10%
1782 ms
55 ms
132 ms
169 ms
132 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lifecall.com, 86% (124 requests) were made to Lifecall.b-cdn.net and 5% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Lifecall.com.
Page size can be reduced by 343.8 kB (24%)
1.4 MB
1.1 MB
In fact, the total size of Lifecall.com main page is 1.4 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. 85% 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 886.3 kB which makes up the majority of the site volume.
Potential reduce by 327.6 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 327.6 kB or 83% of the original size.
Potential reduce by 11.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. This website has mostly compressed JavaScripts.
Potential reduce by 4.4 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. Lifecall.com has all CSS files already compressed.
Number of requests can be reduced by 106 (79%)
135
29
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifecall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
www.lifecall.com
1782 ms
mediaelementplayer-legacy.min.css
55 ms
wp-mediaelement.min.css
132 ms
woocommerce-layout.css
169 ms
woocommerce.css
132 ms
font-awesome.min.css
148 ms
style.css
128 ms
grid-system.css
140 ms
style.css
170 ms
header-layout-centered-menu.css
150 ms
header-secondary-nav.css
151 ms
element-testimonial.css
142 ms
element-flip-box.css
195 ms
element-icon-with-text.css
148 ms
css
76 ms
responsive.css
224 ms
product-style-classic.css
214 ms
woocommerce.css
215 ms
ascend.css
187 ms
menu-dynamic.css
158 ms
js_composer.min.css
161 ms
style.css
164 ms
css
43 ms
wp-polyfill-inert.min.js
222 ms
regenerator-runtime.min.js
176 ms
wp-polyfill.min.js
163 ms
hooks.min.js
202 ms
w.js
28 ms
jquery.min.js
216 ms
jquery-migrate.min.js
256 ms
jquery.blockUI.min.js
204 ms
add-to-cart.min.js
202 ms
js.cookie.min.js
204 ms
woocommerce.min.js
204 ms
s-202403.js
27 ms
css
33 ms
wc-blocks.css
326 ms
formreset.min.css
235 ms
formsmain.min.css
246 ms
readyclass.min.css
248 ms
browsers.min.css
249 ms
style-non-critical.css
250 ms
woocommerce-non-critical.css
328 ms
e-202403.js
10 ms
api.js
40 ms
magnific.css
179 ms
core.css
190 ms
rs6.css
186 ms
rbtools.min.js
837 ms
rs6.min.js
168 ms
sourcebuster.min.js
237 ms
order-attribution.min.js
236 ms
react.min.js
293 ms
deprecated.min.js
292 ms
dom.min.js
275 ms
react-dom.min.js
265 ms
escape-html.min.js
252 ms
element.min.js
291 ms
is-shallow-equal.min.js
288 ms
i18n.min.js
288 ms
keycodes.min.js
288 ms
priority-queue.min.js
289 ms
compose.min.js
747 ms
private-apis.min.js
738 ms
redux-routine.min.js
738 ms
data.min.js
725 ms
lodash.min.js
719 ms
wc-blocks-registry.js
744 ms
url.min.js
744 ms
api-fetch.min.js
740 ms
wc-settings.js
741 ms
data-controls.min.js
730 ms
g.gif
105 ms
html-entities.min.js
751 ms
analytics.js
147 ms
notices.min.js
876 ms
wc-blocks-middleware.js
734 ms
wc-blocks-data.js
875 ms
dom-ready.min.js
734 ms
a11y.min.js
872 ms
primitives.min.js
735 ms
warning.min.js
739 ms
blocks-components.js
864 ms
blocks-checkout.js
862 ms
order-attribution-blocks.min.js
797 ms
jquery.easing.min.js
798 ms
jquery.mousewheel.min.js
800 ms
priority.js
797 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
101 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
573 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
589 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
591 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
590 ms
transit.min.js
798 ms
waypoints.js
758 ms
imagesLoaded.min.js
744 ms
hoverintent.min.js
746 ms
magnific.js
748 ms
touchswipe.min.js
747 ms
collect
498 ms
nectar-testimonial-slider.js
703 ms
anime.min.js
710 ms
superfish.js
707 ms
init.js
717 ms
cart-fragments.min.js
661 ms
js_composer_front.min.js
239 ms
jquery.json.min.js
239 ms
gravityforms.min.js
238 ms
jquery.maskedinput.min.js
236 ms
placeholders.jquery.min.js
229 ms
utils.min.js
221 ms
js
217 ms
vendor-theme.min.js
220 ms
scripts-theme.min.js
229 ms
icomoon.woff
218 ms
fontawesome-webfont.svg
219 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
65 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
62 ms
Lifecall-Logo.png
216 ms
product-Standard-Basic.png
167 ms
product-Advanced.png
167 ms
product-Cellular-shadow.png
166 ms
mobile-alert-watch.png
160 ms
product-Advanced-Mobile.png
160 ms
product-mobilealert-Pro.png
238 ms
Slide-1-rev-b.jpg
241 ms
slide2.jpg
235 ms
Slide-4.jpg
233 ms
Slide-Gardner2.jpg
236 ms
Slide-5.jpg
235 ms
icon-home-247.jpg
238 ms
icon-home-alarm.jpg
234 ms
icon-home-emergency.jpg
235 ms
affiliates.gif
235 ms
01.png
234 ms
04.png
235 ms
02.png
234 ms
05.png
234 ms
03.png
235 ms
06.png
234 ms
Testimonialsbg2.jpg
232 ms
fontawesome-webfont.woff
7 ms
g.gif
87 ms
recaptcha__en.js
45 ms
woocommerce-smallscreen.css
76 ms
lifecall.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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lifecall.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
Browser errors were logged to the console
lifecall.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifecall.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 Lifecall.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.
lifecall.com
Open Graph data is detected on the main page of Lifecall. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: