50.7 sec in total
257 ms
36.3 sec
14.1 sec
Welcome to principal.com homepage info - get ready to check Principal best content for United States right away, or after learning these important things about principal.com
Let's keep your finances simple. Insure what you have. Invest when you're ready. Retire with confidence.
Visit principal.comWe analyzed Principal.com page load time and found that the first response time was 257 ms and then it took 50.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
principal.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.7 s
1/100
25%
Value45.9 s
0/100
10%
Value36,970 ms
0/100
30%
Value0.07
96/100
15%
Value100.0 s
0/100
10%
257 ms
927 ms
1362 ms
105 ms
3296 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 17% of them (10 requests) were addressed to the original Principal.com, 12% (7 requests) were made to Principalcdn.com and 12% (7 requests) were made to Public.cobrowse.oraclecloud.com. The less responsive or slowest element that took the longest time to load (11.9 sec) relates to the external source Cookies.onetrust.com.
Page size can be reduced by 1.4 MB (36%)
3.9 MB
2.5 MB
In fact, the total size of Principal.com main page is 3.9 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 110.4 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 110.4 kB or 84% of the original size.
Potential reduce by 71.9 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. Principal images are well optimized though.
Potential reduce by 877.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 877.7 kB or 67% of the original size.
Potential reduce by 320.2 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. Principal.com needs all CSS files to be minified and compressed as it can save up to 320.2 kB or 50% of the original size.
Number of requests can be reduced by 28 (54%)
52
24
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Principal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
principal.com
257 ms
www.principal.com
927 ms
horizon.min.css
1362 ms
pcom-3.35.0.min.css
105 ms
horizon.min.js
3296 ms
pcom-3.35.0.min.js
769 ms
tealeaf-ui-sdk.min.js
3173 ms
7eb7bbf7-4039-4965-83e0-069984148f4c.js
1246 ms
tout-icon-rollover-v2.png
1047 ms
setCookie.cgi
8723 ms
tout-icon-check-v2.png
998 ms
fa-calculator_Midnight_bynder.png
7450 ms
gtm.js
7450 ms
audiencehero_nyc_14_1020_2228_bynder.jpg
7823 ms
audiencehero_nyc_14_1020_2228_bynder.jpg
7458 ms
logo-company-name-white.png
6500 ms
1134 ms
global_launcher_acb.js
3031 ms
FSElliotWeb-Regular.woff
1196 ms
FSElliotWeb-Bold.woff
1245 ms
fontawesome-webfont.woff
1296 ms
wrapper.js
1828 ms
jquery.min.js
1719 ms
optanon.css
3971 ms
ll_storage_ie.html
9914 ms
hostui_animation.js
9809 ms
webtrends-min.js
8766 ms
analytics.js
9282 ms
EU
11851 ms
setCookie.cgi
10713 ms
activityi;src=1391526;type=princ0;cat=princ0;ord=503032363904;~oref=https%3A%2F%2Fwww.principal.com%2F
4029 ms
wtid.js
3745 ms
collect
2073 ms
collect
3446 ms
collect
1359 ms
hostui_tc_ie.js
440 ms
collect
1642 ms
conversion.js
3592 ms
v4llpanel_collapsednarrownoagent_background.png
4145 ms
v4llpanelhovertooltipbg.png
1182 ms
v4llpanelminimize.png
2204 ms
v4llpanelpreload.gif
2605 ms
v4llpanel_innerlogo_background.png
3179 ms
v4llpanel_notconnected_background.png
3647 ms
v4llpanel_separator.png
3693 ms
v4llpanel_panelclosebutton_background.png
3692 ms
llpasstobegintext_background.png
3692 ms
2241 ms
fbevents.js
1919 ms
bat.js
2126 ms
blank.gif
2126 ms
516 ms
dcs.gif
1710 ms
1552 ms
191121361292645
179 ms
652 ms
694 ms
424 ms
232 ms
iFrame.html
343 ms
principal.com accessibility score
principal.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
principal.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 Principal.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 Principal.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.
principal.com
Open Graph description is not detected on the main page of Principal. 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: