2.4 sec in total
93 ms
1.4 sec
848 ms
Welcome to drhockemeyer.com homepage info - get ready to check Dr Hockemeyer best content right away, or after learning these important things about drhockemeyer.com
Top optometrists serving New Haven & Allen County, IN are right in sight! Contact Hockemeyer Family Eye Care to schedule an appointment with an eye doctor.
Visit drhockemeyer.comWe analyzed Drhockemeyer.com page load time and found that the first response time was 93 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.
drhockemeyer.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value29.2 s
0/100
25%
Value10.4 s
8/100
10%
Value1,360 ms
16/100
30%
Value0.423
23/100
15%
Value20.4 s
2/100
10%
93 ms
124 ms
123 ms
101 ms
108 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 24% of them (24 requests) were addressed to the original Drhockemeyer.com, 36% (36 requests) were made to Fonts.gstatic.com and 8% (8 requests) were made to Files.hellonetcdn.com. The less responsive or slowest element that took the longest time to load (649 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 951.9 kB (21%)
4.5 MB
3.5 MB
In fact, the total size of Drhockemeyer.com main page is 4.5 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. 80% 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. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 149.0 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 149.0 kB or 83% of the original size.
Potential reduce by 43.8 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 Hockemeyer images are well optimized though.
Potential reduce by 722.3 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 722.3 kB or 62% of the original size.
Potential reduce by 36.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. Drhockemeyer.com needs all CSS files to be minified and compressed as it can save up to 36.8 kB or 49% of the original size.
Number of requests can be reduced by 42 (76%)
55
13
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dr Hockemeyer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
drhockemeyer.com
93 ms
drhockemeyer.com
124 ms
graphs-lite-public.css
123 ms
choices.min.css
101 ms
intl-tel-input.min.css
108 ms
richtext.min.css
69 ms
content.min.css
102 ms
wpforms-classic-full.min.css
33 ms
style.css
56 ms
745993043f.js
62 ms
et-core-unified-7.min.css
73 ms
jquery.min.js
86 ms
jquery-migrate.min.js
84 ms
Chart.min.js
37 ms
graphs-lite-public.js
98 ms
scripts.min.js
102 ms
jquery.fitvids.js
215 ms
common.js
329 ms
smush-lazy-load.min.js
207 ms
sticky-elements.js
245 ms
gtm.js
325 ms
fbevents.js
101 ms
605 ms
embed
312 ms
embed
347 ms
widget.js
452 ms
IMG_8943-1.jpg
407 ms
hockemeyer-logo-2.png
66 ms
92zPtBhPNqw79Ij1E865zBUv7myRJQVF.woff
129 ms
92zPtBhPNqw79Ij1E865zBUv7myRJQVG.ttf
167 ms
92zPtBhPNqw79Ij1E865zBUv7myjJQVF.woff
162 ms
92zPtBhPNqw79Ij1E865zBUv7myjJQVG.ttf
166 ms
92zPtBhPNqw79Ij1E865zBUv7mz9JQVF.woff
185 ms
92zPtBhPNqw79Ij1E865zBUv7mz9JQVG.ttf
185 ms
92zPtBhPNqw79Ij1E865zBUv7mwjJQVF.woff
186 ms
92zPtBhPNqw79Ij1E865zBUv7mwjJQVG.ttf
207 ms
92zPtBhPNqw79Ij1E865zBUv7myjJAVF.woff
284 ms
92zPtBhPNqw79Ij1E865zBUv7myjJAVG.ttf
208 ms
92zPtBhPNqw79Ij1E865zBUv7mx9IgVF.woff
230 ms
92zPtBhPNqw79Ij1E865zBUv7mx9IgVG.ttf
230 ms
92zPtBhPNqw79Ij1E865zBUv7mxEIgVF.woff
231 ms
92zPtBhPNqw79Ij1E865zBUv7mxEIgVG.ttf
279 ms
92zPtBhPNqw79Ij1E865zBUv7mwjIgVF.woff
341 ms
92zPtBhPNqw79Ij1E865zBUv7mwjIgVG.ttf
280 ms
92zPtBhPNqw79Ij1E865zBUv7mwKIgVF.woff
279 ms
92zPtBhPNqw79Ij1E865zBUv7mwKIgVG.ttf
278 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZt8FNI4.woff
284 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZt8FNI0.ttf
280 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZu0FNI4.woff
340 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZu0FNI0.ttf
278 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZrMFNI4.woff
387 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZrMFNI0.ttf
280 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZm0FNI4.woff
340 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZm0FNI0.ttf
337 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZu0ENI4.woff
445 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZu0ENI0.ttf
446 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZjMCNI4.woff
422 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZjMCNI0.ttf
421 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZgoCNI4.woff
421 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZgoCNI0.ttf
463 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZm0CNI4.woff
513 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZm0CNI0.ttf
519 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZkQCNI4.woff
649 ms
92zJtBhPNqw73oHH7BbQp4-B6XlrZkQCNI0.ttf
648 ms
modules.woff
179 ms
fa-solid-900.woff
159 ms
fa-brands-400.woff
126 ms
fa-regular-400.woff
121 ms
js
221 ms
js
117 ms
analytics.js
161 ms
d66uaaqxv9
164 ms
widget_app_base_1707998198539.js
56 ms
collect
51 ms
collect
146 ms
clarity.js
38 ms
css
82 ms
all.min.css
35 ms
video.6.13.0.js
190 ms
video-js.min.6.13.0.css
162 ms
jquery.min.js
104 ms
videojs-contextmenu-ui.css
158 ms
rt-videojs-playlist-ui.css
160 ms
videojs-ie8.min.js
161 ms
videojs-playlist.min.js
164 ms
videojs-playlist-ui.min.js
164 ms
videojs-contextmenu.min.js
170 ms
videojs-contextmenu-ui.min.js
176 ms
CustomCCButton.js
132 ms
videojs-resolution-switcher-v7_20210303.js
141 ms
videojs-resolution-switcher-v7.css
135 ms
KolorWheel.min.js
151 ms
SharePanel.js
156 ms
unmute.png
69 ms
innewhav22_2_60_rev1_iwd1.jpg
68 ms
universal_tracking.php
178 ms
AKZC3Y+AA==
33 ms
fa-brands-400.ttf
47 ms
fa-solid-900.ttf
58 ms
fa-regular-400.ttf
53 ms
c.gif
8 ms
drhockemeyer.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.
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
drhockemeyer.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
drhockemeyer.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Drhockemeyer.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 Drhockemeyer.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.
drhockemeyer.com
Open Graph data is detected on the main page of Dr Hockemeyer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: