2.6 sec in total
207 ms
2.2 sec
203 ms
Click here to check amazing Forever content. Otherwise, check out these important facts you probably never knew about forever.io
We are a private, humanitarian initiative with the mission of enabling people to vastly extend their healthy lifespan.
Visit forever.ioWe analyzed Forever.io page load time and found that the first response time was 207 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
forever.io performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.4 s
20/100
25%
Value5.7 s
52/100
10%
Value970 ms
28/100
30%
Value0.002
100/100
15%
Value10.4 s
24/100
10%
207 ms
550 ms
101 ms
566 ms
590 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Forever.io, 98% (52 requests) were made to Forever-healthy.org. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Forever-healthy.org.
Page size can be reduced by 2.1 MB (84%)
2.4 MB
390.6 kB
In fact, the total size of Forever.io main page is 2.4 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. 55% of websites need less resources to load. CSS take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 121.5 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 121.5 kB or 84% of the original size.
Potential reduce by 336.4 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 336.4 kB or 69% of the original size.
Potential reduce by 1.6 MB
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. Forever.io needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 88% of the original size.
Number of requests can be reduced by 36 (82%)
44
8
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forever. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
forever.io
207 ms
forever-healthy.org
550 ms
classic-themes.min.css
101 ms
style.min.css
566 ms
style-media-min-md.min.css
590 ms
style-media-min-lg.min.css
583 ms
elementor-icons.min.css
392 ms
custom-frontend.min.css
671 ms
swiper.min.css
394 ms
post-11.css
488 ms
custom-pro-frontend.min.css
868 ms
post-1630.css
597 ms
post-1699.css
660 ms
post-1690.css
661 ms
borlabs-cookie_1_en.css
664 ms
jquery.min.js
894 ms
jquery-migrate.min.js
754 ms
borlabs-cookie-prioritize.min.js
757 ms
vendor.min.js
756 ms
main.min.js
761 ms
ajax-load-more.min.js
847 ms
wpml-switch-language.min.js
849 ms
jquery.smartmenus.min.js
851 ms
borlabs-cookie.min.js
857 ms
webpack-pro.runtime.min.js
966 ms
webpack.runtime.min.js
967 ms
frontend-modules.min.js
967 ms
wp-polyfill-inert.min.js
967 ms
regenerator-runtime.min.js
967 ms
wp-polyfill.min.js
968 ms
hooks.min.js
1039 ms
i18n.min.js
1039 ms
frontend.min.js
1057 ms
waypoints.min.js
1058 ms
core.min.js
1060 ms
frontend.min.js
1062 ms
elements-handlers.min.js
1133 ms
fa-custom.min.js
1135 ms
lazyload.min.js
1056 ms
forever-shape.svg
274 ms
open-sans-v27-latin-regular.woff
224 ms
open-sans-v27-latin-600.woff
224 ms
CaeciliaLTStd-BoldItalic.woff
277 ms
montserrat-v23-latin-700.woff
277 ms
montserrat-v23-latin-600.woff
278 ms
montserrat-v23-latin-500.woff
278 ms
montserrat-v23-latin-regular.woff
293 ms
logo_forever-healthy_white.svg
98 ms
logo_forever-healthy_black.svg
134 ms
Website-Support-Initiativen-FH-Longevity-HiRes-20-07-768x768.jpg.webp
137 ms
Website-Support-Initiativen-FH-Health-HiRes-20-07-768x768.jpg.webp
139 ms
Website-Support-Initiativen-FH-Rejuvenation-MedRes-20-07-768x768.jpg.webp
149 ms
style-media-min-xl.min.css
100 ms
forever.io accessibility score
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
Links do not have a discernible name
forever.io 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
forever.io 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 Forever.io 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 Forever.io 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.
forever.io
Open Graph data is detected on the main page of Forever. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: