2.6 sec in total
196 ms
2.1 sec
260 ms
Visit putnam.com now to see the best up-to-date Putnam content for United States and also check out these interesting facts you probably never knew about putnam.com
Putnam offers actively-managed mutual funds and Institutional strategies across equities, fixed income, absolute return, and alternatives.
Visit putnam.comWe analyzed Putnam.com page load time and found that the first response time was 196 ms and then it took 2.4 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.
putnam.com performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value3.4 s
67/100
25%
Value3.3 s
90/100
10%
Value1,510 ms
14/100
30%
Value0.003
100/100
15%
Value10.4 s
24/100
10%
196 ms
88 ms
88 ms
96 ms
634 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 45% of them (34 requests) were addressed to the original Putnam.com, 11% (8 requests) were made to Use.typekit.net and 8% (6 requests) were made to D.putnam.com. The less responsive or slowest element that took the longest time to load (634 ms) belongs to the original domain Putnam.com.
Page size can be reduced by 1.5 MB (60%)
2.5 MB
996.3 kB
In fact, the total size of Putnam.com main page is 2.5 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. 60% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 145.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. 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 145.3 kB or 77% of the original size.
Potential reduce by 30.2 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. Putnam images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 72% of the original size.
Potential reduce by 157.1 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. Putnam.com needs all CSS files to be minified and compressed as it can save up to 157.1 kB or 83% of the original size.
Number of requests can be reduced by 39 (62%)
63
24
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Putnam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.putnam.com
196 ms
style.css
88 ms
plugins.css
88 ms
main.css
96 ms
splash.css
634 ms
maneuver-in-market.css
85 ms
modernizr-2.6.2.min.js
148 ms
jzf3eve.js
261 ms
index.min.js
268 ms
index.min.js
449 ms
jquery.min.js
102 ms
main.js
54 ms
plugins.js
101 ms
scroller.plugins.js
68 ms
EasyScrollerExtended.js
74 ms
ss.js
68 ms
splash.js
83 ms
blueconic.min.js
294 ms
Bootstrap.js
58 ms
analytics.js
228 ms
BrightcoveExperiences.js
379 ms
APIModules_all.js
448 ms
browser_bg.jpg
62 ms
www.putnam.com
68 ms
section-grey-link5.png
65 ms
section-grey-link4.png
64 ms
section-gray-link-down.png
64 ms
section-gray-link2.png
171 ms
serverComponent.php
63 ms
logo.png
154 ms
icon-branding-carat-sm.png
153 ms
responsive-spacer-nav.png
154 ms
inv_strat_sh_minm_ex.jpg
157 ms
inv_strat_splash_copy_lg.jpg
157 ms
icon_twitter_med.png
306 ms
cmo_q116_feat_img.jpg
378 ms
fv2_logo.png
156 ms
fv_appstore.png
305 ms
fv_gplay.png
153 ms
fv_online.png
304 ms
fv_correlation_lg.png
306 ms
icon-pats.png
304 ms
icon-celtics.png
305 ms
icon_ted2.png
376 ms
icon_golf.png
375 ms
icomoon.ttf
151 ms
0cc8ebac9f8b8bf5969860c5a3411c4e.js
248 ms
f81be21f196fa6e96049c04ff78199c4.js
222 ms
ypvk_yI2b-_vul5TuOuCZyV2eGRIe_yhSVroliFb0uCffOcREN32IgCjMKM2HMJtgM.woff
220 ms
Zh5r25ARMZ8rfY1Piu1rM0PozEbdFcGLyXSqcZf6Yj6ffOAREN32IgCjMKM2HMJtM3.woff
222 ms
sZqw0BeOokIUXxHaXeJCmT6us5b-fw1GREgUAYifXAqffO0REN32IgCjMKM2HMJtg6.woff
328 ms
iFtCRXuGomJGndf054Mx1oyo2-w8vbrtQykkKmKtBuwffOeREN32IgCjMKM2HMJtg3.woff
330 ms
i18q8D9ZxSOcj8oY8iVPjZBBU2+kGIIypokuqTI+cx3qXMq7Z6PQIsx1DYGrQxtLul50YV50rVcCiNJc0enX4qdkNRYe8j2g46+SIMHapXJw1GFdIWH2DfalQknZeTDWsRW2bqlBK3ORIz9AqJUapQAAAA=
145 ms
gz8NC9rTm7F2GDGdOWcKmGclTGR_7PvPEtn-gtgQad6ffVAREN32IgCjMKM2HMJtM3.woff
368 ms
WF2bzfs1Vd0NRwH6XlCrZywnIf1x3oGqE1J08urop46ffVcREN32IgCjMKM2HMJtgM.woff
368 ms
feeds
88 ms
recent-blogs
192 ms
26 ms
linkid.js
24 ms
www-widgetapi.js
167 ms
insight.min.js
100 ms
bat.js
161 ms
5fc7b3c17686e7f3fa30c3b39b8416bf
55 ms
299275_feat_img.jpg
142 ms
127 ms
c8995ddc7154570ecacaa06dae3431bc
73 ms
ntpagetag.jpg
315 ms
collect
25 ms
collect
68 ms
p.gif
180 ms
collect
89 ms
ga-audiences
41 ms
ga-audiences
39 ms
15 ms
13 ms
putnam.com 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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
putnam.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
Page has valid source maps
putnam.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Putnam.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 Putnam.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.
putnam.com
Open Graph data is detected on the main page of Putnam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: