1.9 sec in total
139 ms
1.5 sec
273 ms
Visit rehabmaps.upmc.com now to see the best up-to-date Rehabmaps Upmc content for United States and also check out these interesting facts you probably never knew about rehabmaps.upmc.com
UPMC Centers for Rehab Services Locations 2011
Visit rehabmaps.upmc.comWe analyzed Rehabmaps.upmc.com page load time and found that the first response time was 139 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
rehabmaps.upmc.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value12.6 s
0/100
25%
Value6.8 s
35/100
10%
Value1,180 ms
21/100
30%
Value0
100/100
15%
Value12.4 s
15/100
10%
139 ms
63 ms
66 ms
189 ms
104 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 18% of them (12 requests) were addressed to the original Rehabmaps.upmc.com, 47% (32 requests) were made to Maps.googleapis.com and 15% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (474 ms) relates to the external source Maps.googleapis.com.
Page size can be reduced by 743.0 kB (52%)
1.4 MB
697.1 kB
In fact, the total size of Rehabmaps.upmc.com main page is 1.4 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 926.9 kB which makes up the majority of the site volume.
Potential reduce by 77.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. 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 77.7 kB or 79% of the original size.
Potential reduce by 17.0 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. Rehabmaps Upmc images are well optimized though.
Potential reduce by 643.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 643.7 kB or 69% of the original size.
Potential reduce by 4.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. Rehabmaps.upmc.com needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 69% of the original size.
Number of requests can be reduced by 26 (43%)
60
34
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rehabmaps Upmc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
rehabmaps.upmc.com
139 ms
font.css
63 ms
googleMap.css
66 ms
modernizr-1.6.min.js
189 ms
js
104 ms
jquery.min.js
35 ms
plugins.js
222 ms
script.js
55 ms
bgGrey.jpg
48 ms
gtm.js
85 ms
header.jpg
83 ms
gotham-black-webfont.woff
67 ms
common.js
46 ms
util.js
241 ms
geocoder.js
239 ms
locations.xml
41 ms
gtm.js
203 ms
gotham-black-webfont.ttf
332 ms
map.js
141 ms
geometry.js
273 ms
directions.js
272 ms
marker.js
241 ms
infowindow.js
174 ms
StaticMapService.GetMapImage
474 ms
gtm.js
217 ms
onion.js
60 ms
openhand_8_8.cur
156 ms
ViewportInfoService.GetViewportInfo
129 ms
stats.js
18 ms
controls.js
115 ms
handheld.css
110 ms
css
266 ms
spotlight-poi.png
180 ms
analytics.js
136 ms
dc.js
150 ms
transparent.png
88 ms
vt
94 ms
vt
95 ms
vt
96 ms
vt
90 ms
vt
97 ms
vt
92 ms
vt
98 ms
vt
99 ms
vt
95 ms
vt
128 ms
vt
145 ms
vt
143 ms
vt
144 ms
vt
143 ms
vt
143 ms
vt
149 ms
google4.png
138 ms
mapcnt6.png
152 ms
sv5.png
153 ms
vt
120 ms
linkid.js
79 ms
inpage_linkid.js
77 ms
appmeasurement.js
314 ms
tmapctrl.png
73 ms
cb_scout5.png
111 ms
tmapctrl4.png
103 ms
imgs8.png
103 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
114 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
137 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
183 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
193 ms
AuthenticationService.Authenticate
15 ms
rehabmaps.upmc.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
button, link, and menuitem elements do not have accessible names.
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
Document doesn't have a <title> element
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
rehabmaps.upmc.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
rehabmaps.upmc.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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 Rehabmaps.upmc.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 Rehabmaps.upmc.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.
rehabmaps.upmc.com
Open Graph description is not detected on the main page of Rehabmaps Upmc. 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: