10.1 sec in total
817 ms
9 sec
281 ms
Click here to check amazing Lifeforte content for Nigeria. Otherwise, check out these important facts you probably never knew about lifeforte.com
Visit lifeforte.comWe analyzed Lifeforte.com page load time and found that the first response time was 817 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lifeforte.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value11.6 s
0/100
25%
Value10.6 s
7/100
10%
Value730 ms
40/100
30%
Value0.003
100/100
15%
Value11.2 s
19/100
10%
817 ms
221 ms
283 ms
113 ms
115 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lifeforte.com, 3% (3 requests) were made to Themes.googleusercontent.com. The less responsive or slowest element that took the longest time to load (817 ms) relates to the external source Lifeforte.org.
Page size can be reduced by 1.1 MB (23%)
4.7 MB
3.6 MB
In fact, the total size of Lifeforte.com main page is 4.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. 50% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 47.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. This page needs HTML code to be minified as it can gain 7.7 kB, which is 14% 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 47.3 kB or 88% of the original size.
Potential reduce by 868.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. Obviously, Lifeforte needs image optimization as it can save up to 868.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 100.7 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 100.7 kB or 70% of the original size.
Potential reduce by 38.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. Lifeforte.com needs all CSS files to be minified and compressed as it can save up to 38.9 kB or 83% of the original size.
Number of requests can be reduced by 24 (25%)
96
72
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifeforte. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
index.html
817 ms
normalize.css
221 ms
style.css
283 ms
grid.css
113 ms
css_004.css
115 ms
css.css
114 ms
css_002.css
169 ms
css_003.css
170 ms
slider_002.js
224 ms
imagepreloader.js
216 ms
wt-rotator.css
271 ms
jquery-1.js
507 ms
jquery_002x.js
334 ms
preview.js
226 ms
slider_2_prev_active.png
58 ms
slider_2_next_active.png
58 ms
slider_button_next_active.png
58 ms
slider_button_prev_active.png
87 ms
top-header-bg.jpg
112 ms
top-header-line.png
58 ms
lifefortelogo.png
204 ms
nav-bg.gif
60 ms
nav-primary-bg.jpg
61 ms
divider.png
62 ms
menu-arrow.png
113 ms
slider-bg.gif
115 ms
loader.gif
117 ms
p50.jpg
340 ms
p1.jpg
280 ms
p2.jpg
395 ms
p3.jpg
453 ms
p4.jpg
229 ms
p5.jpg
316 ms
p6.jpg
341 ms
p7.jpg
391 ms
p8.jpg
429 ms
p9.jpg
454 ms
p10.jpg
455 ms
p11.jpg
505 ms
p12.jpg
567 ms
p13.jpg
539 ms
p14.jpg
623 ms
p15jpg
511 ms
p16.jpg
569 ms
p17.jpg
566 ms
p18.jpg
637 ms
p19.jpg
597 ms
p20.jpg
681 ms
p21.jpg
686 ms
p22.jpg
634 ms
p24.jpg
712 ms
p23.jpg
733 ms
p25.jpg
693 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
19 ms
EInbV5DfGHOiMmvb1Xr-hqRDOzjiPcYnFooOUGCOsRk.woff
73 ms
DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff
37 ms
p26.jpg
755 ms
p27.jpg
741 ms
p28.jpg
744 ms
p29.jpg
698 ms
p31.jpg
776 ms
p30.jpg
739 ms
p32.jpg
705 ms
p34.jpg
765 ms
p35.jpg
741 ms
p36.jpg
659 ms
p38.jpg
651 ms
p37.jpg
666 ms
p39.jpg
644 ms
p40.jpg
632 ms
p41.jpg
635 ms
p42.jpg
598 ms
p43.jpg
550 ms
p44.jpg
626 ms
p45.jpg
554 ms
p46.jpg
566 ms
p47.jpg
575 ms
p15.jpg
531 ms
wrapper-bg.jpg
535 ms
page_title_block_top.jpg
529 ms
page_title_block_bot.jpg
512 ms
page_title_block_left.jpg
523 ms
page_title_block_right.jpg
523 ms
page_title_block_left_top.jpg
505 ms
page_title_block_right_top.jpg
487 ms
page_title_block_left_bot.jpg
483 ms
page_title_block_right_bot.jpg
493 ms
AWARD.jpg
460 ms
british-council-award.jpg
493 ms
slider_2_wrapper.jpg
485 ms
slider_2_bg.png
456 ms
slider_2_prev.png
451 ms
slider_img_box.jpg
437 ms
slider_2_img_1.jpg
445 ms
slider_name_box.jpg
412 ms
slider_2_img_2.jpg
414 ms
slider.jpg
412 ms
slider_2_next.png
398 ms
footer-bg.gif
451 ms
footer-light.png
800 ms
widget-footer-bg.png
403 ms
bottom.png
453 ms
vr.gif
406 ms
footlogo.png
397 ms
hr.gif
369 ms
cambridge.jpg
380 ms
edexcel.jpg
385 ms
waec.jpg
404 ms
vtip.png
399 ms
lifeforte.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
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.
lifeforte.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
Issues were logged in the Issues panel in Chrome Devtools
lifeforte.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifeforte.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 Lifeforte.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.
lifeforte.com
Open Graph description is not detected on the main page of Lifeforte. 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: