4.2 sec in total
328 ms
3.3 sec
513 ms
Click here to check amazing Holland Eye content. Otherwise, check out these important facts you probably never knew about hollandeye.com
Welcome to our Home page. Contact Holland Eye Surgery & Laser Center today at 616-396-2316 or visit our office servicing Holland, MI
Visit hollandeye.comWe analyzed Hollandeye.com page load time and found that the first response time was 328 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
hollandeye.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value9.2 s
1/100
25%
Value6.5 s
38/100
10%
Value180 ms
92/100
30%
Value0
100/100
15%
Value8.8 s
35/100
10%
328 ms
611 ms
59 ms
69 ms
140 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 40% of them (22 requests) were addressed to the original Hollandeye.com, 20% (11 requests) were made to Styles.prosites.com and 11% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Analytics.prosites.com.
Page size can be reduced by 414.7 kB (15%)
2.7 MB
2.3 MB
In fact, the total size of Hollandeye.com main page is 2.7 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 31.9 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. This page needs HTML code to be minified as it can gain 6.5 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.9 kB or 73% of the original size.
Potential reduce by 104.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. Holland Eye images are well optimized though.
Potential reduce by 109.8 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 109.8 kB or 33% of the original size.
Potential reduce by 168.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. Hollandeye.com needs all CSS files to be minified and compressed as it can save up to 168.3 kB or 79% of the original size.
Number of requests can be reduced by 33 (70%)
47
14
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Holland Eye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.hollandeye.com
328 ms
bootstrap.min.css
611 ms
css
59 ms
font-awesome.min.css
69 ms
animate.min.css
140 ms
owl.carousel.css
188 ms
sm-core-css.css
206 ms
video-js.css
252 ms
jquery.fancybox.css
275 ms
plugins.css
275 ms
pagecontrols.css
102 ms
default.css
79 ms
navigation.css
89 ms
jquery-1.9.1.min.js
76 ms
jquery-migrate-1.1.0.min.js
72 ms
WebForms.js
30 ms
MicrosoftAjax.js
33 ms
MicrosoftAjaxWebForms.js
32 ms
bootstrap.min.js
279 ms
jquery.smartmenus_v1.0.0.js
276 ms
RWDUtil.js
273 ms
Functions.js
316 ms
default.js
73 ms
carousel.js
338 ms
jquery.easing.min.js
337 ms
wow.min.js
338 ms
owl.carousel.min.js
342 ms
jquery.fancybox.pack.js
344 ms
video.js
439 ms
classie.js
403 ms
scrolling-nav.js
402 ms
placeholders.min.js
405 ms
matomo.js
468 ms
FB-f-Logo__blue_72.png
338 ms
carecredit_button_applypay_prequal_350x213_bluegreen_v1.jpg
154 ms
logo.png
44 ms
thumbnail_Doctor%20Group%20Photo-1.jpg
935 ms
building2020.jpg
1144 ms
pay%20bill.png
421 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
51 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
50 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
127 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
137 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
139 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
139 ms
cover1.jpg
138 ms
contact-bg.jpg
109 ms
cover-testimonial.jpg
120 ms
fontawesome-webfont.woff
250 ms
ga.js
77 ms
__utm.gif
12 ms
matomo.php
201 ms
matomo.php
1071 ms
configs.php
222 ms
configs.php
1437 ms
hollandeye.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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
hollandeye.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
hollandeye.com SEO score
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
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 Hollandeye.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 Hollandeye.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.
hollandeye.com
Open Graph description is not detected on the main page of Holland Eye. 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: