1 sec in total
38 ms
701 ms
286 ms
Welcome to altum.com homepage info - get ready to check Altum best content for United States right away, or after learning these important things about altum.com
Grants management software for research funding. Manage applications, peer review, and award. Measure impact and communicate outcomes.
Visit altum.comWe analyzed Altum.com page load time and found that the first response time was 38 ms and then it took 987 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
altum.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value5.0 s
28/100
25%
Value5.7 s
52/100
10%
Value930 ms
30/100
30%
Value0.034
100/100
15%
Value14.4 s
9/100
10%
38 ms
153 ms
79 ms
31 ms
39 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 90% of them (66 requests) were addressed to the original Altum.com, 3% (2 requests) were made to Ssl.google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (280 ms) relates to the external source Assets.zendesk.com.
Page size can be reduced by 1.2 MB (54%)
2.2 MB
1.0 MB
In fact, the total size of Altum.com main page is 2.2 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 21.7 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 5.0 kB, which is 18% 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 21.7 kB or 79% of the original size.
Potential reduce by 21.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. Altum images are well optimized though.
Potential reduce by 811.0 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 811.0 kB or 73% of the original size.
Potential reduce by 350.8 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. Altum.com needs all CSS files to be minified and compressed as it can save up to 350.8 kB or 85% of the original size.
Number of requests can be reduced by 48 (72%)
67
19
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Altum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
altum.com
38 ms
www.altum.com
153 ms
css
79 ms
styles.css
31 ms
normalize.css
39 ms
style.css
37 ms
bootstrap.min.css
63 ms
cs-select.css
33 ms
cs-skin-underline.css
40 ms
common.css
46 ms
home.css
44 ms
about.css
42 ms
community.css
39 ms
clients-partners.css
40 ms
case-study.css
43 ms
careers.css
43 ms
leadership.css
44 ms
job.css
45 ms
communications.css
46 ms
strategic-communications.css
47 ms
community-outreach.css
46 ms
international-collaborations.css
48 ms
performance-management.css
49 ms
performance-pages.css
50 ms
landing-page.css
54 ms
grants-management.css
56 ms
easy-grants.css
55 ms
proposalcentral.css
55 ms
philantrack.css
56 ms
philantrack-grantseekers.css
62 ms
business-discovery.css
56 ms
budgeting.css
58 ms
portfolio-analysis.css
62 ms
blog.css
60 ms
pt_blog.css
59 ms
newsroom.css
62 ms
product-selector.css
106 ms
hubspot.css
63 ms
conditionizr-4.3.0.min.js
43 ms
jquery.js
90 ms
jquery-migrate.min.js
80 ms
bootstrap.min.js
81 ms
modernizr-2.7.1.min.js
77 ms
jquery.magicmenu.js
77 ms
scripts.js
75 ms
jquery.form.min.js
75 ms
scripts.js
74 ms
wp-embed.min.js
73 ms
wp-emoji-release.min.js
74 ms
main.js
280 ms
38561.js
275 ms
ga.js
122 ms
bg.jpg
119 ms
submenu-arrow.png
8 ms
slider-bkg1.jpg
37 ms
slider-bkg2.jpg
36 ms
slider-bkg3.jpg
60 ms
monitor_about.png
120 ms
product-bg3.jpg
275 ms
product-img3.png
53 ms
product-check3.png
56 ms
product-bg2.jpg
60 ms
product-img2.png
61 ms
product-check2.png
62 ms
product-advisor-bg.png
65 ms
Alzheimers-e1431707613498.png
118 ms
NIMH-e1431707767673.png
118 ms
contact-bkg.jpg
72 ms
logo.svg
115 ms
IQHow_FEYlDC4Gzy_m8fcsBaWKZ57bY3RXgXH6dOjZ0.ttf
116 ms
zhcz-_WihjSQC0oHJ9TCYMDdSZkkecOE1hvV7ZHvhyU.ttf
120 ms
glyphicons-halflings-regular.woff
150 ms
__utm.gif
122 ms
altum.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.
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
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.
altum.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
altum.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
Page is blocked from indexing
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 Altum.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 Altum.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.
altum.com
Open Graph data is detected on the main page of Altum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: