2.4 sec in total
68 ms
1.2 sec
1.1 sec
Visit dunhamsbay.com now to see the best up-to-date Dunhamsbay content and also check out these interesting facts you probably never knew about dunhamsbay.com
Enjoy the best of Lake George lodging & dining at our Lake George Resort with amazing views & indoor pool. Perfect for a family vacation, weekend getaway, wedding, conference or special event.
Visit dunhamsbay.comWe analyzed Dunhamsbay.com page load time and found that the first response time was 68 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 45% of websites can load faster.
dunhamsbay.com performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value13.4 s
0/100
25%
Value5.9 s
48/100
10%
Value510 ms
57/100
30%
Value0.235
53/100
15%
Value13.2 s
12/100
10%
68 ms
242 ms
48 ms
56 ms
15 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dunhamsbay.com, 67% (58 requests) were made to Baysidelakegeorge.com and 27% (23 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (411 ms) relates to the external source Baysidelakegeorge.com.
Page size can be reduced by 158.5 kB (6%)
2.5 MB
2.3 MB
In fact, the total size of Dunhamsbay.com main page is 2.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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 158.1 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 158.1 kB or 83% of the original size.
Potential reduce by 0 B
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. Dunhamsbay images are well optimized though.
Potential reduce by 257 B
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 100 B
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. Dunhamsbay.com has all CSS files already compressed.
Number of requests can be reduced by 53 (91%)
58
5
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dunhamsbay. 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 23 to 1 for CSS and as a result speed up the page load time.
dunhamsbay.com
68 ms
baysidelakegeorge.com
242 ms
frontend.min.css
48 ms
css
56 ms
astra-addon-6538ee332d4a11-00511569.css
15 ms
frontend-lite.min.css
30 ms
post-41.css
41 ms
post-30.css
159 ms
elementor-icons.min.css
193 ms
swiper.min.css
157 ms
post-442.css
42 ms
uael-frontend.min.css
70 ms
all.min.css
54 ms
v4-shims.min.css
52 ms
post-540.css
115 ms
css
66 ms
fontawesome.min.css
107 ms
solid.min.css
118 ms
brands.min.css
118 ms
regular.min.css
119 ms
jquery.min.js
121 ms
jquery-migrate.min.js
119 ms
open_in_new_window_yes.js
122 ms
open_in_new_window.js
123 ms
v4-shims.min.js
124 ms
js
114 ms
widget-icon-list.min.css
123 ms
basic.min.css
123 ms
theme-ie11.min.css
126 ms
theme.min.css
125 ms
gravity-forms.min.css
126 ms
frontend.min.js
127 ms
lazysizes.min.js
130 ms
astra-addon-6538ee332d8473-13745784.js
135 ms
uael-nav-menu.min.js
132 ms
jquery_resize.min.js
147 ms
js_cookie.min.js
149 ms
wp-polyfill-inert.min.js
151 ms
regenerator-runtime.min.js
163 ms
wp-polyfill.min.js
162 ms
dom-ready.min.js
407 ms
hooks.min.js
411 ms
i18n.min.js
133 ms
a11y.min.js
143 ms
jquery.json.min.js
140 ms
gravityforms.min.js
133 ms
placeholders.jquery.min.js
343 ms
utils.min.js
297 ms
vendor-theme.min.js
298 ms
scripts-theme.min.js
311 ms
uael-frontend.min.js
293 ms
webpack.runtime.min.js
291 ms
frontend-modules.min.js
292 ms
waypoints.min.js
292 ms
core.min.js
291 ms
frontend.min.js
291 ms
gtm.js
192 ms
homepage-main-cabin.jpg
167 ms
DSC_5624-scaled.jpg
164 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
224 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
243 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
243 ms
fa-solid-900.woff
244 ms
fa-regular-400.woff
222 ms
fa-brands-400.woff
224 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBOshPcIrq0.woff
242 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBPLhPcIrq0.woff
284 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBPihPcIrq0.woff
285 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBOVhPcIrq0.woff
282 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBN5g_cIrq0.woff
282 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBNLg_cIrq0.woff
242 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBMVg_cIrq0.woff
350 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBPLg_cIrq0.woff
284 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBNLgvcIrq0.woff
286 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZT1eTx8cM.woff
282 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZKFeTx8cM.woff
324 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZAVeTx8cM.woff
282 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZdleTx8cM.woff
325 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZmlCTx8cM.woff
327 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFCTx8cM.woff
322 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZ9lCTx8cM.woff
327 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZKFCTx8cM.woff
327 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFGTx8cM.woff
327 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
323 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
324 ms
lake-footer.jpg
154 ms
dunhamsbay.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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
dunhamsbay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
dunhamsbay.com SEO score
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 Dunhamsbay.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 Dunhamsbay.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.
dunhamsbay.com
Open Graph data is detected on the main page of Dunhamsbay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: