3.1 sec in total
306 ms
2.2 sec
600 ms
Click here to check amazing I Live Life Well content for United States. Otherwise, check out these important facts you probably never knew about ilivelifewell.com
FB Description
Visit ilivelifewell.comWe analyzed Ilivelifewell.com page load time and found that the first response time was 306 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
ilivelifewell.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value14.2 s
0/100
25%
Value5.6 s
54/100
10%
Value60 ms
100/100
30%
Value0.001
100/100
15%
Value10.1 s
26/100
10%
306 ms
324 ms
147 ms
96 ms
108 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 95% of them (84 requests) were addressed to the original Ilivelifewell.com, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Decibelinsight.net. The less responsive or slowest element that took the longest time to load (653 ms) relates to the external source Decibelinsight.net.
Page size can be reduced by 2.3 MB (62%)
3.7 MB
1.4 MB
In fact, the total size of Ilivelifewell.com main page is 3.7 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. 65% of websites need less resources to load. Javascripts take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 68.6 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 28.7 kB, which is 35% 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 68.6 kB or 82% of the original size.
Potential reduce by 68.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. I Live Life Well images are well optimized though.
Potential reduce by 1.5 MB
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.5 MB or 74% of the original size.
Potential reduce by 619.5 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. Ilivelifewell.com needs all CSS files to be minified and compressed as it can save up to 619.5 kB or 73% of the original size.
Number of requests can be reduced by 65 (78%)
83
18
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Live Life Well. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
ilivelifewell.com
306 ms
default.aspx
324 ms
corev15.css
147 ms
controls15.css
96 ms
boilerplate.css
108 ms
style.css
112 ms
style.min.css
99 ms
font-awesome.css
101 ms
standardmenu.css
142 ms
megamenu.css
171 ms
touch-tooltip.css
183 ms
mightyslider.css
168 ms
mightyslider_mod.css
173 ms
slidePushMenu.css
195 ms
custom.css
200 ms
jquery-1.11.0.min.js
264 ms
jquery-ui.min.js
309 ms
jquery.easing.js
213 ms
modernizr.custom.js
227 ms
megamenu_plugins.js
261 ms
megamenu.js
245 ms
jquery.nav.js
259 ms
modal.box.js
271 ms
add2home.js
290 ms
jquery.SPServices-2014.02.min.js
341 ms
custom.js
302 ms
page.controls.top.js
303 ms
init.js
323 ms
initstrings.js
317 ms
strings.js
357 ms
core.js
358 ms
menu.js
337 ms
mquery.js
346 ms
callout.js
350 ms
clienttemplates.js
369 ms
sharing.js
369 ms
suitelinks.js
375 ms
form.js
348 ms
ScriptResource.axd
302 ms
blank.js
302 ms
ScriptResource.axd
312 ms
WebResource.axd
309 ms
WebResource.axd
304 ms
mightyslider.js
344 ms
classie.js
274 ms
style.css
315 ms
style.css
296 ms
style.css
288 ms
style.css
281 ms
style.css
295 ms
style.css
319 ms
style.css
330 ms
style.css
296 ms
style.css
284 ms
style.css
283 ms
style.css
280 ms
style.css
310 ms
style.css
300 ms
style.css
294 ms
style.css
297 ms
page.controls.bottom.js
286 ms
grid.js
280 ms
di.js
653 ms
analytics.js
467 ms
slider-ie8.html
452 ms
spcommon.png
82 ms
logo-llw.png
81 ms
logo-abbott.png
77 ms
searchresultui.png
75 ms
runner%20icons.png
85 ms
mngr.png
77 ms
heart.png
125 ms
logo-abbott-footer.png
104 ms
blue-bg.png
104 ms
Preloader_6.gif
135 ms
283FBE_4_0.woff
141 ms
283FBE_8_0.woff
235 ms
SliderPreview.css
135 ms
royal-slider-1.0.min.css
133 ms
jquery-1.5.1.min.js
164 ms
jquery.easing.1.3.min.js
178 ms
royal-slider-1.0.min.js
180 ms
collect
19 ms
caregiver-slider.jpg
120 ms
body-for-life-slider.jpg
216 ms
collect
35 ms
sliderBG.png
53 ms
controlsSprite.png
52 ms
ilivelifewell.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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ilivelifewell.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
ilivelifewell.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Ilivelifewell.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 Ilivelifewell.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.
ilivelifewell.com
Open Graph data is detected on the main page of I Live Life Well. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: