Tools & Wizards About Us
lifefone.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lifefone.com

LifeFone Medical Alert | LifeFone

Page Load Speed

8.7 sec in total

First Response

41 ms

Resources Loaded

4.1 sec

Page Rendered

4.6 sec

lifefone.com screenshot

About Website

Visit lifefone.com now to see the best up-to-date Life Fone content for United States and also check out these interesting facts you probably never knew about lifefone.com

LifeFone's Medical Alert System with Fall Detection & GPS. At Home & On the Go, LifeFone's medical alert device help button helps seniors age in place.

Visit lifefone.com

Key Findings

We analyzed Lifefone.com page load time and found that the first response time was 41 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.

Performance Metrics

lifefone.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value2,140 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

lifefone.com

41 ms

lifefone.com

80 ms

www.lifefone.com

2802 ms

solidus_starter_frontend-d4fc6d141c0f96f4c28779a41358722f457f3084e83226a41f22c3fa0ab9ee14.js

24 ms

solidus_starter_frontend-a6e6483a61e9fba2be840318ffa3d08def91c14a8f94d1d5d8b4d0eb8f37fe98.css

91 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 64% of them (54 requests) were addressed to the original Lifefone.com, 7% (6 requests) were made to Static.olark.com and 5% (4 requests) were made to Wp.lifefone.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Lifefone.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 451.1 kB (25%)

Content Size

1.8 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lifefone.com main page is 1.8 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. 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. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 68.4 kB

  • Original 86.0 kB
  • After minification 85.3 kB
  • After compression 17.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 68.4 kB or 80% of the original size.

Image Optimization

-23%

Potential reduce by 373.5 kB

  • Original 1.7 MB
  • After minification 1.3 MB

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, Life Fone needs image optimization as it can save up to 373.5 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 9.3 kB

  • Original 48.4 kB
  • After minification 48.3 kB
  • After compression 39.2 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 9.3 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (35%)

Requests Now

66

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life Fone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

lifefone.com

lifefone.com

41 ms

lifefone.com

lifefone.com

80 ms

www.lifefone.com

www.lifefone.com

2802 ms

solidus_starter_frontend-d4fc6d141c0f96f4c28779a41358722f457f3084e83226a41f22c3fa0ab9ee14.js

solidus_starter_frontend-d4fc6d141c0f96f4c28779a41358722f457f3084e83226a41f22c3fa0ab9ee14.js

24 ms

solidus_starter_frontend-a6e6483a61e9fba2be840318ffa3d08def91c14a8f94d1d5d8b4d0eb8f37fe98.css

solidus_starter_frontend-a6e6483a61e9fba2be840318ffa3d08def91c14a8f94d1d5d8b4d0eb8f37fe98.css

91 ms

application-Cy4SKCCp.js

application-Cy4SKCCp.js

60 ms

application-B3rq05lb.css

application-B3rq05lb.css

37 ms

js

js

61 ms

js

js

170 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

25 ms

63064.js

63064.js

380 ms

api.js

api.js

33 ms

js

js

264 ms

invoca-latest.min.js

invoca-latest.min.js

322 ms

fbevents.js

fbevents.js

263 ms

events.js

events.js

349 ms

e3yNG8XrDx-619ceda6.js

e3yNG8XrDx-619ceda6.js

348 ms

bat.js

bat.js

357 ms

family_safety-300x200.jpg

family_safety-300x200.jpg

405 ms

widget_async.js

widget_async.js

394 ms

loader.js

loader.js

407 ms

logo-CSlvjrQw.png

logo-CSlvjrQw.png

230 ms

vipx_headon-thumb-320x284-5-nt.png

vipx_headon-thumb-320x284-5-nt.png

294 ms

vip-x-graphic-Dg2cRr7k.svg

vip-x-graphic-Dg2cRr7k.svg

232 ms

vip-active-two-pendants-no-bg.png

vip-active-two-pendants-no-bg.png

229 ms

Belle_W_on_band_2zc.png

Belle_W_on_band_2zc.png

335 ms

VIP_flex_blue.png

VIP_flex_blue.png

335 ms

smartwatch_silhouette_320x284.png

smartwatch_silhouette_320x284.png

325 ms

lf-at-home-systems-thumb.png

lf-at-home-systems-thumb.png

339 ms

MothersDay-CWITaGMO.webp

MothersDay-CWITaGMO.webp

410 ms

MothersDay_mobile-Cs7n8y9f.webp

MothersDay_mobile-Cs7n8y9f.webp

390 ms

badge_2024_money-B80ZN243.svg

badge_2024_money-B80ZN243.svg

387 ms

badge-2024-consumeradvocate-DUjR3Zz7.svg

badge-2024-consumeradvocate-DUjR3Zz7.svg

383 ms

badge_2024_usnews-BmmpquRj.png

badge_2024_usnews-BmmpquRj.png

390 ms

badge-2024-forbes-BXsYpmA2.svg

badge-2024-forbes-BXsYpmA2.svg

385 ms

360_Reviews_Best-Medical-Alert-Systems_2022_LifeFone-Ol3rnRYT.png

360_Reviews_Best-Medical-Alert-Systems_2022_LifeFone-Ol3rnRYT.png

417 ms

2024-vip-money-us-news-recognition-banner-full-width-light.png

2024-vip-money-us-news-recognition-banner-full-width-light.png

422 ms

at-home-hp-image-CbIrwwLA.jpg

at-home-hp-image-CbIrwwLA.jpg

420 ms

on-the-go-hp-image-BCF69kj5.jpg

on-the-go-hp-image-BCF69kj5.jpg

427 ms

recognition-mobile-background.jpg-2d_cWcNP.webp

recognition-mobile-background.jpg-2d_cWcNP.webp

436 ms

recognition-background.png-C2B0c8ja.webp

recognition-background.png-C2B0c8ja.webp

452 ms

lifefone-recognition-badge-CLh0xrbv.png

lifefone-recognition-badge-CLh0xrbv.png

449 ms

flag-icon-BJooiIVQ.png

flag-icon-BJooiIVQ.png

467 ms

a-plus-icon-VkBd7Qoc.png

a-plus-icon-VkBd7Qoc.png

452 ms

doplet-icon-BTq9tsPV.png

doplet-icon-BTq9tsPV.png

466 ms

nation-icon-large-B02t3dXb.png

nation-icon-large-B02t3dXb.png

495 ms

hp-video-image-2.jpg.webp

hp-video-image-2.jpg.webp

484 ms

consumer-friendly-policies-large.jpg-CbtBg3YG.webp

consumer-friendly-policies-large.jpg-CbtBg3YG.webp

581 ms

consumer-friendly-policies-mobile-ByqZvR_F.jpg

consumer-friendly-policies-mobile-ByqZvR_F.jpg

488 ms

couple-bikes-meadow-blue.jpg-CxUuSMU2.webp

couple-bikes-meadow-blue.jpg-CxUuSMU2.webp

513 ms

couple-bikes-meadow-mobile-DHHX3zJl.webp

couple-bikes-meadow-mobile-DHHX3zJl.webp

494 ms

handshake-icon-mobile-CMFeRGET.png

handshake-icon-mobile-CMFeRGET.png

528 ms

handshake-icon-BU6EiCRS.png

handshake-icon-BU6EiCRS.png

531 ms

fall_detection-300x300.jpg

fall_detection-300x300.jpg

391 ms

getting_up_safely_fall-300x200.jpg

getting_up_safely_fall-300x200.jpg

391 ms

work_life_balance-300x217.jpg

work_life_balance-300x217.jpg

391 ms

NunitoSans-Regular-2DeC9KkV.woff

NunitoSans-Regular-2DeC9KkV.woff

522 ms

NunitoSans-Light-Zr5AWMVa.woff

NunitoSans-Light-Zr5AWMVa.woff

533 ms

NunitoSans-ExtraLight-DXuhtZR3.woff

NunitoSans-ExtraLight-DXuhtZR3.woff

571 ms

NunitoSans-SemiBold-D5CU7R3W.woff

NunitoSans-SemiBold-D5CU7R3W.woff

571 ms

NunitoSans-ExtraBold-CSMrGZnW.woff

NunitoSans-ExtraBold-CSMrGZnW.woff

357 ms

NunitoSans-Bold-D2W-EE56.woff

NunitoSans-Bold-D2W-EE56.woff

357 ms

NunitoSans-Black-DaI_s3uH.woff

NunitoSans-Black-DaI_s3uH.woff

321 ms

NunitoSans-SemiBoldItalic-CUk24oa_.woff

NunitoSans-SemiBoldItalic-CUk24oa_.woff

625 ms

rt

rt

21 ms

ProcessStats.aspx

ProcessStats.aspx

70 ms

conv

conv

36 ms

NunitoSans-ExtraBoldItalic-5wAihwHE.woff

NunitoSans-ExtraBoldItalic-5wAihwHE.woff

272 ms

NunitoSans-BoldItalic-CX3ltI4X.woff

NunitoSans-BoldItalic-CX3ltI4X.woff

391 ms

NunitoSans-BlackItalic-9Aj9C25M.woff

NunitoSans-BlackItalic-9Aj9C25M.woff

389 ms

NunitoSans-Italic-H_cqE7Mp.woff

NunitoSans-Italic-H_cqE7Mp.woff

388 ms

widget_async.js

widget_async.js

16 ms

NunitoSans-LightItalic-DnFXk7y_.woff

NunitoSans-LightItalic-DnFXk7y_.woff

338 ms

NunitoSans-ExtraLightItalic-DtpvHVRX.woff

NunitoSans-ExtraLightItalic-DtpvHVRX.woff

337 ms

app.js

app.js

22 ms

9214-506-10-8285.js

9214-506-10-8285.js

24 ms

c

c

68 ms

application2.js

application2.js

135 ms

main.js

main.js

14 ms

storage.html

storage.html

22 ms

storage.js

storage.js

23 ms

visits

visits

92 ms

log.png

log.png

97 ms

pd.js

pd.js

18 ms

Accessibility Review

lifefone.com accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

lifefone.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

lifefone.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifefone.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 Lifefone.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.

Social Sharing Optimization

lifefone.com

Open Graph description is not detected on the main page of Life Fone. 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: