2.4 sec in total
126 ms
2.1 sec
197 ms
Click here to check amazing Johnhakimmd content. Otherwise, check out these important facts you probably never knew about johnhakimmd.com
Read patient reviews and find a Prince Frederick Cardiologist at Practice JOHN HAKIM, MD AND ASSOCIATES and book an appointment instantly. See a list of insurances accepted by JOHN HAKIM, MD AND ASSOC...
Visit johnhakimmd.comWe analyzed Johnhakimmd.com page load time and found that the first response time was 126 ms and then it took 2.3 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.
johnhakimmd.com performance score
126 ms
3 ms
149 ms
4 ms
132 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Johnhakimmd.com, 17% (17 requests) were made to Maps.googleapis.com and 10% (10 requests) were made to D2cwdzolmutht6.cloudfront.net. The less responsive or slowest element that took the longest time to load (592 ms) relates to the external source D23tkj0nqpfswj.cloudfront.net.
Page size can be reduced by 1.3 MB (64%)
2.0 MB
715.3 kB
In fact, the total size of Johnhakimmd.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 527 B
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 527 B or 47% of the original size.
Potential reduce by 29.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, Johnhakimmd needs image optimization as it can save up to 29.4 kB or 12% 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.0 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.0 MB or 68% of the original size.
Potential reduce by 208.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. Johnhakimmd.com needs all CSS files to be minified and compressed as it can save up to 208.6 kB or 87% of the original size.
Number of requests can be reduced by 53 (67%)
79
26
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Johnhakimmd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
johnhakimmd.com
126 ms
global.css
3 ms
john-hakim-md-and-associates-26463
149 ms
powered_by.png
4 ms
john-hakim-md-and-associates-26463
132 ms
sg.patient-beta.framework__f5cf27c75a82a6020a62ba4a45789209__.min.css
127 ms
sg.patient-beta__6c8439325f75fd625ab422602ee31f38__.min.css
142 ms
component-sdk__944abec663ebaeea608828646eac9db6__.min.css
137 ms
rb.shared.desktop__636e15d15995feb4811fb44d87527256__.min.css
132 ms
rb.practice.desktop__f9836a49f737771eb08251bc18507a10__.min.css
139 ms
error-logger__e455ee6696ad8de42c87042b57b48539__.min.js
135 ms
sg.patient-beta.framework__ac77f1e7831dcfbeaad294aad6da3e61__.min.js
170 ms
sg.patient-beta__d64afabf6e587a4f06fcffcfd09d4ca6__.min.js
150 ms
component-sdk__9cf88e81fa6d6d6f0931503abe6d5afb__.min.js
207 ms
rb.patient-core-ui__c9beccc81b1cb5b55470b0fe1921e3fc__.min.js
136 ms
search__3bb99368a52d1c849bc8baece12d1e1e__.min.js
203 ms
rb0.desktop__433f53287ced7dee102f877359ddad2d__.min.js
202 ms
rb.shared.desktop__c7a96416160e68902d5221cb0b3c9a06__.min.js
131 ms
rb.profile.desktop__13b4c207b03082fe54c958f547c9103d__.min.js
135 ms
rb.practice.desktop__4d295491afe517b16c59baddb5e269f0__.min.js
146 ms
ProceduresAndInsurance
45 ms
gtm.js
556 ms
26463large.jpg
592 ms
81bf6253-fea5-440f-887c-a63388096ca8circle_medium.png
588 ms
9191a9466c2d1497c76f00e82a100d2bsprite_hdr_ftr-regular.png
418 ms
c7f020a3c81ea113defe57f7dd379551dropdown-arrow-blue.png
55 ms
c2751b15da02fb24c50a8029db03d6b7sprite-regular.png
353 ms
31ac43e538be958059a25e5f3072a185KievitSlabPro-Book.woff
194 ms
29eee684aa6b3de12f5bb8a113458a0eSharpSans-No1-Bold.woff
192 ms
759677b23ab04e4ef3b9d621a785d245SharpSans-No1-Semibold.woff
192 ms
1b283d7a04bac78e502cac8ecdd0611cSharpSans-No1-Medium.woff
194 ms
_Incapsula_Resource
221 ms
timeslots
111 ms
timeslots
62 ms
timeslots
109 ms
analytics.js
143 ms
conversion_async.js
169 ms
live.js
168 ms
fbevents.js
150 ms
a_-.js
154 ms
_Incapsula_Resource
56 ms
event
56 ms
event
187 ms
event
148 ms
event
189 ms
event
133 ms
event
149 ms
event
147 ms
event
243 ms
661683190618278
12 ms
hit
53 ms
115 ms
55 ms
98 ms
92 ms
92 ms
collect
83 ms
bounce
28 ms
88 ms
71 ms
66 ms
60 ms
57 ms
366738.gif
16 ms
53 ms
apid
41 ms
js
51 ms
pd.js
328 ms
pixel
101 ms
common.js
15 ms
map.js
33 ms
util.js
32 ms
marker.js
28 ms
overlay.js
28 ms
pixel
120 ms
pixel
119 ms
onion.js
51 ms
openhand_8_8.cur
90 ms
ViewportInfoService.GetViewportInfo
55 ms
controls.js
12 ms
css
62 ms
transparent.png
40 ms
sprite-regular.png
42 ms
Pug
75 ms
google_white5.png
29 ms
mapcnt6.png
41 ms
tmapctrl.png
41 ms
tmapctrl4.png
41 ms
vt
62 ms
vt
56 ms
vt
63 ms
vt
62 ms
vt
57 ms
vt
45 ms
vt
188 ms
tap.php
19 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
31 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
42 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
42 ms
AuthenticationService.Authenticate
37 ms
analytics
75 ms
30 ms
johnhakimmd.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnhakimmd.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 Johnhakimmd.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.
johnhakimmd.com
Open Graph description is not detected on the main page of Johnhakimmd. 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: