35.3 sec in total
359 ms
30.7 sec
4.3 sec
Visit permanente.net now to see the best up-to-date Permanente content for United States and also check out these interesting facts you probably never knew about permanente.net
My Doctor Online Homepage
Visit permanente.netWe analyzed Permanente.net page load time and found that the first response time was 359 ms and then it took 35 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.
permanente.net performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value11.0 s
0/100
25%
Value11.9 s
4/100
10%
Value14,170 ms
0/100
30%
Value0.968
2/100
15%
Value19.4 s
2/100
10%
359 ms
293 ms
383 ms
364 ms
810 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Permanente.net, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (7.6 sec) relates to the external source Zn8dnzxtfkqprztxv-tpmg.siteintercept.qualtrics.com.
Page size can be reduced by 276.3 kB (36%)
774.4 kB
498.1 kB
In fact, the total size of Permanente.net main page is 774.4 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. 60% of websites need less resources to load. Images take 408.9 kB which makes up the majority of the site volume.
Potential reduce by 23.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. This page needs HTML code to be minified as it can gain 5.1 kB, which is 17% 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 23.3 kB or 79% of the original size.
Potential reduce by 27.6 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. Permanente images are well optimized though.
Potential reduce by 188.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 188.0 kB or 64% of the original size.
Potential reduce by 37.4 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. Permanente.net needs all CSS files to be minified and compressed as it can save up to 37.4 kB or 85% of the original size.
Number of requests can be reduced by 57 (66%)
87
30
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Permanente. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and as a result speed up the page load time.
359 ms
normalize.min.css
293 ms
style.css
383 ms
css
364 ms
jquery.min.js
810 ms
angular.js
1093 ms
angular-cookies.js
1888 ms
angular-route.min.js
725 ms
angular-animate.min.js
1844 ms
mdoHome.js
2019 ms
mdoHomeShared.js
1836 ms
mainContentService.js
1836 ms
mdoHomeController.js
1839 ms
mdoHomePageController.js
1884 ms
stringToHtml.js
1936 ms
search-input-box.js
2063 ms
mdo-shell-shared.js
1936 ms
filters.js
1937 ms
mdoShellContainer.js
1976 ms
personalbar.js
1979 ms
fadeToggle.js
2080 ms
setOpacity.js
2020 ms
toggleMenu.js
2019 ms
proxyMemberServices.js
2070 ms
proxyIndex.js
2072 ms
userStateModelService.js
2072 ms
mdo-shell-desktop.js
2072 ms
global-search.js
2254 ms
masthead.js
2354 ms
mainnav.js
2355 ms
stay-connected.js
2355 ms
leftnav.js
2323 ms
print.js
2359 ms
footer.js
2375 ms
scrollup.js
2376 ms
sso.js
2377 ms
checkLogin.js
2592 ms
dev.js
2558 ms
loginDetails.js
2527 ms
mrnByTokenId.js
2470 ms
proxyList.js
2090 ms
proxyListByGuid.js
1728 ms
proxy.js
974 ms
response.js
1073 ms
timeout.js
1076 ms
userService.js
1072 ms
memberDetails.js
1028 ms
ssoTimeoutConstants.js
1028 ms
ssoTimeoutCookieService.js
977 ms
ssoTimeoutModalDirective.js
1212 ms
ssoTimeoutService.js
1194 ms
mdo-shell.html
334 ms
main.html
251 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
2875 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
4025 ms
gtm.js
4950 ms
ssoTimeoutModal.html
1691 ms
masthead.html
543 ms
leftnav.html
3324 ms
mainnav.html
5660 ms
personalbar.html
4221 ms
footer.html
3777 ms
search-input-box.html
1812 ms
content
2055 ms
3077 ms
mdo-ui@2x.png
3252 ms
check-login
2635 ms
ssoTimeoutModalIcon.jpg
2207 ms
globalSearchPlaceholderInfo
1999 ms
chevron.png
3675 ms
mag-glass-gray-d.png
5157 ms
About%20TPMG_tcm75-1226940.png
5616 ms
DoctorsHomepage_tcm75-1226939.jpg
5587 ms
ChooseADoctorPromo_tcm75-1226938.jpg
5402 ms
SearchHealthInfo_tcm75-1226935.jpg
5586 ms
BannerMDOFinal_tcm75-1226945.png
4769 ms
stay-connected.html
4029 ms
sm-TPMG-banner-logo.png
4462 ms
login-details
7125 ms
ajax-loader-blue2x.gif
2550 ms
icon_caret@1x.png
2515 ms
icon_info@1x.png
2549 ms
twitter@1x.png
2538 ms
sm-icon-print.png
2317 ms
links-mapping
4357 ms
7632 ms
ga.js
7454 ms
analytics.js
7454 ms
__utm.gif
1381 ms
collect
173 ms
collect
464 ms
permanente.net accessibility score
permanente.net 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
permanente.net SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Permanente.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Permanente.net 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.
permanente.net
Open Graph description is not detected on the main page of Permanente. 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: