4.7 sec in total
185 ms
4.3 sec
209 ms
Welcome to docguide.com homepage info - get ready to check Doc Guide best content for United States right away, or after learning these important things about docguide.com
Visit docguide.comWe analyzed Docguide.com page load time and found that the first response time was 185 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
docguide.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value10.5 s
0/100
25%
Value7.9 s
23/100
10%
Value1,240 ms
19/100
30%
Value0.034
100/100
15%
Value10.3 s
25/100
10%
185 ms
605 ms
263 ms
178 ms
362 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 57% of them (27 requests) were addressed to the original Docguide.com, 28% (13 requests) were made to Wgt.opencme.org and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (649 ms) relates to the external source Wgt.opencme.org.
Page size can be reduced by 850.7 kB (79%)
1.1 MB
232.8 kB
In fact, the total size of Docguide.com main page is 1.1 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. 20% of websites need less resources to load. Javascripts take 518.4 kB which makes up the majority of the site volume.
Potential reduce by 57.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. 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 57.3 kB or 85% of the original size.
Potential reduce by 4.4 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, Doc Guide needs image optimization as it can save up to 4.4 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 374.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 374.2 kB or 72% of the original size.
Potential reduce by 414.8 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. Docguide.com needs all CSS files to be minified and compressed as it can save up to 414.8 kB or 87% of the original size.
Number of requests can be reduced by 30 (67%)
45
15
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doc Guide. 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 from 4 to 1 for CSS and as a result speed up the page load time.
docguide.com
185 ms
30days
605 ms
d459a49991db8d920b88022c0cad8b06.css
263 ms
print.css
178 ms
b70a87ecf4e026458e958f65afeb6835.js
362 ms
wz_tooltip.js
185 ms
tip_balloon.js
176 ms
logo.gif
180 ms
menu_arrow.gif
349 ms
menu_arrow_out.gif
348 ms
sponsored.gif
359 ms
menu-leaf.png
91 ms
OpenCME_Reg_23px.gif
169 ms
hor-line.gif
263 ms
start_box_bg.png
236 ms
ga.js
30 ms
stemb.gif
140 ms
stemt.gif
141 ms
l.gif
174 ms
lb.gif
217 ms
b.gif
306 ms
rb.gif
308 ms
r.gif
314 ms
rt.gif
323 ms
t.gif
350 ms
lt.gif
388 ms
background.gif
483 ms
hintbox.gif
482 ms
__utm.gif
11 ms
viewid=7842172
88 ms
viewid=7842172
79 ms
DG_iOS_app_365x455.gif
191 ms
ocme_logo.png
184 ms
wgt_activities
649 ms
css_ebefd82980015b9bd641b0601b2ccad6.css
435 ms
ocme_ga.js
180 ms
ga.js
360 ms
js_5033242f143e500fbb9375e189d215c8.js
638 ms
feedback-button.gif
90 ms
geg_widget.png
175 ms
cleveland%20clinic.png
176 ms
UniversityOFlorida.png
178 ms
penn_48px.png
179 ms
__utm.gif
11 ms
toolbar.png
252 ms
ajax-loader.gif
340 ms
css_f08f67acdb3f6fcdab38f690a1e46f1d.css
177 ms
docguide.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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
docguide.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
docguide.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docguide.com 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 Docguide.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.
docguide.com
Open Graph description is not detected on the main page of Doc Guide. 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: