Tools & Wizards About Us
ga2.mylifeline.org screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

ga2.mylifeline.org

MyLifeLine | transform cancer experiences with community connections

Page Load Speed

1.4 sec in total

First Response

38 ms

Resources Loaded

814 ms

Page Rendered

583 ms

ga2.mylifeline.org screenshot

About Website

Welcome to ga2.mylifeline.org homepage info - get ready to check Ga 2 My Life Line best content for United States right away, or after learning these important things about ga2.mylifeline.org

MyLifeLine connects cancer patients to support networks to reduce isolation with personal websites and discussion boards. Connect to your community.

Visit ga2.mylifeline.org

Key Findings

We analyzed Ga2.mylifeline.org page load time and found that the first response time was 38 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

ga2.mylifeline.org performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value1.513

0/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

ga2.mylifeline.org

38 ms

ga2.mylifeline.org

465 ms

gtm.js

128 ms

js

191 ms

js

206 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 37% of them (14 requests) were addressed to the original Ga2.mylifeline.org, 50% (19 requests) were made to D3d7e01xja9yqp.cloudfront.net and 8% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (465 ms) belongs to the original domain Ga2.mylifeline.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.9 kB (38%)

Content Size

450.0 kB

After Optimization

281.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ga2.mylifeline.org main page is 450.0 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. Images take 184.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 144.7 kB

  • Original 179.9 kB
  • After minification 131.9 kB
  • After compression 35.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. This page needs HTML code to be minified as it can gain 48.0 kB, which is 27% 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 144.7 kB or 80% of the original size.

Image Optimization

-13%

Potential reduce by 24.1 kB

  • Original 184.9 kB
  • After minification 160.8 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, Ga 2 My Life Line needs image optimization as it can save up to 24.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 162 B

  • Original 85.2 kB
  • After minification 85.2 kB
  • After compression 85.1 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.

Requests Breakdown

Number of requests can be reduced by 16 (47%)

Requests Now

34

After Optimization

18

  • Images
  • JavaScript

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

Network Requests Diagram

ga2.mylifeline.org

ga2.mylifeline.org

38 ms

ga2.mylifeline.org

ga2.mylifeline.org

465 ms

gtm.js

gtm.js

128 ms

js

js

191 ms

js

js

206 ms

hotjar-1196573.js

hotjar-1196573.js

164 ms

fbevents.js

fbevents.js

70 ms

csc-gc_2021.svg

csc-gc_2021.svg

143 ms

jquery.min.js

jquery.min.js

127 ms

bootstrap.min.js

bootstrap.min.js

141 ms

lazyload.min.js

lazyload.min.js

150 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

151 ms

moment.min.js

moment.min.js

152 ms

class.d5542b120ee564edf083.js

class.d5542b120ee564edf083.js

151 ms

cookieconsent-js.ed54f4833ac528c83448.js

cookieconsent-js.ed54f4833ac528c83448.js

157 ms

export.d5cd1326367cb9f6abf7.js

export.d5cd1326367cb9f6abf7.js

160 ms

global-js.b265802ca47de834480b.js

global-js.b265802ca47de834480b.js

159 ms

hotjar.a38faf9d19b22c34cfea.js

hotjar.a38faf9d19b22c34cfea.js

159 ms

search-js.4ce5819115d534711f22.js

search-js.4ce5819115d534711f22.js

163 ms

home-bundle-js.acdbcb65f450da57ba1a.js

home-bundle-js.acdbcb65f450da57ba1a.js

238 ms

verify_phone.svg

verify_phone.svg

28 ms

user_story.svg

user_story.svg

83 ms

connect_community.svg

connect_community.svg

79 ms

template_3.jpg

template_3.jpg

79 ms

template_2.jpg

template_2.jpg

82 ms

template_6.jpg

template_6.jpg

79 ms

evelina_thumbnail.webp

evelina_thumbnail.webp

71 ms

logo_starburst.png

logo_starburst.png

107 ms

guidestar_2021.png

guidestar_2021.png

107 ms

charity-navigator.png

charity-navigator.png

108 ms

banner-home.webp

banner-home.webp

162 ms

mll-intro-overlay.webp

mll-intro-overlay.webp

162 ms

security_shield.webp

security_shield.webp

162 ms

friends-family-0823.webp

friends-family-0823.webp

164 ms

amber.webp

amber.webp

164 ms

helpline-counseler-image.webp

helpline-counseler-image.webp

233 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

118 ms

fontawesome-webfont.woff2

fontawesome-webfont.woff2

72 ms

Accessibility Review

ga2.mylifeline.org accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

ga2.mylifeline.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ga2.mylifeline.org SEO score

100

Search Engine Optimization Advices

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 Ga2.mylifeline.org 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 Ga2.mylifeline.org 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

ga2.mylifeline.org

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