3 sec in total
31 ms
1.9 sec
1.1 sec
Visit cancun-indy.com now to see the best up-to-date Cancun Indy content and also check out these interesting facts you probably never knew about cancun-indy.com
Locally family owned and operated, Cancun Mexican Restaurant has TWO Indy locations to serve you! Call about our Catering Service today at (317) 695-2352.
Visit cancun-indy.comWe analyzed Cancun-indy.com page load time and found that the first response time was 31 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
cancun-indy.com performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value6.8 s
7/100
25%
Value14.9 s
1/100
10%
Value410 ms
67/100
30%
Value0.042
99/100
15%
Value26.2 s
0/100
10%
31 ms
895 ms
60 ms
91 ms
237 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 60% of them (50 requests) were addressed to the original Cancun-indy.com, 29% (24 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Fbgcdn.com. The less responsive or slowest element that took the longest time to load (895 ms) belongs to the original domain Cancun-indy.com.
Page size can be reduced by 294.5 kB (3%)
8.6 MB
8.3 MB
In fact, the total size of Cancun-indy.com main page is 8.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.0 MB which makes up the majority of the site volume.
Potential reduce by 176.2 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 176.2 kB or 83% of the original size.
Potential reduce by 56.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. Cancun Indy images are well optimized though.
Potential reduce by 59.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 59.0 kB or 16% of the original size.
Potential reduce by 3.0 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. Cancun-indy.com has all CSS files already compressed.
Number of requests can be reduced by 42 (74%)
57
15
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cancun Indy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
cancun-indy.com
31 ms
cancun-indy.com
895 ms
main.min.css
60 ms
order-online.css
91 ms
dflip.min.css
237 ms
frontend-lite.min.css
241 ms
swiper.min.css
235 ms
post-6.css
234 ms
frontend-lite.min.css
239 ms
global.css
112 ms
post-7.css
169 ms
post-28.css
225 ms
css
33 ms
public-style.css
281 ms
ewm2.js
174 ms
jquery.min.js
348 ms
jquery-migrate.min.js
291 ms
widget-icon-list.min.css
291 ms
widget-nav-menu.min.css
292 ms
ewm2.js
97 ms
widget-carousel.min.css
292 ms
e-gallery.min.css
333 ms
animations.min.css
404 ms
frontend.min.js
404 ms
dflip.min.js
531 ms
public-scripts.js
405 ms
jquery.smartmenus.min.js
405 ms
imagesloaded.min.js
405 ms
e-gallery.min.js
406 ms
webpack-pro.runtime.min.js
405 ms
webpack.runtime.min.js
474 ms
frontend-modules.min.js
530 ms
wp-polyfill-inert.min.js
529 ms
regenerator-runtime.min.js
528 ms
wp-polyfill.min.js
556 ms
hooks.min.js
528 ms
i18n.min.js
593 ms
frontend.min.js
592 ms
waypoints.min.js
594 ms
core.min.js
592 ms
frontend.min.js
593 ms
elements-handlers.min.js
618 ms
jquery.sticky.min.js
596 ms
cancun-logo-1-2.png
299 ms
1702671490534.png
278 ms
Cancun.png
267 ms
1696891971854.jpg
270 ms
1696892736807.jpg
276 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
169 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
172 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
171 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
171 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
171 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
171 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxCZCITlqm5.ttf
313 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxCTSITlqm5.ttf
451 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxCKiITlqm5.ttf
220 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxCEyITlqm5.ttf
374 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxC_yUTlqm5.ttf
187 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxCzSUTlqm5.ttf
431 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxCkyUTlqm5.ttf
317 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxCTSUTlqm5.ttf
374 ms
V8mjoR7-XjwJ8_Au3Ti5tXj5Rd83frpWLK4d-taxqWw2HMWjDxBAg5S_0QsrggxCzSQTlqm5.ttf
480 ms
1696977703653.jpg
249 ms
o.jpg
247 ms
shutterstock_2328403777.jpg
248 ms
rawpixel-645297-unsplash.jpg
250 ms
Birthday-Campaign-1.png
280 ms
98130109_2599049817023874_4963511116337512448_n.jpg
277 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf
229 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rm.ttf
233 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf
234 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISmb2Rm.ttf
234 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rm.ttf
235 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf
256 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf
257 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOmb2Rm.ttf
257 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rm.ttf
259 ms
embed
315 ms
order-online.css
90 ms
sp.js
31 ms
i
169 ms
js
49 ms
cancun-indy.com 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.
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
cancun-indy.com 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
Issues were logged in the Issues panel in Chrome Devtools
cancun-indy.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cancun-indy.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 Cancun-indy.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.
cancun-indy.com
Open Graph description is not detected on the main page of Cancun Indy. 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: