1.8 sec in total
289 ms
1.4 sec
121 ms
Visit graham-center.org now to see the best up-to-date Graham Center content and also check out these interesting facts you probably never knew about graham-center.org
The Robert Graham Center improves individual and population health by enhancing the delivery of primary care.
Visit graham-center.orgWe analyzed Graham-center.org page load time and found that the first response time was 289 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
graham-center.org performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value5.9 s
14/100
25%
Value8.4 s
18/100
10%
Value1,370 ms
16/100
30%
Value0.055
98/100
15%
Value15.8 s
6/100
10%
289 ms
321 ms
79 ms
72 ms
19 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 47% of them (14 requests) were addressed to the original Graham-center.org, 37% (11 requests) were made to Ui.aafp.net and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (321 ms) belongs to the original domain Graham-center.org.
Page size can be reduced by 98.5 kB (48%)
204.3 kB
105.8 kB
In fact, the total size of Graham-center.org main page is 204.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. CSS take 93.7 kB which makes up the majority of the site volume.
Potential reduce by 22.6 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 3.2 kB, which is 11% 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 22.6 kB or 81% of the original size.
Potential reduce by 33.2 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 33.2 kB or 40% of the original size.
Potential reduce by 42.6 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. Graham-center.org needs all CSS files to be minified and compressed as it can save up to 42.6 kB or 46% of the original size.
Number of requests can be reduced by 7 (35%)
20
13
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Graham Center. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
graham-center.org
289 ms
www.graham-center.org
321 ms
home.html
79 ms
gtm.js
72 ms
jquery-1.8.3.min.js
19 ms
AAFPUser.js
124 ms
utils.js
93 ms
clientlib-base.min.css
91 ms
responsive-grid.min.css
149 ms
aafp-web-components.esm.js
119 ms
aafp-web-components.js
120 ms
style.css
125 ms
embed-lite.min.js
90 ms
clientlib-base.min.js
213 ms
spinner-logo.svg
19 ms
icon21-access.svg
111 ms
icon21-behavior.svg
112 ms
icon21-geography.svg
113 ms
icon21-education.svg
147 ms
icon21-quality.svg
175 ms
icon21-cost.svg
177 ms
icon21-community.svg
212 ms
icon21-workforce.svg
213 ms
Roboto-Light.woff
63 ms
Roboto-Thin.woff
73 ms
Roboto-Regular.woff
65 ms
Roboto-Medium.woff
65 ms
Roboto-Bold.woff
196 ms
Roboto-Black.woff
77 ms
TimesNewRomanPS-BoldMT.woff
127 ms
graham-center.org 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-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
graham-center.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
graham-center.org SEO score
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 Graham-center.org 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 Graham-center.org 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.
graham-center.org
Open Graph data is detected on the main page of Graham Center. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: