3.2 sec in total
96 ms
2.6 sec
424 ms
Click here to check amazing Patokalake content. Otherwise, check out these important facts you probably never knew about patokalake.com
Secluded on 85 acres of pristine woodland, White Oaks Cabins at Patoka Lake is a perfect haven for nature lovers, hopeless romantics, or anyone seeking peace and tranquility.
Visit patokalake.comWe analyzed Patokalake.com page load time and found that the first response time was 96 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
patokalake.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.7 s
85/100
25%
Value2.3 s
98/100
10%
Value140 ms
95/100
30%
Value0
100/100
15%
Value2.6 s
98/100
10%
96 ms
129 ms
20 ms
27 ms
28 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 22% of them (12 requests) were addressed to the original Patokalake.com, 48% (26 requests) were made to Static.xx.fbcdn.net and 26% (14 requests) were made to Scontent-iad3-2.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (986 ms) relates to the external source Facebook.com.
Page size can be reduced by 7.7 kB (3%)
275.6 kB
267.9 kB
In fact, the total size of Patokalake.com main page is 275.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 264.2 kB which makes up the majority of the site volume.
Potential reduce by 4.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 4.0 kB or 62% of the original size.
Potential reduce by 104 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. Patokalake images are well optimized though.
Potential reduce by 3.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. Patokalake.com needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 73% of the original size.
Number of requests can be reduced by 20 (39%)
51
31
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Patokalake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
patokalake.com
96 ms
www.patokalake.com
129 ms
display.css
20 ms
castlethumb.jpg
27 ms
thumb2.jpg
28 ms
thumb3.jpg
23 ms
thumb4.jpg
24 ms
thumb5.jpg
24 ms
welsh-flag.gif
24 ms
tripadvisor_award2017.jpg
23 ms
patokashore2.jpg
23 ms
treegraphic.jpg
42 ms
likebox.php
986 ms
YU1prgYt23u.css
56 ms
KMWcFVqNByY.css
96 ms
KCBgpVwfLM_.css
91 ms
css;%20charset=utf-8,.l_c3pyo2v0u%7Bmargin-bottom:6px%7D.a_c3pyo4on2%7Bmargin-right:8px%7D.r_c3pyo2ey1%20.h_c3pyo4oy5%7B-webkit-box-align:center;display:-webkit-box%7D.y_c3pyo2ta3%7Bmargin-bottom:-6px%7D.u_c3pyo2ta4%7Bpadding-bottom:6px%7D._5v3q%20.l_c3pyo2v0u%7Bmargin-bottom:11px%7D._5v3q%20.l_c3pyo2v0u.i_c3pynyi2f%7Bmargin-bottom:-1px%7D._5v3q%20.l_c3pyo2v0u.i_c3pynyi2f%20.o_c3pynyi2g%7Bpadding-bottom:3px%7D._5v3q%20._5pa-%20.l_c3pyo2v0u%7Bmargin-bottom:7px%7D.r_c3pyo2ey1%7Bborder-bottom:1px%20solid%20%2523e9e9e9;color:%25237f7f7f;display:block;font-size:13px;margin:-18px%200%2014px;padding:13px%200%2013px%7D._5v3q%20._90od%20.r_c3pyo2ey1%7Bborder-bottom:none;padding-bottom:0;padding-top:12px%7D._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1,._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1%20a%7Bcolor:%2523606770%7D._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1%20.profileLink%7Bfont-weight:500%7D._5v3q%20.r_c3pyo2ey1%7Bborder-bottom-color:%2523e5e5e5;color:%252390949c;line-height:15px;margin:-12px%200%2012px;padding:10px%2023px%2010px%200%7D._5v3q%20.r_c3pyo2ey1.x_c3pynzq_4,._1s31.x_c3pynzq_4%20.r_c3pyo2ey1%7Bcolor:%2523616770%7D._5v3q%20.r_c3pyo2ey1.v_c3pynzq_6,._1s31.v_c3pynzq_6%20.r_c3pyo2ey1%7Bfont-size:13px%7D._3ccb%20.r_c3pyo2ey1%7Bfont-size:12px;padding-bottom:9px;padding-top:11px%7D._6q1a%20.i_c3pyo4rdp.r_c3pyo2ey1%7B-webkit-box-align:center;display:-webkit-box%7D._6q1a%20.i_c3pyo4rdp%20.w_c3pyo4re7%7Bfont-size:14px;line-height:16px%7D._6q1a%20.i_c3pyo4rdp%20.w_c3pyo4re7%20.profileLink%7Bfont-weight:bold%7D._6q1a%20.i_c3pyo4rdp%20.e_c3pyo4re8%7B-webkit-box-align:center;background-color:%252342b72a;border-radius:50%25;-webkit-box-shadow:0%202px%204px%200%20rgba(0,%200,%200,%20.1);display:-webkit-inline-box;height:24px;-webkit-box-pack:center;margin-right:8px;width:24px%7D%2523bootloader_TvoAAb3%7Bheight:42px;%7D.bootloader_TvoAAb3%7Bdisplay:block!important;%7D
25 ms
vMwEbhXEBhM.css
86 ms
nYa8oQZnpdr.js
112 ms
WOLN5pzG8JN.js
82 ms
q6VzhXzzuec.js
110 ms
YJojGYumZIr.js
222 ms
iiDbYMCPtB3.js
221 ms
MkVcCW5Kzr9.js
233 ms
1lYRIUv3fB9.js
236 ms
3dOgMOBrGR6.js
240 ms
irCgPB7CJbM.js
240 ms
I-9YqvQlahI.js
271 ms
SixM03AXEw8.js
269 ms
6NWFpg-EZsH.js
262 ms
Nq8nSHiYqQL.js
262 ms
ihjLACFC70L.js
301 ms
kllmdWKFTV2.js
266 ms
271684128_10161865066878228_2403129480972413550_n.png
397 ms
261366167_10161788755628228_8443869194059154228_n.jpg
729 ms
309262303_530216598910688_7056271684694760500_n.jpg
796 ms
306840864_523021996296815_7648499077688045171_n.jpg
763 ms
305808839_519520946646920_5924737790879293765_n.jpg
754 ms
305739083_519521109980237_5305704050218855842_n.jpg
756 ms
305632936_519521449980203_8502743421129863052_n.jpg
780 ms
305741676_519521593313522_1039927363106379584_n.jpg
745 ms
306283278_519520309980317_6635930106281777856_n.jpg
777 ms
303361127_513727170559631_5457630360518053229_n.jpg
851 ms
302437407_511670314098650_1692150036472415202_n.jpg
852 ms
302037930_511670224098659_4699006820639917993_n.jpg
849 ms
302311635_511670254098656_7741758218106614743_n.jpg
847 ms
302013445_511670244098657_789690734715204575_n.jpg
826 ms
UXtr_j2Fwe-.png
321 ms
re1hPxQECWj.png
343 ms
1f642.png
323 ms
1f44c.png
338 ms
1f44d.png
337 ms
01wobW0ovxv.js
32 ms
aJf13HRCfaQ.js
32 ms
patokalake.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
<frame> or <iframe> elements do not have a title
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
patokalake.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
patokalake.com SEO score
EN
EN
US-ASCII
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Patokalake.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 Patokalake.com main page’s claimed encoding is us-ascii. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
patokalake.com
Open Graph description is not detected on the main page of Patokalake. 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: