10.2 sec in total
218 ms
5.5 sec
4.5 sec
Welcome to alive.com homepage info - get ready to check Alive best content for United States right away, or after learning these important things about alive.com
For more than 40 years alive magazine has brought readers tips, articles and recipes to improve your health and wellness. Read on and share with your friends.
Visit alive.comWe analyzed Alive.com page load time and found that the first response time was 218 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
alive.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value4.5 s
37/100
25%
Value32.4 s
0/100
10%
Value68,470 ms
0/100
30%
Value0.002
100/100
15%
Value91.6 s
0/100
10%
218 ms
2059 ms
97 ms
169 ms
169 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 27% of them (27 requests) were addressed to the original Alive.com, 24% (24 requests) were made to D2mdn1s78c9h86.cloudfront.net and 15% (15 requests) were made to Ads.alive.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Alive.com.
Page size can be reduced by 1.1 MB (22%)
5.0 MB
3.9 MB
In fact, the total size of Alive.com main page is 5.0 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. Only a small number of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 66.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.3 kB or 79% of the original size.
Potential reduce by 364.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. Alive images are well optimized though.
Potential reduce by 550.2 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 550.2 kB or 71% of the original size.
Potential reduce by 105.6 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. Alive.com needs all CSS files to be minified and compressed as it can save up to 105.6 kB or 81% of the original size.
Number of requests can be reduced by 46 (56%)
82
36
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
alive.com
218 ms
www.alive.com
2059 ms
wp-emoji-release.min.js
97 ms
widget.css
169 ms
menu-image.css
169 ms
default.css
171 ms
lightbox.css
182 ms
pagenavi-css.css
180 ms
css
59 ms
style.min.css
306 ms
jquery.js.gzip
59 ms
jquery-migrate.min.js.gzip
55 ms
lightbox.min.js
242 ms
wpembedfb.js
241 ms
fb.js
245 ms
modernizr.js.gzip
56 ms
main.min.js.gzip
84 ms
foundation.min.js.gzip
53 ms
fl.js
1808 ms
spcjs.php
1817 ms
js
87 ms
handlebars-1.0.0.min.js
433 ms
jquery.storelocator.js
433 ms
buttons.js
48 ms
2de0a4
23 ms
logo-alive.png
77 ms
logo-alive-alt.png
65 ms
cancer-front-blur_296283794.jpg
191 ms
mushroom-cord_94947103.jpg
260 ms
windmill_274473437.jpg
252 ms
stuartfitbit1.jpg
69 ms
04-April-Balance.jpg
64 ms
Moducare_March.jpg
65 ms
spices-front_225001330.jpg
267 ms
Warm-Salade-Ni%C3%A7oise-with-Baked-Eggs-CK7B5070-dark.jpg
297 ms
One-Pot-Tuscan-Spelt-and-Zucchini-Noodles-CK7B9196.jpg
262 ms
70224e54fa5d15a8c291b1b706cb0d63.jpg
191 ms
img-alive-magazine.jpg
191 ms
alive-publishing-header-logo.png
192 ms
alive-studios.png
242 ms
alive-listens.png
242 ms
alive-academy.png
244 ms
alive-interactive-color@2x.png
252 ms
alive-awards@2x.png
253 ms
close.png
182 ms
loading.gif
179 ms
prev.png
182 ms
next.png
177 ms
logo-alive-black.png
212 ms
2DE0A4_13_0.woff
240 ms
2DE0A4_11_0.woff
294 ms
2DE0A4_D_0.woff
281 ms
So5lHxHT37p2SS4-t60SlCtfYakCkPqOMDce0h_3gD8.ttf
110 ms
EYh7Vl4ywhowqULgRdYwIH3uxQAI1Bvm-GxtFNy4yl0.ttf
112 ms
EYh7Vl4ywhowqULgRdYwICxQL91WRy8t8mPvAX_dIgA.ttf
115 ms
RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf
116 ms
ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf
116 ms
ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf
113 ms
fontawesome-webfont.woff
293 ms
2DE0A4_B_0.woff
203 ms
flag-can@2x.png
206 ms
flag-usa@2x.png
206 ms
flag-aus@2x.png
212 ms
fl.js
98 ms
spcjs.php
419 ms
spc.php
115 ms
fl.js
111 ms
gtm.js
176 ms
all.js
294 ms
getAllAppDefault.esi
36 ms
76caa14aa42c227e75522739abeab219.jpg
318 ms
lg.php
127 ms
b21345dc858ce37ddbdb5f37db209aaa.png
232 ms
lg.php
182 ms
12a86685f5c8b117a3df097a3c7f67bf.png
228 ms
lg.php
231 ms
42e42ab93d7eb4d1ac2d9cc6db3a742c.jpg
325 ms
lg.php
302 ms
lg.php
328 ms
analytics.js
7 ms
collect
17 ms
getSegment.php
189 ms
checkOAuth.esi
10 ms
jquery.form-n-validate.js
57 ms
174 ms
t.dhj
67 ms
xd_arbiter.php
219 ms
xd_arbiter.php
426 ms
t.dhj
53 ms
cm
50 ms
x35248
90 ms
s-3271.xgi
14 ms
31 ms
hbpix
27 ms
11 ms
xrefid.xgi
8 ms
pixel
20 ms
pixel
22 ms
2981
34 ms
alive.com accessibility score
alive.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
alive.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alive.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 Alive.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.
alive.com
Open Graph data is detected on the main page of Alive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: