2.8 sec in total
174 ms
1.8 sec
912 ms
Welcome to pelicaninn.com homepage info - get ready to check Pelican Inn best content for United States right away, or after learning these important things about pelicaninn.com
The Pelican Inn at Muir Beach opens its doors to you for the fellowship of its Tudor bar, country cooking, or a getaway of carefree feasting and relaxation.
Visit pelicaninn.comWe analyzed Pelicaninn.com page load time and found that the first response time was 174 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pelicaninn.com performance score
174 ms
260 ms
358 ms
85 ms
135 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 72% of them (51 requests) were addressed to the original Pelicaninn.com, 8% (6 requests) were made to Cdnjs.cloudflare.com and 4% (3 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (716 ms) relates to the external source Cdn.enable.co.il.
Page size can be reduced by 553.6 kB (17%)
3.3 MB
2.8 MB
In fact, the total size of Pelicaninn.com main page is 3.3 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. 60% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 423.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 423.7 kB or 75% of the original size.
Potential reduce by 37.6 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. Pelican Inn images are well optimized though.
Potential reduce by 75.0 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 75.0 kB or 15% of the original size.
Potential reduce by 17.2 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. Pelicaninn.com needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 22% of the original size.
Number of requests can be reduced by 29 (47%)
62
33
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pelican Inn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
pelicaninn.com
174 ms
pelicaninn.com
260 ms
www.pelicaninn.com
358 ms
js
85 ms
style.min.css
135 ms
jquery.min.js
260 ms
jquery-migrate.min.js
229 ms
gcommerce-ada-fixes.js
197 ms
slick.min.css
62 ms
flatpickr.min.css
73 ms
app.css
297 ms
stylesheet.css
207 ms
stylesheet.css
218 ms
css
46 ms
f6026b71-27fa-41f8-a282-2ea2f84c53a7.css
55 ms
dashicons.min.css
355 ms
display-structure.css
322 ms
init.js
716 ms
slick.min.js
21 ms
imagesloaded.min.js
228 ms
masonry.min.js
322 ms
gmaps.min.js
22 ms
flatpickr.min.js
23 ms
jquery.waypoints.min.js
22 ms
bundle.js
322 ms
underscore.min.js
321 ms
backbone.min.js
322 ms
front-end-deps.js
454 ms
api.js
38 ms
front-end.js
454 ms
analytics.js
84 ms
864457681
399 ms
pelicaninn_seamlessbackgroundwhite.jpg
296 ms
header-logo@2x.png
117 ms
home-logo@2x.png
119 ms
pelicaninn1.jpg
336 ms
1800x750.png
187 ms
480x400.png
195 ms
muirbeach_large2.jpg
530 ms
ext_dusk_large.jpg
422 ms
icon-calendar.svg
266 ms
decorative-line-2.svg
256 ms
woodcut@2x.png
318 ms
decorative-line-1.svg
329 ms
B6OgjKAJyIt.jpg
361 ms
640x640.png
384 ms
B6JHgVxpWpw.jpg
527 ms
B6BXe1BpSmr.jpg
529 ms
B58TyrFJTju.jpg
528 ms
B53WiZCJQmk.jpg
587 ms
B5vU5Cspnez.jpg
531 ms
B5qmtrkJj9a.jpg
531 ms
B5lBizlJXKD.jpg
534 ms
B5c-KO9p_pX.jpg
583 ms
home-1@2x-80-e1485960055861.jpg
594 ms
pelicaninn@2x.png
592 ms
romantic-places@2x.png
593 ms
alpenhof@2x.png
594 ms
culloden-house@2x.png
609 ms
mountain-home-inn@2x.png
612 ms
taychreggan@2x.png
596 ms
seamless_wall_texture2black.jpg
595 ms
domisc__-webfont.woff
605 ms
fa9e5c7b-5b75-43c5-a37e-a41ca7bc49c0.woff
151 ms
Ktk1ALSLW8zDe0rthJysWrnLsAzHEKOe.woff
43 ms
f0cc6d32-ccc9-4a1b-8215-7b4195332a9e.woff
120 ms
e-phemera_-_temporal-webfont.woff
624 ms
collect
24 ms
js
52 ms
api.js
12 ms
recaptcha__en.js
73 ms
pelicaninn.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pelicaninn.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 Pelicaninn.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.
pelicaninn.com
Open Graph data is detected on the main page of Pelican Inn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: