4.3 sec in total
265 ms
3.4 sec
688 ms
Welcome to berlioz.mx homepage info - get ready to check Berlioz best content for Mexico right away, or after learning these important things about berlioz.mx
Catering Corporativo, para tus juntas y eventos, Berlioz ofrece una comida gourmet de tres tiempos, servida en una elegante caja práctica y sofisticada.
Visit berlioz.mxWe analyzed Berlioz.mx page load time and found that the first response time was 265 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
berlioz.mx performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value5.4 s
20/100
25%
Value16.7 s
0/100
10%
Value2,000 ms
7/100
30%
Value0.204
61/100
15%
Value16.7 s
5/100
10%
265 ms
32 ms
209 ms
196 ms
199 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 79% of them (78 requests) were addressed to the original Berlioz.mx, 18% (18 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Berlioz.mx.
Page size can be reduced by 247.0 kB (35%)
713.3 kB
466.3 kB
In fact, the total size of Berlioz.mx main page is 713.3 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. 70% of websites need less resources to load. Javascripts take 389.1 kB which makes up the majority of the site volume.
Potential reduce by 168.4 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 168.4 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. Berlioz images are well optimized though.
Potential reduce by 56.1 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 56.1 kB or 14% of the original size.
Potential reduce by 22.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. Berlioz.mx needs all CSS files to be minified and compressed as it can save up to 22.6 kB or 18% of the original size.
Number of requests can be reduced by 65 (96%)
68
3
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Berlioz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
berlioz.mx
265 ms
style-index.css
32 ms
font-awesome.min.css
209 ms
swiper.min.css
196 ms
style.min.css
199 ms
metorik.css
179 ms
wccs-public.min.css
39 ms
style.css
41 ms
elementor-icons.min.css
204 ms
frontend-lite.min.css
240 ms
swiper.min.css
326 ms
post-11733.css
213 ms
frontend-lite.min.css
224 ms
global.css
376 ms
post-5274.css
384 ms
jquery-ui.css
242 ms
frontendstyles.css
250 ms
flatsome.css
259 ms
flatsome-shop.css
271 ms
style.css
274 ms
css
38 ms
jquery.min.js
277 ms
jquery-migrate.min.js
280 ms
core.min.js
477 ms
datepicker.min.js
293 ms
zcga.js
475 ms
tyche.js
477 ms
widget-animated-headline.min.css
322 ms
widget-carousel.min.css
452 ms
css
28 ms
rs6.css
451 ms
lazysizes.min.js
698 ms
rbtools.min.js
700 ms
rs6.min.js
454 ms
jquery.blockUI.min.js
698 ms
add-to-cart.min.js
455 ms
js.cookie.min.js
697 ms
woocommerce.min.js
697 ms
cart-fragments.min.js
697 ms
gtm4wp-ecommerce-generic.js
758 ms
gtm4wp-woocommerce.js
843 ms
metorik.min.js
864 ms
tracker.js
703 ms
flatsome-live-search.js
540 ms
index.js
691 ms
wp-polyfill-inert.min.js
584 ms
regenerator-runtime.min.js
969 ms
wp-polyfill.min.js
574 ms
hoverIntent.min.js
945 ms
flatsome.js
640 ms
woocommerce.js
644 ms
swiper.min.js
859 ms
scripts.min.js
769 ms
jquery-numerator.min.js
776 ms
imagesloaded.min.js
791 ms
webpack-pro.runtime.min.js
908 ms
webpack.runtime.min.js
780 ms
frontend-modules.min.js
946 ms
hooks.min.js
894 ms
i18n.min.js
922 ms
frontend.min.js
1268 ms
btynawch.js
469 ms
waypoints.min.js
1172 ms
frontend.min.js
896 ms
elements-handlers.min.js
912 ms
underscore.min.js
917 ms
wp-util.min.js
955 ms
frontend.min.js
1055 ms
dummy.png
925 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
125 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff
929 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
125 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
222 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
243 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
246 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
245 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
244 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
246 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
243 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf
98 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf
101 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf
101 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf
101 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf
101 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf
102 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf
104 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf
103 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf
103 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff
886 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff
863 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff
884 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff
998 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff
883 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff
1060 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff
965 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff
997 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff
1286 ms
fl-icons.ttf
891 ms
eicons.woff
926 ms
berlioz.mx accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
berlioz.mx 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
berlioz.mx 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
![]()
ES
![]()
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berlioz.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Berlioz.mx 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.
berlioz.mx
Open Graph data is detected on the main page of Berlioz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: