5.4 sec in total
1.2 sec
4 sec
258 ms
Click here to check amazing Docgiff content. Otherwise, check out these important facts you probably never knew about docgiff.com
Dr. Ken Walker (who writes under the pseudonym of Dr. W. Gifford-Jones, MD) is a graduate of the University of Toronto and the Harvard Medical School
Visit docgiff.comWe analyzed Docgiff.com page load time and found that the first response time was 1.2 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
docgiff.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value12.2 s
0/100
25%
Value10.1 s
9/100
10%
Value350 ms
73/100
30%
Value0.011
100/100
15%
Value12.0 s
16/100
10%
1210 ms
115 ms
144 ms
172 ms
158 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 69% of them (54 requests) were addressed to the original Docgiff.com, 10% (8 requests) were made to Apis.google.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Docgiff.com.
Page size can be reduced by 351.0 kB (39%)
896.9 kB
545.8 kB
In fact, the total size of Docgiff.com main page is 896.9 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. 55% of websites need less resources to load. Images take 424.2 kB which makes up the majority of the site volume.
Potential reduce by 36.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 36.3 kB or 73% of the original size.
Potential reduce by 22.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. Docgiff 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 37.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. Docgiff.com needs all CSS files to be minified and compressed as it can save up to 37.3 kB or 79% of the original size.
Number of requests can be reduced by 51 (67%)
76
25
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docgiff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.docgiff.com
1210 ms
wp-emoji-release.min.js
115 ms
theme-my-login.css
144 ms
pagenavi-css.css
172 ms
upw-theme-standard.min.css
158 ms
shortcodes.css
159 ms
jquery.fancybox-1.3.7.min.css
150 ms
style_2.1.2.css
188 ms
button.facebook.js
211 ms
style.css
223 ms
functions.js
358 ms
shadowbox.css
228 ms
shadowbox.js
238 ms
flexslider.css
253 ms
public.css
282 ms
public.css
294 ms
comment-reply.min.js
300 ms
all.js
164 ms
button.googleplus.js
301 ms
widgets.js
40 ms
wp-embed.min.js
330 ms
jquery.js
498 ms
jquery-migrate.min.js
405 ms
jquery.flexslider-min.js
485 ms
jquery.fancybox-1.3.7.min.js
404 ms
jquery.easing.pack.js
482 ms
jquery.mousewheel.min.js
483 ms
mqdefault.jpg
121 ms
giff_bg_image.jpg
348 ms
page_wrapper_bg.png
122 ms
header_wrapper_bg.png
424 ms
navigation_wrapper_bg.png
337 ms
main_nav_home_bg.png
342 ms
main_nav_item_bg.png
339 ms
main_nav_stories_bg.png
339 ms
content_wrapper_bg.png
338 ms
display_bar_wrapper_bg.jpg
455 ms
DocGiffBanner3_MedTipSIGNUP.jpg
597 ms
DocGiffBanner5_OnTour.jpg
687 ms
facebook_logo.png
443 ms
text_image_small.png
442 ms
text_image_med.png
506 ms
text_image_large.png
505 ms
printer.png
504 ms
90-W-Gifford-Jones-MD-Book-Mock-Up.jpg
505 ms
SJB_VitC_16yearimagesV2_small.jpg
590 ms
P1020021-150x150.jpg
679 ms
P1020020-150x150.jpg
703 ms
box_small_border.gif
560 ms
box_small_bottom_border.gif
661 ms
box_small_top_border.gif
660 ms
box_border.gif
653 ms
box_bottom_border.gif
718 ms
box_top_border.gif
734 ms
form_field_bg.gif
1392 ms
plusone.js
252 ms
287 ms
ga.js
205 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
54 ms
xd_arbiter.php
130 ms
xd_arbiter.php
186 ms
bg_direction_nav.png
417 ms
cb=gapi.loaded_0
30 ms
cb=gapi.loaded_1
54 ms
fastbutton
140 ms
__utm.gif
46 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
39 ms
share_button.php
87 ms
postmessageRelay
89 ms
qeKvIRsJabD.js
145 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
27 ms
LVx-xkvaJ0b.png
193 ms
3193398744-postmessagerelay.js
20 ms
rpc:shindig_random.js
32 ms
cb=gapi.loaded_0
3 ms
jot
142 ms
print.css
78 ms
docgiff.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 input fields do not have accessible names
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
Links do not have a discernible name
docgiff.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
docgiff.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docgiff.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 Docgiff.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.
docgiff.com
Open Graph description is not detected on the main page of Docgiff. 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: