2.3 sec in total
16 ms
1.7 sec
528 ms
Click here to check amazing Foundation Life content. Otherwise, check out these important facts you probably never knew about foundationlife.com
Compare life insurance quotes and apply in minutes online or over the phone. Need help? Call 1.866.526.7264.
Visit foundationlife.comWe analyzed Foundationlife.com page load time and found that the first response time was 16 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
foundationlife.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value6.2 s
11/100
25%
Value10.2 s
8/100
10%
Value1,830 ms
9/100
30%
Value0.069
96/100
15%
Value15.0 s
7/100
10%
16 ms
303 ms
75 ms
139 ms
195 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Foundationlife.com, 72% (92 requests) were made to Insureinminutes.com and 17% (22 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (666 ms) relates to the external source Insureinminutes.com.
Page size can be reduced by 163.7 kB (16%)
1.0 MB
872.8 kB
In fact, the total size of Foundationlife.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 530.2 kB which makes up the majority of the site volume.
Potential reduce by 125.1 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 125.1 kB or 82% of the original size.
Potential reduce by 3.8 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. Foundation Life images are well optimized though.
Potential reduce by 21.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 12.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. Foundationlife.com has all CSS files already compressed.
Number of requests can be reduced by 92 (90%)
102
10
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foundation Life. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
foundationlife.com
16 ms
insureinminutes.com
303 ms
float-to-top-button.min.css
75 ms
zebra_tooltips.css
139 ms
blocks.style.build.css
195 ms
embedpress.css
189 ms
settings.css
192 ms
fontello.css
188 ms
jquery.qtip.min.css
184 ms
directory.min.css
209 ms
wppopups.css
248 ms
public-main.css
251 ms
wppopups-base.css
252 ms
style.css
254 ms
tablepress-combined.min.css
251 ms
tablepress-responsive.min.css
270 ms
css
51 ms
css2
69 ms
css2
68 ms
elementor-icons.min.css
307 ms
frontend.min.css
315 ms
swiper.min.css
325 ms
post-11290.css
311 ms
embedpress-elementor.css
326 ms
global.css
337 ms
post-7980.css
381 ms
dashicons.min.css
386 ms
plyr.css
383 ms
css
67 ms
jquery.min.js
395 ms
jquery-migrate.min.js
411 ms
wp-polyfill-inert.min.js
415 ms
regenerator-runtime.min.js
440 ms
wp-polyfill.min.js
446 ms
hooks.min.js
444 ms
plyr.polyfilled.js
455 ms
rbtools.min.js
518 ms
rs6.min.js
546 ms
jquery.qtip.min.js
506 ms
jquery.directory.min.js
505 ms
wppopups.js
514 ms
addthis_widget.js
61 ms
30ede005b9.js
76 ms
strife.js
351 ms
css
62 ms
shortcodes.css
539 ms
rs6.css
514 ms
public-main.js
452 ms
jquery.fitvids.js
402 ms
jquery.bxslider.js
402 ms
pmc_infinity.js
401 ms
jquery.scrollUp.min.js
476 ms
float-to-top-button.min.js
478 ms
zebra_tooltips.js
464 ms
wppopups.js
425 ms
pdfobject.min.js
423 ms
initplyr.js
424 ms
vimeo-player.js
517 ms
front.js
539 ms
react.min.js
528 ms
deprecated.min.js
488 ms
dom.min.js
518 ms
react-dom.min.js
506 ms
escape-html.min.js
502 ms
element.min.js
666 ms
is-shallow-equal.min.js
636 ms
i18n.min.js
592 ms
keycodes.min.js
606 ms
priority-queue.min.js
562 ms
compose.min.js
580 ms
private-apis.min.js
575 ms
redux-routine.min.js
577 ms
data.min.js
553 ms
ads.js
547 ms
documents-viewer-script.js
545 ms
morphext.min.js
535 ms
welcomebar-front.js
547 ms
detectmobilebrowser.js
538 ms
mystickymenu.min.js
534 ms
jquery.scrollTo.js
509 ms
retina.min.js
508 ms
custom.js
502 ms
jquery.easing.1.3.js
506 ms
jquery.cycle.all.min.js
508 ms
gistfile_pmc.js
506 ms
jquery.isotope.min.js
506 ms
webfontloader.js
78 ms
comment-reply.min.js
430 ms
core.min.js
483 ms
tabs.min.js
482 ms
webpack.runtime.min.js
482 ms
frontend-modules.min.js
559 ms
waypoints.min.js
480 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
153 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff
164 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
163 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
165 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
164 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
161 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
176 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff
175 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvUDT.woff
176 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vUDT.woff
177 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebukDT.woff
177 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiukDT.woff
177 ms
frontend.min.js
472 ms
30ede005b9.css
104 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff
82 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
85 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexg.woff
83 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexg.woff
82 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
84 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexg.woff
84 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff
85 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff
85 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexg.woff
86 ms
IIM_Favicon.jpg
214 ms
Insureinminutes_logo-a-copy-3-fixed.png
446 ms
dummy.png
446 ms
business-3560914_1920-compressed-and-cropped-for-Google-959x1024.jpg
523 ms
Carrier-Logos-compressed.png
415 ms
quote-icon-hayes.png
414 ms
font-awesome-css.min.css
99 ms
fontawesome-webfont.woff
79 ms
quote.png
95 ms
arrow012.png
63 ms
foundationlife.com 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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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.
foundationlife.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
Issues were logged in the Issues panel in Chrome Devtools
foundationlife.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
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 Foundationlife.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 Foundationlife.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.
foundationlife.com
Open Graph data is detected on the main page of Foundation Life. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: