Access philipslifeline.com. Lifeline

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value2,580 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

philipslifeline.com

148 ms

www.lifeline.philips.com

475 ms

iframe_api

145 ms

common-clientlibs.min.css

82 ms

global.min.css

156 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Philipslifeline.com, 69% (60 requests) were made to Lifeline.philips.com and 6% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Lifeline.philips.com.

Content Size

8.5 MB

After Optimization

2.7 MB

In fact, the total size of Philipslifeline.com main page is 8.5 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. 80% 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 5.7 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 360.4 kB

Original 405.4 kB
After minification 291.5 kB
After compression 45.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 114.0 kB, which is 28% 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 360.4 kB or 89% of the original size.

Image Optimization

-64%

Potential reduce by 3.7 MB

Original 5.7 MB
After minification 2.0 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, Philips Lifeline needs image optimization as it can save up to 3.7 MB or 64% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 1.2 MB

Original 1.7 MB
After minification 1.7 MB
After compression 542.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.2 MB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 550.5 kB

Original 640.7 kB
After minification 634.9 kB
After compression 90.2 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. Philipslifeline.com needs all CSS files to be minified and compressed as it can save up to 550.5 kB or 86% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

These are opportunities to improve the legibility of your content.

High

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

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.

High

Links do not have a discernible name

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

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Philipslifeline.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Philipslifeline.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

philipslifeline.com

Open Graph data is detected on the main page of Philips Lifeline. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Lifeline | Medical Alert Systems

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

philipslifeline.com

www.lifeline.philips.com

iframe_api

common-clientlibs.min.css

global.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

philipslifeline.com

www.lifeline.philips.com

iframe_api

common-clientlibs.min.css

global.min.css

components.min.css

blog.min.css

modernizr.js

respond.js

addthis_widget.js

global.min.js

components.min.js

searchbox-clientlibs.min.js

jquery.xdomainrequest.min.js

conversion_async.js

conversion.js

googleanalytics.min.js

2605510322.js

s_code_philipsglobal.js

adaptiveimage.min.js

prodcompare.min.css

prodcompare.min.js

quickview.min.css

quickview.min.js

www-widgetapi.js

new-logo.png

ajax-loader.gif

1458139196877.jpg

sticky-speech-bubble.png

stickybar-phone-icon.png

carat-down.png

carat-up.png

btn-callnow-mobile.png

modal-close-icon.png

1452099816847.png

HomeSafe_StandardLL_sm.png

HomeSafeAA_sm.png

tile-gosafe-img.png

response-app-tile.png

med-disp-tile-img.png

HomeSafe-logo.png

p-gosafe-icon1.png

p-lifeline-icon.png