4.8 sec in total
126 ms
3.2 sec
1.4 sec
Welcome to blog.lef.org homepage info - get ready to check Blog Lef best content for United States right away, or after learning these important things about blog.lef.org
The Wellness Blog is a science-based blog publishing articles about vitamins & supplements, nutrition, self-care & healthy living tips.
Visit blog.lef.orgWe analyzed Blog.lef.org page load time and found that the first response time was 126 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
blog.lef.org performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value7.6 s
3/100
25%
Value4.9 s
65/100
10%
Value4,160 ms
1/100
30%
Value0.006
100/100
15%
Value15.3 s
7/100
10%
126 ms
56 ms
116 ms
83 ms
29 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Blog.lef.org, 14% (19 requests) were made to Static.xx.fbcdn.net and 7% (10 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (802 ms) relates to the external source Connect.facebook.net.
Page size can be reduced by 637.5 kB (35%)
1.8 MB
1.2 MB
In fact, the total size of Blog.lef.org main page is 1.8 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. 75% 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 878.7 kB which makes up the majority of the site volume.
Potential reduce by 290.9 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 290.9 kB or 75% of the original size.
Potential reduce by 19.4 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. Blog Lef images are well optimized though.
Potential reduce by 327.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 327.3 kB or 58% of the original size.
Potential reduce by 9 B
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. Blog.lef.org has all CSS files already compressed.
Number of requests can be reduced by 76 (58%)
131
55
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Lef. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
blog.lifeextension.com
126 ms
3645911276-widget_css_bundle.css
56 ms
authorization.css
116 ms
plusone.js
83 ms
widgets.js
29 ms
addthis_widget.js
45 ms
widget.js
39 ms
widget.js
72 ms
3226477086-widgets.js
38 ms
ga.js
178 ms
fbds.js
245 ms
header_bg.gif
244 ms
cb=gapi.loaded_0
168 ms
cb=gapi.loaded_1
167 ms
google_top_exp.js
167 ms
1x1trans.gif
167 ms
chickpea-tomato-chicken.jpg
487 ms
icon18_email.gif
282 ms
boundless.jpg
425 ms
immune.jpg
430 ms
pixel.png
116 ms
feed-icon32x32.png
241 ms
FitMom%2BPic%2Bfor%2BBio.jpg
357 ms
icon18_wrench_allbkg.png
253 ms
tired.jpg
367 ms
digestion-IBS-woman-stomach.jpg
397 ms
get_custom_js
294 ms
navbar.g
257 ms
blank.html
193 ms
header_bg.ashx
140 ms
562 ms
cb=gapi.loaded_2
168 ms
cb=gapi.loaded_3
170 ms
fastbutton
346 ms
fastbutton
341 ms
fastbutton
289 ms
fastbutton
273 ms
fastbutton
269 ms
badge
532 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
256 ms
300lo.json
214 ms
all.js&version=v2.0
802 ms
header_Blog_LE.ashx
171 ms
sh.8e5f85691f9aaa082472a194.html
46 ms
returnToBlogHome2.ashx
141 ms
1x1trans.ashx
161 ms
collect
372 ms
postmessageRelay
311 ms
img18.ashx
666 ms
footer_bg.ashx
152 ms
icons_peach.png
165 ms
platform:gapi.iframes.style.common.js
164 ms
arrows-light.png
275 ms
show_widget
50 ms
tc.js
75 ms
149 ms
vglnk.js
88 ms
418034017.jpg
102 ms
229881765.jpg
74 ms
185723835.jpg
201 ms
395683769.jpg
205 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
94 ms
likebox.php
288 ms
p
237 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
137 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
170 ms
pixel.gif
154 ms
pixel.gif
159 ms
mapuid
151 ms
cb=gapi.loaded_0
156 ms
cb=gapi.loaded_1
157 ms
ga-audiences
101 ms
demconf.jpg
63 ms
3193398744-postmessagerelay.js
178 ms
rpc:shindig_random.js
74 ms
cb=gapi.loaded_0
62 ms
cb=gapi.loaded_1
59 ms
fastbutton
272 ms
grlryt2bdKIyfMSOhzd1eA.woff
310 ms
rs=AGLTcCObu_AspndiuVgsAof6R5t3WzcDSA
78 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
86 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
132 ms
ebiMDO3r-8l.css
443 ms
jGc-59L_9lo.css
542 ms
6qHpHChjY_J.css
564 ms
ztINr5qMqM_.css
638 ms
QnQTU9p4OI_.js
644 ms
Yuj_Y8xNH2C.js
686 ms
Mpe38fuBVZ2.js
606 ms
n8qIhCw3vMx.js
607 ms
QKy94bWvcbp.js
620 ms
6q5od22S-uf.js
659 ms
7B-2ZS3Qt8r.js
705 ms
qcMicXoOToy.js
763 ms
57RpJa05x58.js
713 ms
269 ms
postmessageRelay
218 ms
cb=gapi.loaded_0
119 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
63 ms
v2
179 ms
d-QWLnp4didxos_6urzFtg.woff
88 ms
vxNK-E6B13CyehuDCmvQvw.woff
89 ms
xrefid.xgi
64 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
33 ms
ping
162 ms
127 ms
dpx
13 ms
52154.gif
14 ms
xd_arbiter.php
167 ms
xd_arbiter.php
293 ms
ca.png
187 ms
jot.html
15 ms
domains
55 ms
pixel.gif
58 ms
11988537_10153109389516868_5673088349601587620_n.jpg
178 ms
10294225_10152134187136868_4733116153907237727_n.jpg
216 ms
10441359_10204180730758152_7575798696832224979_n.jpg
259 ms
10986677_10204054070929790_2345965376455453438_n.jpg
291 ms
424770_513070198707328_910748973_n.jpg
301 ms
10361570_10201420792838212_1514220705149230492_n.jpg
298 ms
1934069_10153479804576868_8739280898404212878_n.jpg
297 ms
12226994_10153477275601868_7369468240299455301_n.jpg
294 ms
1453219_10153474581921868_1479873299231274123_n.jpg
301 ms
wL6VQj7Ab77.png
47 ms
s7jcwEQH7Sx.png
47 ms
QDwYpIaRyfG.png
46 ms
VXcANLwwL5J.js
44 ms
AmlxWlqMvlv.js
92 ms
47154.gif
7 ms
ping
61 ms
22 ms
like.php
81 ms
like.php
105 ms
like.php
158 ms
like.php
172 ms
like.php
126 ms
LVx-xkvaJ0b.png
44 ms
blog.lef.org accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
blog.lef.org 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
blog.lef.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.lef.org 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 Blog.lef.org 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.
blog.lef.org
Open Graph description is not detected on the main page of Blog Lef. 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: