Tools & Wizards About Us
lifelinelanding.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

lifelinelanding.com

Enroll for FREE Government Cell Phone Service - Lifeline Landing

Page Load Speed

2.6 sec in total

First Response

167 ms

Resources Loaded

2.1 sec

Page Rendered

377 ms

lifelinelanding.com screenshot

About Website

Welcome to lifelinelanding.com homepage info - get ready to check Lifeline Landing best content right away, or after learning these important things about lifelinelanding.com

Lifeline Landing partners with leading National Wireless Carriers to provide a FREE cellular phone. Sign Up Today to avail free government cell phone service.

Visit lifelinelanding.com

Key Findings

We analyzed Lifelinelanding.com page load time and found that the first response time was 167 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

lifelinelanding.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value680 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

lifelinelanding.com

167 ms

www.lifelinelanding.com

417 ms

style.css

187 ms

www.lifelinelanding.com

260 ms

clockface.css

193 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 87% of them (75 requests) were addressed to the original Lifelinelanding.com, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (686 ms) belongs to the original domain Lifelinelanding.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 219.1 kB (30%)

Content Size

729.8 kB

After Optimization

510.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lifelinelanding.com main page is 729.8 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. 50% of websites need less resources to load. Javascripts take 309.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 41.2 kB

  • Original 50.1 kB
  • After minification 35.2 kB
  • After compression 9.0 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 14.9 kB, which is 30% 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 41.2 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 25.2 kB

  • Original 307.8 kB
  • After minification 282.7 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. Lifeline Landing images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 136.4 kB

  • Original 309.7 kB
  • After minification 309.7 kB
  • After compression 173.3 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 136.4 kB or 44% of the original size.

CSS Optimization

-26%

Potential reduce by 16.4 kB

  • Original 62.1 kB
  • After minification 62.1 kB
  • After compression 45.7 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. Lifelinelanding.com needs all CSS files to be minified and compressed as it can save up to 16.4 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (57%)

Requests Now

77

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lifelinelanding.com

lifelinelanding.com

167 ms

www.lifelinelanding.com

www.lifelinelanding.com

417 ms

style.css

style.css

187 ms

www.lifelinelanding.com

www.lifelinelanding.com

260 ms

clockface.css

clockface.css

193 ms

timepicker.css

timepicker.css

194 ms

datepicker.css

datepicker.css

195 ms

main.css

main.css

195 ms

modernizr.js

modernizr.js

250 ms

jsapi

jsapi

23 ms

jquery.min.js

jquery.min.js

19 ms

loader.js

loader.js

18 ms

tinynav.js

tinynav.js

196 ms

superfish.js

superfish.js

196 ms

jquery.sticky.js

jquery.sticky.js

197 ms

jquery.ui.totop.js

jquery.ui.totop.js

197 ms

camera.js

camera.js

318 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

257 ms

jquery.fancybox.js

jquery.fancybox.js

322 ms

carousel.js

carousel.js

260 ms

jquery.tweet.js

jquery.tweet.js

261 ms

jflickrfeed.min.js

jflickrfeed.min.js

261 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

320 ms

jquery.nicescroll.js

jquery.nicescroll.js

388 ms

gmap3.js

gmap3.js

325 ms

jquery.isotope.js

jquery.isotope.js

388 ms

theme-options.js

theme-options.js

381 ms

jquery.cookies.js

jquery.cookies.js

383 ms

bootstrap.js

bootstrap.js

447 ms

main.js

main.js

388 ms

bootstrap-colorpicker.js

bootstrap-colorpicker.js

444 ms

date.js

date.js

445 ms

daterangepicker.js

daterangepicker.js

449 ms

clockface.js

clockface.js

450 ms

bootstrap-timepicker.js

bootstrap-timepicker.js

451 ms

jquery.bootstrap.wizard.js

jquery.bootstrap.wizard.js

508 ms

bootstrap-datepicker.js

bootstrap-datepicker.js

506 ms

bootstrap.css

bootstrap.css

455 ms

bootstrap-theme.css

bootstrap-theme.css

395 ms

jquery.fancybox.css

jquery.fancybox.css

396 ms

theme-options.css

theme-options.css

396 ms

css

css

21 ms

animate.css

animate.css

503 ms

camera.css

camera.css

440 ms

owl.carousel.css

owl.carousel.css

456 ms

owl.theme.css

owl.theme.css

454 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

454 ms

flickr.css

flickr.css

447 ms

font-awesome.min.css

font-awesome.min.css

451 ms

ga.js

ga.js

193 ms

panelbg.png

panelbg.png

193 ms

logo.png

logo.png

686 ms

cubes.png

cubes.png

186 ms

logo.png

logo.png

185 ms

arrow_box_action.png

arrow_box_action.png

186 ms

1.jpg

1.jpg

186 ms

2.jpg

2.jpg

185 ms

3.jpg

3.jpg

548 ms

4.jpg

4.jpg

553 ms

5.jpg

5.jpg

548 ms

6.jpg

6.jpg

550 ms

7.jpg

7.jpg

549 ms

8.jpg

8.jpg

552 ms

bg.jpg

bg.jpg

555 ms

1.png

1.png

553 ms

2.png

2.png

552 ms

3.png

3.png

552 ms

4.png

4.png

553 ms

5.png

5.png

554 ms

6.png

6.png

554 ms

arrow_footer.png

arrow_footer.png

588 ms

big.png

big.png

588 ms

camera-loader.gif

camera-loader.gif

405 ms

1.jpg

1.jpg

500 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

360 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

363 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

363 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

401 ms

counter.js

counter.js

57 ms

__utm.gif

__utm.gif

17 ms

t.php

t.php

148 ms

blue.css

blue.css

75 ms

logo.png

logo.png

79 ms

mCSB_buttons.png

mCSB_buttons.png

79 ms

ui.totop.png

ui.totop.png

79 ms

patttern-corporate.png

patttern-corporate.png

127 ms

Accessibility Review

lifelinelanding.com accessibility score

69

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.

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

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

lifelinelanding.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lifelinelanding.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

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

High

Tap targets are not sized appropriately

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 Lifelinelanding.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 Lifelinelanding.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

lifelinelanding.com

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