2.8 sec in total
133 ms
2.3 sec
346 ms
Click here to check amazing Medex content. Otherwise, check out these important facts you probably never knew about medex.com
The ClearGuard™ HD antimicrobial barrier cap is the first and only device available for sale in the US that kills infection causing bacteria inside a hemodialysis catheter hub.
Visit medex.comWe analyzed Medex.com page load time and found that the first response time was 133 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
medex.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value6.5 s
9/100
25%
Value8.1 s
21/100
10%
Value440 ms
64/100
30%
Value0
100/100
15%
Value8.6 s
37/100
10%
133 ms
884 ms
78 ms
79 ms
122 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Medex.com, 75% (62 requests) were made to Smiths-medical.com and 5% (4 requests) were made to A.collective-media.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Smiths-medical.com.
Page size can be reduced by 1.7 MB (65%)
2.6 MB
919.0 kB
In fact, the total size of Medex.com main page is 2.6 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.5 MB which makes up the majority of the site volume.
Potential reduce by 172.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 25.9 kB, which is 12% 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 172.6 kB or 79% of the original size.
Potential reduce by 94.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. Obviously, Medex needs image optimization as it can save up to 94.6 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 74% of the original size.
Potential reduce by 269.2 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. Medex.com needs all CSS files to be minified and compressed as it can save up to 269.2 kB or 87% of the original size.
Number of requests can be reduced by 44 (60%)
73
29
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Medex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
medex.com
133 ms
medex
884 ms
fonts.min.css
78 ms
normalize.min.css
79 ms
styles.min.css
122 ms
jquery.safari-checkbox.css
80 ms
jquery.selectbox.css
85 ms
jquery.jcarousel.connected-carousels.css
83 ms
jquery.ui.css
114 ms
jquery.colorbox.css
118 ms
jquery.bxslider.css
118 ms
jquery-1.10.2.min.js
151 ms
jquery-migrate-1.2.1.min.js
135 ms
jquery.colorbox.js
168 ms
css
42 ms
css
74 ms
jquery.prettyPhoto.js
168 ms
prettyPhoto.css
169 ms
WebResource.axd
176 ms
ScriptResource.axd
200 ms
ScriptResource.axd
198 ms
brand
39 ms
show_afs_search.js
44 ms
jscript.js
166 ms
jquery.hoverIntent-1.8.0.min.js
167 ms
jquery.checkbox.min.js
167 ms
jquery.carouFredSel-5.2.3-packed.js
168 ms
jquery.jcarousel.js
251 ms
placeholders.min.js
254 ms
jquery.jcarousel.connected-carousels.js
256 ms
jquery-ui.js
338 ms
jquery.bxslider.js
257 ms
jquery.selectbox-0.2.min.js
256 ms
ss.js
258 ms
jscriptend.js
259 ms
addthis_widget.js
16 ms
brand
25 ms
analytics.js
13 ms
logo.png
123 ms
FINAL_Shortened_1000_ML_46239.png
1114 ms
FS113.jpg
646 ms
MX92133L.jpg
157 ms
MicroBore_ExtensionSets.png
156 ms
MicroBoreT-Connectors.png
159 ms
SmallBoreExtensionSets.png
184 ms
UltraSmBoreExtSet_MX448HFpng.png
705 ms
20dropGravitySet_SM5009.png
189 ms
SM872M.jpg
460 ms
ajax-loader.gif
461 ms
Smiths_NewFooter.jpg
469 ms
arrow-up.png
463 ms
collect
86 ms
search-icon.png
398 ms
icon-add-to-inquiry.png
398 ms
icon-add-to-brochure.png
398 ms
0-2-2-0-097-097-097-030.png
399 ms
icon-print.png
400 ms
icon-share.png
401 ms
Smiths_Hero_Desktop_BRANDS_Medex.jpg
432 ms
hero-shadow.png
403 ms
small-arrows2.png
403 ms
arrow-first-disabled.png
416 ms
arrow-prev-disabled.png
431 ms
arrow-next-active.png
465 ms
arrow-last-active.png
563 ms
DINWeb-Medium.woff
512 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
5 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
12 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
13 ms
DINWebPro-Bold.woff
519 ms
DINWeb.woff
520 ms
300lo.json
43 ms
overlay.png
183 ms
empty.png
185 ms
checkbox.png
185 ms
sh.8e5f85691f9aaa082472a194.html
51 ms
layers.e5ea973510bf60b3db41.js
33 ms
datapair
44 ms
datapair
31 ms
datapair
33 ms
datapair
34 ms
pixel
17 ms
pixel
14 ms
medex.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
Form elements do not have associated labels
medex.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
medex.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 valid hreflang
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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Medex.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 Medex.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.
medex.com
Open Graph description is not detected on the main page of Medex. 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: