2.7 sec in total
238 ms
2.2 sec
199 ms
Click here to check amazing Life Sign content. Otherwise, check out these important facts you probably never knew about lifesign.com
QuitKey helps you quit smoking gradually. QuitKey is scientifically proven to help you stop smoking without side effects and weans you off nicotine for good.
Visit lifesign.comWe analyzed Lifesign.com page load time and found that the first response time was 238 ms and then it took 2.4 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.
lifesign.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value5.0 s
27/100
25%
Value7.4 s
28/100
10%
Value2,920 ms
3/100
30%
Value0.01
100/100
15%
Value21.4 s
1/100
10%
238 ms
185 ms
277 ms
206 ms
276 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Lifesign.com, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Lifesign.com.
Page size can be reduced by 56.4 kB (15%)
366.0 kB
309.6 kB
In fact, the total size of Lifesign.com main page is 366.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. 15% of websites need less resources to load. Images take 314.1 kB which makes up the majority of the site volume.
Potential reduce by 9.8 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 5.1 kB, which is 41% 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 9.8 kB or 78% of the original size.
Potential reduce by 26.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. Life Sign images are well optimized though.
Potential reduce by 34 B
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.
Potential reduce by 19.9 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. Lifesign.com needs all CSS files to be minified and compressed as it can save up to 19.9 kB or 89% of the original size.
Number of requests can be reduced by 5 (20%)
25
20
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life Sign. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
lifesign.com
238 ms
style.css
185 ms
quitkey.png
277 ms
tag01.png
206 ms
tag02.png
276 ms
contact.png
145 ms
quitkey_banner.png
2044 ms
qkincldimg01.png
303 ms
qkincldimg02.png
302 ms
ad01.png
271 ms
facebook.png
254 ms
twitter.png
257 ms
pinterest.png
257 ms
googleplus.png
291 ms
ga.js
10 ms
nav_bg.png
179 ms
liborder_bg.png
187 ms
conshadow_bg.png
190 ms
iconli_bg.png
189 ms
qknlcldbg_top.png
215 ms
qknlcldbg_mid.png
251 ms
headbg_btm.png
249 ms
liarrow.png
252 ms
ordernow_btn.png
253 ms
qknlcldbg_btm.png
269 ms
__utm.gif
13 ms
lifesign.com accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lifesign.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lifesign.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifesign.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 Lifesign.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.
lifesign.com
Open Graph description is not detected on the main page of Life Sign. 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: