2 sec in total
115 ms
1.1 sec
760 ms
Welcome to drhokemeyer.com homepage info - get ready to check DR Hokemeyer best content right away, or after learning these important things about drhokemeyer.com
Visit drhokemeyer.comWe analyzed Drhokemeyer.com page load time and found that the first response time was 115 ms and then it took 1.9 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.
drhokemeyer.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value10.3 s
0/100
25%
Value24.8 s
0/100
10%
Value1,040 ms
25/100
30%
Value0
100/100
15%
Value40.5 s
0/100
10%
115 ms
24 ms
33 ms
35 ms
30 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 77% of them (95 requests) were addressed to the original Drhokemeyer.com, 7% (9 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (489 ms) belongs to the original domain Drhokemeyer.com.
Page size can be reduced by 71.5 kB (1%)
11.8 MB
11.7 MB
In fact, the total size of Drhokemeyer.com main page is 11.8 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. Only a small number of websites need less resources to load. Images take 10.6 MB which makes up the majority of the site volume.
Potential reduce by 50.7 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 50.7 kB or 78% of the original size.
Potential reduce by 5.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. DR Hokemeyer images are well optimized though.
Potential reduce by 4.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 10.5 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. Drhokemeyer.com has all CSS files already compressed.
Number of requests can be reduced by 88 (79%)
112
24
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DR Hokemeyer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
drhokemeyer.com
115 ms
styles.css
24 ms
email-subscribers-public.css
33 ms
wpa.css
35 ms
grid.min.css
30 ms
helper-parts.min.css
48 ms
main.min.css
40 ms
mediaelementplayer-legacy.min.css
38 ms
wp-mediaelement.min.css
48 ms
style.css
50 ms
font-awesome.min.css
51 ms
style.min.css
71 ms
style.css
74 ms
dripicons.css
61 ms
kiko-all.css
67 ms
font-awesome-5.min.css
77 ms
stylesheet.min.css
89 ms
print.css
83 ms
style_dynamic.css
85 ms
responsive.min.css
118 ms
style_dynamic_responsive.css
122 ms
js_composer.min.css
125 ms
css
45 ms
core-dashboard.min.css
120 ms
elementor-icons.min.css
122 ms
frontend.min.css
139 ms
swiper.min.css
145 ms
post-4364.css
137 ms
global.css
122 ms
post-4392.css
146 ms
style.css
145 ms
css
60 ms
jquery.min.js
146 ms
jquery-migrate.min.js
147 ms
signup-form-widget.min.js
56 ms
rs6.css
145 ms
index.js
147 ms
index.js
146 ms
email-subscribers-public.js
147 ms
api.js
64 ms
wpa.js
146 ms
rbtools.min.js
136 ms
rs6.min.js
144 ms
core.min.js
134 ms
main.min.js
126 ms
accordion.min.js
126 ms
tabs.min.js
123 ms
doubletaptogo.js
130 ms
modernizr.min.js
135 ms
jquery.appear.js
132 ms
hoverIntent.min.js
130 ms
jquery.prettyPhoto.js
120 ms
mediaelement-and-player.min.js
131 ms
mediaelement-migrate.min.js
121 ms
wp-mediaelement.min.js
141 ms
jquery.waitforimages.js
120 ms
jquery.form.min.js
113 ms
waypoints.min.js
110 ms
jquery.easing.1.3.js
104 ms
jquery.mousewheel.min.js
86 ms
jquery.isotope.min.js
88 ms
skrollr.js
92 ms
TweenLite.min.js
97 ms
ScrollToPlugin.min.js
84 ms
smoothPageScroll.min.js
90 ms
default_dynamic.js
84 ms
default.min.js
157 ms
comment-reply.min.js
154 ms
style.css
86 ms
js_composer_front.min.js
154 ms
qode-like.min.js
153 ms
new-tab.js
155 ms
wp-polyfill-inert.min.js
156 ms
regenerator-runtime.min.js
157 ms
wp-polyfill.min.js
156 ms
index.js
155 ms
webpack.runtime.min.js
154 ms
frontend-modules.min.js
154 ms
waypoints.min.js
202 ms
frontend.min.js
148 ms
hooks.min.js
148 ms
i18n.min.js
143 ms
elementor.js
139 ms
logo_v5_1.png
365 ms
logo_black.png
92 ms
EveningRocks-bw-scaled.jpg
93 ms
EveningRocks-text-scaled.jpg
231 ms
ChoyaGray-bw-scaled.jpg
237 ms
ChoyaGray-text-scaled.jpg
239 ms
Closest-bw-scaled.jpg
232 ms
Closest-text-scaled.jpg
230 ms
bolders-bw-scaled.jpg
232 ms
bolders-text-scaled.jpg
362 ms
JTWhiteSpace-bw-scaled.jpg
361 ms
JTWhiteSpace-text-scaled.jpg
363 ms
RedClose-bw-scaled.jpg
275 ms
RedClose-text-new-clin-phil-scaled.jpg
359 ms
logo_v5_1_white_footer2.png
269 ms
logo_v5_1_white.png
360 ms
flU8Rqu5zY00QEpyWJYWN5f9XeM.ttf
72 ms
flUhRqu5zY00QEpyWJYWN58AfvNQKBY.ttf
182 ms
flUhRqu5zY00QEpyWJYWN59Yf_NQKBY.ttf
194 ms
flU-Rqu5zY00QEpyWJYWN5-Qbep5CA.ttf
227 ms
flUhRqu5zY00QEpyWJYWN59IePNQKBY.ttf
195 ms
flUhRqu5zY00QEpyWJYWN59wevNQKBY.ttf
194 ms
fontawesome-webfont.woff
489 ms
underscore-min.js
181 ms
ElegantIcons.woff
280 ms
recaptcha__en.js
104 ms
signup-form-widget.css
18 ms
24f0ea737b1b47a3c6a1513362851409.json
137 ms
anchor
47 ms
styles__ltr.css
5 ms
recaptcha__en.js
46 ms
ctct-close-x.svg
114 ms
anchor
108 ms
logo-ctct-white.svg
132 ms
PSKopaksc4v0TeE9MSufUBd6uLsTLN3_1JKIESb4JYg.js
72 ms
webworker.js
90 ms
logo_48.png
59 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
23 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
23 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
22 ms
recaptcha__en.js
91 ms
drhokemeyer.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
drhokemeyer.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
Page has valid source maps
drhokemeyer.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drhokemeyer.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 Drhokemeyer.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.
drhokemeyer.com
Open Graph description is not detected on the main page of DR Hokemeyer. 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: