2.4 sec in total
123 ms
2 sec
233 ms
Welcome to mayca.com homepage info - get ready to check Mayca best content for Costa Rica right away, or after learning these important things about mayca.com
Homepage - Mayca Food Service
Visit mayca.comWe analyzed Mayca.com page load time and found that the first response time was 123 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
mayca.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value12.3 s
0/100
25%
Value7.2 s
30/100
10%
Value1,050 ms
26/100
30%
Value0.18
68/100
15%
Value12.7 s
14/100
10%
123 ms
786 ms
45 ms
46 ms
46 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 99% of them (72 requests) were addressed to the original Mayca.com, 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (786 ms) belongs to the original domain Mayca.com.
Page size can be reduced by 863.2 kB (46%)
1.9 MB
1.0 MB
In fact, the total size of Mayca.com main page is 1.9 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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 33.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.7 kB or 82% of the original size.
Potential reduce by 397.7 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. Obviously, Mayca needs image optimization as it can save up to 397.7 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 318.9 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 318.9 kB or 70% of the original size.
Potential reduce by 112.9 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. Mayca.com needs all CSS files to be minified and compressed as it can save up to 112.9 kB or 83% of the original size.
Number of requests can be reduced by 50 (71%)
70
20
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mayca. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
mayca.com
123 ms
786 ms
system.css
45 ms
general.css
46 ms
template.css
46 ms
green.css
46 ms
module_default.css
49 ms
style.css
68 ms
vmsite-ltr.css
107 ms
template.css.php
123 ms
cssOTmegaMenu.css
87 ms
mootools-core.js
151 ms
core.js
88 ms
caption.js
109 ms
mootools-more.js
256 ms
dropdownMenu.js
130 ms
otscript.js
149 ms
acymailing_module.js
153 ms
jquery.min.js
227 ms
jquery.noConflict.js
172 ms
jquery.min.js
25 ms
jquery.fpss.js
188 ms
jsOTmegaMenu.js
188 ms
system.css
156 ms
reset.css
174 ms
editor.css
193 ms
joomla.css
192 ms
layout.css
218 ms
dropdownMenu.css
217 ms
typography.css
229 ms
customs.css
255 ms
customs.thumb.productdetails.css
235 ms
virtuemart.css
276 ms
headertop-bg.png
67 ms
header-bg.png
43 ms
logo.png
87 ms
top-partner.png
106 ms
mainmenu-top-leftbg.png
50 ms
mainmenu-top-midbg.png
52 ms
mainmenu-border-item.png
52 ms
search-bg.png
85 ms
search-submitbg.png
84 ms
mainmenu-top-rightbg.png
86 ms
megamenu-leftbg.png
85 ms
megamenu-midbg.png
128 ms
submegamenu-bottombg.png
128 ms
submegamenu-rightbg.png
130 ms
menu-borderbg.png
130 ms
submenu-rightbg.png
132 ms
megamenu-rightbg.png
146 ms
loading_black.gif
168 ms
9_d61d44254608dd06ccdd2ff02982d14d_m.jpg
209 ms
10_e31ace2a15a7c70645ad83df9ecd43b0_m.jpg
286 ms
12_3899dfe821816fbcb3db3e3b23f81585_m.jpg
246 ms
13_48ee1e8a0a8f50dce4f8cb9ab418e211_m.jpg
306 ms
14_fd8b0f77d767f1f6640afba6916ff67c_m.jpg
316 ms
arrow.png
215 ms
nav-left.png
564 ms
nav-right.png
314 ms
arrow.png
336 ms
conservas_400x300.jpg
387 ms
arrow-red.png
356 ms
frijoles_400x300.jpg
378 ms
garbanzos_400x300.jpg
419 ms
bottom-extend-bg.png
398 ms
letter.png
462 ms
bottomboxes-bg.png
428 ms
bottomboxes-midbg.png
544 ms
sysco_mayca.png
460 ms
Oswald.ttf
511 ms
bottom-list-spacer.png
465 ms
bottom-pic.png
587 ms
payment-verified.png
546 ms
mayca.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.
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 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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
mayca.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
mayca.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Mayca.com 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 Mayca.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.
mayca.com
Open Graph description is not detected on the main page of Mayca. 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: