Tools & Wizards About Us
ga2.mylifeline.org screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    26% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

ga2.mylifeline.org

MyLifeLine | transform cancer experiences with community connections

Page Load Speed

2.8 sec in total

First Response

130 ms

Resources Loaded

2 sec

Page Rendered

612 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 130 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ga2.mylifeline.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value15,140 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.345

32/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

ga2.mylifeline.org

130 ms

ga2.mylifeline.org

404 ms

gtm.js

487 ms

js

920 ms

js

1083 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 64% of them (38 requests) were addressed to the original Ga2.mylifeline.org, 10% (6 requests) were made to Googletagmanager.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ga2.mylifeline.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.6 kB (24%)

Content Size

567.0 kB

After Optimization

429.4 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-80%

Potential reduce by 122.3 kB

  • Original 153.4 kB
  • After minification 115.0 kB
  • After compression 31.1 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 38.4 kB, which is 25% 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 122.3 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 15.0 kB

  • Original 306.9 kB
  • After minification 291.9 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. Ga 2 My Life Line images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 286 B

  • Original 106.7 kB
  • After minification 106.7 kB
  • After compression 106.4 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 25 (54%)

Requests Now

46

After Optimization

21

  • AJAX
  • Images
  • JavaScript

The browser has sent 46 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 26 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

ga2.mylifeline.org

ga2.mylifeline.org

130 ms

ga2.mylifeline.org

ga2.mylifeline.org

404 ms

gtm.js

gtm.js

487 ms

js

js

920 ms

js

js

1083 ms

hotjar-1196573.js

hotjar-1196573.js

1083 ms

fbevents.js

fbevents.js

559 ms

jquery.min.js

jquery.min.js

323 ms

bootstrap.min.js

bootstrap.min.js

687 ms

lazyload.min.js

lazyload.min.js

685 ms

cookieconsent.min.js

cookieconsent.min.js

687 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

700 ms

moment.min.js

moment.min.js

726 ms

class.7d16c294170d7e010232.js

class.7d16c294170d7e010232.js

703 ms

export.3bdaae622682a98a1f92.js

export.3bdaae622682a98a1f92.js

704 ms

global-js.6f60216305d60933b58b.js

global-js.6f60216305d60933b58b.js

729 ms

search-js.2a6e0a45da485d40b970.js

search-js.2a6e0a45da485d40b970.js

682 ms

home-bundle-js.fd2a9db6dd059017bc52.js

home-bundle-js.fd2a9db6dd059017bc52.js

683 ms

csc-gc_2021.svg

csc-gc_2021.svg

734 ms

banner-photo-min-05262022-en.webp

banner-photo-min-05262022-en.webp

1122 ms

feature-video-overlay.webp

feature-video-overlay.webp

731 ms

kristen-image.webp

kristen-image.webp

752 ms

phone-message-icon.png

phone-message-icon.png

820 ms

laptop-pencil-icon.png

laptop-pencil-icon.png

893 ms

hand-heart-icon.png

hand-heart-icon.png

894 ms

guidestar_2021.png

guidestar_2021.png

965 ms

charity-navigator.png

charity-navigator.png

965 ms

339670743146325

339670743146325

278 ms

hotjar-870267.js

hotjar-870267.js

475 ms

analytics.js

analytics.js

470 ms

bat.js

bat.js

511 ms

js

js

310 ms

js

js

436 ms

js

js

312 ms

conversion_async.js

conversion_async.js

407 ms

modules.61e17720cf639c3e96a7.js

modules.61e17720cf639c3e96a7.js

306 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

271 ms

collect

collect

106 ms

collect

collect

100 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

47 ms

fontawesome-webfont.woff2

fontawesome-webfont.woff2

55 ms

collect

collect

131 ms

151 ms

ProximaNovaBold.woff

ProximaNovaBold.woff

96 ms

ProximaNovaLight.woff

ProximaNovaLight.woff

7 ms

ProximaNovaRegular.woff

ProximaNovaRegular.woff

4 ms

ProximaNovaSemibold.woff

ProximaNovaSemibold.woff

4 ms

ionicons.woff

ionicons.woff

4 ms

ga-audiences

ga-audiences

15 ms

ionicons.woff2

ionicons.woff2

4 ms

Flaticon.woff

Flaticon.woff

2 ms

icomoon.woff

icomoon.woff

2 ms

icomoon.woff2

icomoon.woff2

2 ms

22 ms

dashboard_vector.png

dashboard_vector.png

42 ms

blogging_vector.png

blogging_vector.png

12 ms

calendar_vector.png

calendar_vector.png

13 ms

keepsake_vector.png

keepsake_vector.png

14 ms

board_vector.png

board_vector.png

12 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

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

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

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ga2.mylifeline.org SEO score

93

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: