6.2 sec in total
2.4 sec
3.5 sec
314 ms
Welcome to restaurantelpelicano.com homepage info - get ready to check Restaurantelpelicano best content right away, or after learning these important things about restaurantelpelicano.com
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!
Visit restaurantelpelicano.comWe analyzed Restaurantelpelicano.com page load time and found that the first response time was 2.4 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
restaurantelpelicano.com performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value3.6 s
60/100
25%
Value3.0 s
94/100
10%
Value210 ms
89/100
30%
Value0.099
90/100
15%
Value3.9 s
89/100
10%
2422 ms
104 ms
134 ms
143 ms
128 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 85% of them (45 requests) were addressed to the original Restaurantelpelicano.com, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Restaurantelpelicano.com.
Page size can be reduced by 264.9 kB (29%)
917.7 kB
652.9 kB
In fact, the total size of Restaurantelpelicano.com main page is 917.7 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. 35% of websites need less resources to load. Images take 588.7 kB which makes up the majority of the site volume.
Potential reduce by 17.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 17.7 kB or 75% of the original size.
Potential reduce by 45.2 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. Restaurantelpelicano images are well optimized though.
Potential reduce by 158.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 158.3 kB or 63% of the original size.
Potential reduce by 43.7 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. Restaurantelpelicano.com needs all CSS files to be minified and compressed as it can save up to 43.7 kB or 81% of the original size.
Number of requests can be reduced by 17 (34%)
50
33
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Restaurantelpelicano. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
restaurantelpelicano.com
2422 ms
style.css
104 ms
gold.css
134 ms
brown.css
143 ms
jqModal.css
128 ms
css
24 ms
css
36 ms
styles.css
235 ms
rtw-style.css
235 ms
jquery.js
253 ms
jquery-migrate.min.js
250 ms
jquery.jcarousel.min.js
248 ms
cookie.js
250 ms
jqModal.js
353 ms
custom.js
355 ms
jquery.form.min.js
360 ms
scripts.js
358 ms
wp-emoji-release.min.js
132 ms
analytics.js
125 ms
bg-tile.png
163 ms
176 ms
bigdoth.png
160 ms
nextdot.png
162 ms
prevdot.png
163 ms
logotipo-250x120.png
175 ms
ajax-loader.gif
194 ms
whbg.png
182 ms
5-150x150.jpg
183 ms
3-150x150.jpg
181 ms
1-150x150.jpg
238 ms
4-150x150.jpg
261 ms
2-150x150.jpg
234 ms
menu51-254x182.jpg
252 ms
clear.png
258 ms
blackbox.png
254 ms
menu4-254x182.jpg
307 ms
menu3-254x182.jpg
365 ms
menu2-254x182.jpg
322 ms
menu1-254x182.jpg
326 ms
goverlay.png
339 ms
goright.png
349 ms
goleft.png
367 ms
galclose.png
384 ms
prevver.png
384 ms
nexter.png
411 ms
counter.js
26 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
26 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
26 ms
collect
125 ms
t.php
108 ms
prevdot.png
287 ms
nextdot.png
296 ms
5.jpg
560 ms
restaurantelpelicano.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
restaurantelpelicano.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
Page has valid source maps
restaurantelpelicano.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Restaurantelpelicano.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Spanish. Our system also found out that Restaurantelpelicano.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.
restaurantelpelicano.com
Open Graph description is not detected on the main page of Restaurantelpelicano. 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: