14.4 sec in total
240 ms
13.8 sec
404 ms
Visit restaurantebutarque.es now to see the best up-to-date Restaurante Butarque content and also check out these interesting facts you probably never knew about restaurantebutarque.es
Restaurante Butarque In&Out. Parque Butarque en Leganés. Madrid. 3 ambientes únicos en Madrid, terraza de verano, salón de evento y Chill Out
Visit restaurantebutarque.esWe analyzed Restaurantebutarque.es page load time and found that the first response time was 240 ms and then it took 14.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
restaurantebutarque.es performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value12.9 s
0/100
25%
Value14.1 s
1/100
10%
Value1,490 ms
14/100
30%
Value0.032
100/100
15%
Value13.2 s
12/100
10%
240 ms
4555 ms
290 ms
333 ms
293 ms
Our browser made a total of 183 requests to load all elements on the main page. We found that 94% of them (172 requests) were addressed to the original Restaurantebutarque.es, 3% (6 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Restaurantebutarque.es.
Page size can be reduced by 271.8 kB (25%)
1.1 MB
812.1 kB
In fact, the total size of Restaurantebutarque.es main page is 1.1 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. 70% of websites need less resources to load. Images take 429.7 kB which makes up the majority of the site volume.
Potential reduce by 198.5 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 198.5 kB or 83% of the original size.
Potential reduce by 753 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. Restaurante Butarque images are well optimized though.
Potential reduce by 16.5 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 16.5 kB or 11% of the original size.
Potential reduce by 56.1 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. Restaurantebutarque.es needs all CSS files to be minified and compressed as it can save up to 56.1 kB or 21% of the original size.
Number of requests can be reduced by 161 (94%)
171
10
The browser has sent 171 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Restaurante Butarque. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 94 to 1 for JavaScripts and from 69 to 1 for CSS and as a result speed up the page load time.
restaurantebutarque.es
240 ms
restaurantebutarque.es
4555 ms
bootstrap-light.min.css
290 ms
base.min.css
333 ms
woo-widget-price-filter.min.css
293 ms
style.min.css
410 ms
mediaelementplayer-legacy.min.css
401 ms
wp-mediaelement.min.css
391 ms
tutor-icon.min.css
417 ms
tutor.min.css
638 ms
tutor-front.min.css
482 ms
js_composer.min.css
666 ms
widget-wd-recent-posts.min.css
508 ms
widget-nav.min.css
515 ms
woo-widget-wd-layered-nav.min.css
524 ms
woo-mod-swatches-base.min.css
584 ms
woo-mod-swatches-filter.min.css
627 ms
woo-widget-product-cat.min.css
648 ms
woo-widget-product-list.min.css
625 ms
woo-widget-slider-price-filter.min.css
685 ms
opt-lazy-load.min.css
735 ms
wp-gutenberg.min.css
730 ms
int-wpcf7.min.css
745 ms
int-rev-slider.min.css
741 ms
int-wpb-base.min.css
767 ms
int-wpb-base-deprecated.min.css
801 ms
woocommerce-base.min.css
842 ms
mod-star-rating.min.css
864 ms
woo-el-track-order.min.css
863 ms
woo-gutenberg.min.css
853 ms
style.css
872 ms
header-base.min.css
916 ms
mod-tools.min.css
954 ms
header-el-base.min.css
956 ms
el-social-icons.min.css
979 ms
header-el-my-account.min.css
971 ms
header-el-search.min.css
977 ms
css
26 ms
w.js
17 ms
css
13 ms
header-el-cart-side.min.css
867 ms
header-el-cart.min.css
766 ms
woo-widget-shopping-cart.min.css
779 ms
wpb-el-banner.min.css
756 ms
el-banner-hover-zoom.min.css
705 ms
el-banner-btn-hover.min.css
688 ms
mod-highlighted-text.min.css
762 ms
el-section-title.min.css
756 ms
el-section-title-style-under-and-over.min.css
704 ms
woo-categories-loop-layout-masonry.min.css
698 ms
woo-categories-loop-old.min.css
686 ms
lib-owl-carousel.min.css
674 ms
woo-product-loop.min.css
689 ms
woo-product-loop-quick.min.css
665 ms
lib-magnific-popup.min.css
683 ms
blog-base.min.css
665 ms
blog-loop-base-old.min.css
662 ms
blog-loop-design-masonry.min.css
627 ms
el-instagram.min.css
686 ms
footer-base.min.css
694 ms
opt-scrolltotop.min.css
694 ms
wd-search-results.min.css
693 ms
wd-search-form.min.css
666 ms
opt-sticky-social.min.css
667 ms
header-el-search-fullscreen-general.min.css
669 ms
header-el-search-fullscreen-1.min.css
668 ms
woo-mod-login-form.min.css
685 ms
header-el-my-account-sidebar.min.css
665 ms
wc-blocks.css
685 ms
v4-shims.min.css
668 ms
all.min.css
675 ms
rs6.css
685 ms
wp-polyfill-inert.min.js
750 ms
regenerator-runtime.min.js
732 ms
wp-polyfill.min.js
731 ms
hooks.min.js
675 ms
jquery.min.js
750 ms
jquery-migrate.min.js
697 ms
jquery.blockUI.min.js
692 ms
add-to-cart.min.js
722 ms
js.cookie.min.js
723 ms
woocommerce.min.js
725 ms
woocommerce-add-to-cart.js
688 ms
kk-script.js
693 ms
device.min.js
729 ms
scrollBar.min.js
719 ms
updateCartFragmentsFix.js
782 ms
index.js
758 ms
index.js
695 ms
rbtools.min.js
898 ms
rs6.min.js
998 ms
i18n.min.js
878 ms
tutor.min.js
998 ms
quicktags.min.js
877 ms
core.min.js
818 ms
mouse.min.js
820 ms
sortable.min.js
812 ms
jquery.ui.touch-punch.js
801 ms
SocialShare.min.js
802 ms
tutor-front.min.js
913 ms
datepicker.min.js
872 ms
sourcebuster.min.js
849 ms
order-attribution.min.js
815 ms
react.min.js
871 ms
deprecated.min.js
881 ms
dom.min.js
903 ms
react-dom.min.js
945 ms
escape-html.min.js
808 ms
element.min.js
817 ms
is-shallow-equal.min.js
804 ms
keycodes.min.js
816 ms
g.gif
13 ms
priority-queue.min.js
824 ms
compose.min.js
817 ms
private-apis.min.js
883 ms
redux-routine.min.js
839 ms
data.min.js
853 ms
lodash.min.js
878 ms
wc-blocks-registry.js
866 ms
url.min.js
916 ms
api-fetch.min.js
893 ms
wc-settings.js
866 ms
fbevents.js
62 ms
data-controls.min.js
857 ms
html-entities.min.js
899 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
81 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
82 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
221 ms
S6uyw4BMUTPHjx4wWw.ttf
223 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
223 ms
notices.min.js
889 ms
wc-blocks-middleware.js
924 ms
wc-blocks-data.js
879 ms
dom-ready.min.js
802 ms
a11y.min.js
888 ms
primitives.min.js
907 ms
warning.min.js
947 ms
blocks-components.js
996 ms
blocks-checkout.js
1074 ms
order-attribution-blocks.min.js
933 ms
js_composer_front.min.js
901 ms
helpers.min.js
973 ms
woocommerceNotices.min.js
954 ms
headerBuilder.min.js
988 ms
menuOffsets.min.js
997 ms
menuSetUp.min.js
994 ms
loginSidebar.min.js
979 ms
onRemoveFromCart.min.js
988 ms
lazyLoading.min.js
980 ms
imagesloaded.min.js
973 ms
owl.carousel.min.js
1006 ms
owlCarouselInit.min.js
973 ms
magnific-popup.min.js
984 ms
productImagesGallery.min.js
972 ms
quickView.min.js
999 ms
tooltips.min.js
1000 ms
btnsToolTips.min.js
946 ms
swatchesVariations.min.js
938 ms
addToCartAllTypes.min.js
964 ms
woocommerceQuantity.min.js
941 ms
underscore.min.js
968 ms
wp-util.min.js
912 ms
add-to-cart-variation.min.js
910 ms
scrollTop.min.js
922 ms
mobileNavigation.min.js
944 ms
autocomplete.min.js
872 ms
ajaxSearch.min.js
903 ms
cartWidget.min.js
812 ms
cart-fragments.min.js
799 ms
stickySocialButtons.min.js
758 ms
searchFullScreen.min.js
763 ms
fa-regular-400.woff
817 ms
fa-solid-900.woff
984 ms
logo-restaurante-butarque-inout-horizontal.jpg
725 ms
dummy.png
705 ms
restaurantebutarque.es
1969 ms
restaurante-butarque-terraza-de-verano-2020.jpg
394 ms
Restaurante-Butarque-salon-interior.jpg
405 ms
Chill-Out-Restaurante-Butarque-de-Leganes-madrid.jpg
710 ms
2520 ms
9k=
3304 ms
9k=
3195 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
4 ms
restaurantebutarque.es accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
restaurantebutarque.es 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
restaurantebutarque.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Restaurantebutarque.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Restaurantebutarque.es 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.
restaurantebutarque.es
Open Graph data is detected on the main page of Restaurante Butarque. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: