8.3 sec in total
1.1 sec
5.3 sec
1.8 sec
Click here to check amazing La Cantine content. Otherwise, check out these important facts you probably never knew about lacantine.ae
Visit lacantine.aeWe analyzed Lacantine.ae page load time and found that the first response time was 1.1 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lacantine.ae performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value74.9 s
0/100
25%
Value42.7 s
0/100
10%
Value5,120 ms
0/100
30%
Value0
100/100
15%
Value85.3 s
0/100
10%
1129 ms
284 ms
561 ms
290 ms
379 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 59% of them (91 requests) were addressed to the original Lacantine.ae, 7% (10 requests) were made to Use.fortawesome.com and 5% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Lacantine.ae.
Page size can be reduced by 9.4 MB (35%)
26.5 MB
17.2 MB
In fact, the total size of Lacantine.ae main page is 26.5 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. Only a small number of websites need less resources to load. Javascripts take 13.8 MB which makes up the majority of the site volume.
Potential reduce by 178.8 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 178.8 kB or 86% of the original size.
Potential reduce by 761.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. La Cantine images are well optimized though.
Potential reduce by 7.6 MB
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 7.6 MB or 55% of the original size.
Potential reduce by 849.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. Lacantine.ae needs all CSS files to be minified and compressed as it can save up to 849.7 kB or 84% of the original size.
Number of requests can be reduced by 88 (68%)
129
41
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of La Cantine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
lacantine.ae
1129 ms
custom-color-overrides.css
284 ms
style.css
561 ms
frontend.min.css
290 ms
elementor-icons.min.css
379 ms
custom-frontend-lite.min.css
570 ms
swiper.min.css
288 ms
post-10.css
288 ms
custom-pro-frontend-lite.min.css
381 ms
global.css
660 ms
post-11.css
663 ms
post-468.css
470 ms
post-452.css
472 ms
post-114.css
577 ms
post-145.css
578 ms
css
30 ms
fontawesome.min.css
653 ms
solid.min.css
658 ms
js
49 ms
custom-pro-widget-nav-menu.min.css
658 ms
custom-widget-icon-list.min.css
526 ms
flatpickr.min.css
685 ms
animations.min.css
683 ms
responsive-embeds.js
702 ms
jquery.min.js
737 ms
jquery-migrate.min.js
683 ms
jquery.smartmenus.min.js
681 ms
api.js
41 ms
flatpickr.min.js
739 ms
webpack-pro.runtime.min.js
737 ms
webpack.runtime.min.js
738 ms
frontend-modules.min.js
739 ms
wp-polyfill-inert.min.js
738 ms
regenerator-runtime.min.js
873 ms
wp-polyfill.min.js
874 ms
hooks.min.js
871 ms
i18n.min.js
871 ms
frontend.min.js
872 ms
waypoints.min.js
872 ms
core.min.js
1037 ms
frontend.min.js
1037 ms
elements-handlers.min.js
940 ms
jquery.sticky.min.js
941 ms
underscore.min.js
940 ms
wp-util.min.js
849 ms
frontend.min.js
1033 ms
gtm.js
118 ms
lacantinedufaubourg
502 ms
logo-black.svg.svg
712 ms
whatsapp.svg
710 ms
menu.svg
714 ms
parisian2.png
1040 ms
parisian3.png
1031 ms
DSC05992-2.jpg
1021 ms
DSC05488-pc.jpg
1025 ms
DSC05467-pc.jpg
1052 ms
DSC02928-12.jpg
1029 ms
DSC05488-phone.jpg
1051 ms
DSC05467-phone.jpg
1025 ms
DSC02928-1.jpg
982 ms
134 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
105 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
136 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
199 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
222 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
357 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
357 ms
dsc02937.webp
941 ms
dsc02922.webp
957 ms
polyfills.js
961 ms
dsc02869.webp
1056 ms
js
155 ms
124 ms
fbevents.js
57 ms
bl1.webp
1023 ms
bl2.webp
1075 ms
bl3.webp
1226 ms
1.webp
1226 ms
2.webp
1223 ms
3.webp
1223 ms
embed
488 ms
m1.webp
1213 ms
194 ms
191 ms
m2.webp
1090 ms
m3.webp
1093 ms
AVI8939-1-1.jpg
1096 ms
DSC05707-Enhanced-NR-1-1.jpg
1096 ms
DSC05970-Enhanced-NR-2-1-1.jpg
1096 ms
AVI8939.jpg
1091 ms
fonts.efde74f5438f3df965f2.css
53 ms
js
72 ms
sdk.js
750 ms
jquery.min.js
228 ms
260 ms
288 ms
production.crypto.efde74f5438f3df965f2.js
217 ms
commons.efde74f5438f3df965f2.js
648 ms
dining.js
584 ms
client
288 ms
client:platform.js
261 ms
a2a676c1.js
264 ms
5c2efbbd.js
397 ms
cb6d04c8.js
530 ms
DSC05707-Enhanced-NR.jpg
928 ms
DSC05970-Enhanced-NR-2.jpg
1033 ms
bar1.png
1038 ms
bar2.png
1037 ms
DSC05997-1.webp
1034 ms
barM1.png
1034 ms
gtm.js
175 ms
analytics.js
344 ms
151 ms
js
175 ms
130 ms
js
321 ms
barM2.png
851 ms
DSC05997-2.webp
918 ms
private.png
971 ms
home-events.png
974 ms
250 ms
246 ms
collect
117 ms
arts-home.png
681 ms
dsc001268.png
605 ms
collect
38 ms
dsc001269.png
667 ms
whatsapp-b.svg
641 ms
rikas-logo-white.png.svg
660 ms
logo-black-1.svg-1.svg
720 ms
logo-black-2.svg-2.svg
723 ms
Vector.svg
724 ms
ga-audiences
27 ms
recaptcha__en.js
282 ms
sdk.js
148 ms
cb=gapi.loaded_0
113 ms
m-outer-3437aaddcdf6922d623e172c2d6f9278.html
107 ms
AMIfv97-N2oeGO7xkGhlZYhBji5Z4F2a7xnR6q1_byqP1fqxwh34UVpoTzz1fTSX6CeCzsRwI3YYg5lUxGzKwYoCcfnyVTHH3pcs3qRIrnEGXwCQ_7gYFqh0C9-mlmG77GC_OHkbreSzweHA6xqvwFFIOgx-ptDDZFm0f3TgDPG8UPNA8LWPuJh_EleOA_S3L2gcPJUlkUI1qwG2J9O-0U1PtMdfSClMFdQ5yMoJrCWlCrOKVX9T5kbh5GtY3eol-lfSHMFUeCM9waSyNLWV3UybqwI_6nb-KqEPZ0zAO8-AVbC-FAExOzgFUuConrazYkJ4ycevu0c4PaCayftcDLTxn3QBP2xR09xHxwW7EF3h37607x2EXIBP4p_qZmO6ma1LSDPFcbC1mnIA2Uy14zZK4wEhzBZICx44txy9ZIi8um4iyCZxlwZGzD8lMtp0DF-1WUQJEY-uXhTsjoyEXBgiwKsx9jId-dsyDNxNphet7FELx9jjf7Q2EoGdkwvLT5Zg9hXl2R_a4-n8JUsFTRQHiTsqbzOxdOxXgAQxpjYzBq1lo4GsIFhQ6gg-p3HbdNkK6Pq5MpPq
244 ms
channel.html
97 ms
sdk.js
65 ms
m-outer-15a2b40a058ddff1cffdb63779fe3de1.js
76 ms
woff.css
80 ms
inner.html
24 ms
woff.css
95 ms
woff.css
64 ms
AAJ42mNgYGBkAIIbu27xgugHjLZ7ofQBAEdjBjQA
1 ms
woff.css
13 ms
woff.css
68 ms
AAJ42mNgYGBkAIIbu27xguiH5wO1obQRAE33BtoA
2 ms
print.css
94 ms
woff.css
11 ms
woff.css
32 ms
AAJ42mNgYGBkAIIbu27xguiH5+UPQulTAFF9B6QA
1 ms
lacantine.ae 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
[aria-*] attributes do not match their roles
ARIA IDs are not unique
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lacantine.ae 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lacantine.ae 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lacantine.ae 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 Lacantine.ae 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.
lacantine.ae
Open Graph description is not detected on the main page of La Cantine. 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: