2.1 sec in total
112 ms
1.6 sec
433 ms
Click here to check amazing Understand content for United States. Otherwise, check out these important facts you probably never knew about understand.com
Discover the most comprehensive medical animations, illustrations, and interactive media available today
Visit understand.comWe analyzed Understand.com page load time and found that the first response time was 112 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
understand.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value9.8 s
0/100
25%
Value5.7 s
50/100
10%
Value2,000 ms
8/100
30%
Value0.028
100/100
15%
Value10.8 s
22/100
10%
112 ms
422 ms
53 ms
80 ms
86 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 97% of them (152 requests) were addressed to the original Understand.com, 1% (2 requests) were made to Ssl.google-analytics.com and 1% (2 requests) were made to Images.boldchat.com. The less responsive or slowest element that took the longest time to load (422 ms) belongs to the original domain Understand.com.
Page size can be reduced by 353.5 kB (18%)
2.0 MB
1.6 MB
In fact, the total size of Understand.com main page is 2.0 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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 44.4 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 20.5 kB, which is 40% 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 44.4 kB or 88% of the original size.
Potential reduce by 13.7 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. Understand images are well optimized though.
Potential reduce by 255.1 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 255.1 kB or 68% of the original size.
Potential reduce by 40.3 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. Understand.com needs all CSS files to be minified and compressed as it can save up to 40.3 kB or 85% of the original size.
Number of requests can be reduced by 22 (29%)
76
54
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Understand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
understand.com
112 ms
www.understand.com
422 ms
jquery-1.7.2.min.js
53 ms
jquery-ui-1.8.18.min.js
80 ms
shadowbox.js
86 ms
shadowbox.css
91 ms
Master.css
89 ms
Home.css
87 ms
Master.js
91 ms
Form-WP.js
106 ms
Home.js
112 ms
jquery-1.7.2.min.js
144 ms
jquery-ui-1.8.18.min.js
141 ms
shadowbox.js
75 ms
home.css
59 ms
master.css
59 ms
shadowbox.css
52 ms
master.js
88 ms
form-wp.js
74 ms
home.js
69 ms
Background.png
90 ms
ga.js
112 ms
Understand-Logo.png
86 ms
Tab_End-R.png
87 ms
Tab_Mid.png
89 ms
Tab.png
89 ms
Tab_End-L.png
90 ms
Button_Fb.png
98 ms
Button_RSS.png
97 ms
Nav_Background.png
78 ms
Nav.png
77 ms
Nav_Thumb_Plastic.png
77 ms
Nav_Thumb_Breast-Cancer.png
77 ms
Nav_Thumb_Knee.png
116 ms
Nav_Thumb_Spine.png
121 ms
Nav_Thumb_Derm.png
116 ms
Nav_Thumb_Hair.png
120 ms
Nav_Thumb_Knee-2.png
120 ms
Nav_Thumb_Shoulder.png
120 ms
Nav_Thumb_Hip.png
127 ms
Nav_Thumb_DD-Urology.png
128 ms
Nav_Thumb_DD-Male.png
134 ms
Hero-Home_Plastic.jpg
134 ms
Hero-Home_Breast.jpg
133 ms
Hero-Home_Ortho.jpg
133 ms
Hero-Home_Custom-Animation.jpg
152 ms
Hero-Home_Deep-Dives.jpg
153 ms
Icon_Skinny-Arrow-Prev.png
155 ms
Icon_Skinny-Arrow-Next.png
160 ms
WP-Thumb-1.jpg
159 ms
WP-Thumb-2.jpg
158 ms
WP-Thumb-3.jpg
178 ms
Arrow-Down-Skinny.png
179 ms
WP-Cover.jpg
184 ms
Component_Fancy-List_Mid.png
183 ms
Thumb_Breasts.png
183 ms
Thumb_Breast-Cancer.png
183 ms
background.png
160 ms
understand-logo.png
162 ms
tab_end-r.png
149 ms
tab_mid.png
151 ms
tab.png
149 ms
tab_end-l.png
147 ms
nav_background.png
172 ms
nav_thumb_plastic.png
181 ms
nav.png
171 ms
nav_thumb_breast-cancer.png
171 ms
button_rss.png
177 ms
button_fb.png
179 ms
__utm.gif
27 ms
nav_thumb_knee.png
158 ms
nav_thumb_derm.png
163 ms
nav_thumb_hair.png
156 ms
nav_thumb_shoulder.png
162 ms
nav_thumb_knee-2.png
163 ms
nav_thumb_spine.png
163 ms
nav_thumb_hip.png
174 ms
nav_thumb_dd-urology.png
174 ms
hero-home_ortho.jpg
268 ms
nav_thumb_dd-male.png
196 ms
hero-home_plastic.jpg
296 ms
hero-home_breast.jpg
309 ms
hero-home_custom-animation.jpg
263 ms
hero-home_deep-dives.jpg
262 ms
icon_skinny-arrow-prev.png
202 ms
wp-thumb-2.jpg
238 ms
wp-thumb-1.jpg
265 ms
icon_skinny-arrow-next.png
266 ms
wp-thumb-3.jpg
266 ms
arrow-down-skinny.png
263 ms
component_fancy-list_mid.png
271 ms
thumb_breast-cancer.png
280 ms
thumb_breasts.png
279 ms
wp-cover.jpg
282 ms
myriadwebpro_0-webfont.woff
262 ms
myriadwebpro-bold_0-webfont.woff
264 ms
segoepr_0-webfont.woff
270 ms
Thumb_Knee.png
280 ms
Thumb_Spine.png
276 ms
Thumb_Filler.png
274 ms
clear.gif
203 ms
clear.gif
211 ms
Thumb_SkinX.png
264 ms
Content_Home_iPad_UTK.jpg
261 ms
Home_DD-Thumb_Knee.png
269 ms
Home_DD-Thumb_Shoulder.png
271 ms
Home_DD-Thumb_Hip.png
273 ms
Home_DD-Thumb_Urology.png
273 ms
Home_DD-Thumb_Male.png
260 ms
Background_Factoid.png
262 ms
Icon_Brain.png
262 ms
Content_Home_Cust-Anim_Medical-Device.jpg
271 ms
Content_Home_Cust-Anim_MOA.jpg
270 ms
Content_Home_Cust-Anim_Surgical-Procedure.jpg
271 ms
Button_Generic_Left.png
258 ms
Button_Generic_Mid.png
259 ms
Button_Generic_Right.png
241 ms
Background_Footer.png
220 ms
Icon_Envelope.png
183 ms
Icon_Fb.png
185 ms
Cred_Logo_BPtW.jpg
172 ms
Cred_Logo_Inc-5000.jpg
171 ms
TextBox_Search.png
168 ms
Button_Search.png
179 ms
Component_Fancy-List_Top.png
178 ms
Component_Fancy-List_Btm.png
168 ms
myriadwebpro_0-webfont.woff
157 ms
myriadwebpro-bold_0-webfont.woff
154 ms
segoepr_0-webfont.woff
142 ms
thumb_knee.png
158 ms
thumb_spine.png
157 ms
thumb_filler.png
155 ms
content_home_ipad_utk.jpg
174 ms
thumb_skinx.png
153 ms
home_dd-thumb_knee.png
148 ms
home_dd-thumb_shoulder.png
155 ms
home_dd-thumb_hip.png
143 ms
home_dd-thumb_urology.png
150 ms
home_dd-thumb_male.png
158 ms
background_factoid.png
155 ms
icon_brain.png
156 ms
content_home_cust-anim_medical-device.jpg
166 ms
content_home_cust-anim_moa.jpg
164 ms
content_home_cust-anim_surgical-procedure.jpg
156 ms
button_generic_left.png
158 ms
button_generic_mid.png
157 ms
button_generic_right.png
157 ms
icon_envelope.png
161 ms
background_footer.png
167 ms
icon_fb.png
163 ms
cred_logo_bptw.jpg
160 ms
cred_logo_inc-5000.jpg
159 ms
textbox_search.png
160 ms
component_fancy-list_top.png
166 ms
button_search.png
167 ms
component_fancy-list_btm.png
165 ms
understand.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
understand.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
understand.com SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Understand.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Understand.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.
understand.com
Open Graph description is not detected on the main page of Understand. 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: