4.4 sec in total
111 ms
3.1 sec
1.2 sec
Welcome to abecargo.com homepage info - get ready to check Abecargo best content for Colombia right away, or after learning these important things about abecargo.com
¡En ABE Cargo hacemos más fácil SU VIDA! Crea tu casillero en USA totalmente gratis y disfruta de todos los beneficios y descuentos.
Visit abecargo.comWe analyzed Abecargo.com page load time and found that the first response time was 111 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
abecargo.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value13.7 s
0/100
25%
Value20.7 s
0/100
10%
Value4,100 ms
1/100
30%
Value0.12
84/100
15%
Value16.9 s
5/100
10%
111 ms
81 ms
85 ms
47 ms
53 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Abecargo.com, 38% (53 requests) were made to Static.wixstatic.com and 32% (44 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (932 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 3.1 MB (47%)
6.5 MB
3.4 MB
In fact, the total size of Abecargo.com main page is 6.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. 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. Javascripts take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 256.1 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 256.1 kB or 86% of the original size.
Potential reduce by 217.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. Abecargo images are well optimized though.
Potential reduce by 2.5 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 2.5 MB or 75% of the original size.
Potential reduce by 152.2 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. Abecargo.com needs all CSS files to be minified and compressed as it can save up to 152.2 kB or 89% of the original size.
Number of requests can be reduced by 72 (58%)
125
53
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Abecargo. 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 10 to 1 for CSS and as a result speed up the page load time.
abecargo.com
111 ms
www.abecargo.com
81 ms
bt
85 ms
require.min.js
47 ms
main-r.min.js
53 ms
viewer.css
51 ms
dynamicmodel
21 ms
ebe118_ab077b60a25d0ee4ce28c9fd9d3a91d0_604.json.z
429 ms
ebe118_93501b6fa80a04776b473a812283ebf0_603.json.z
470 ms
ugc-viewer
83 ms
bt
268 ms
skins.min.js
83 ms
components.min.js
78 ms
utils.min.js
79 ms
core.min.js
77 ms
react-with-addons.min.js
48 ms
lodash.min.js
28 ms
TweenMax.min.js
79 ms
layout.min.js
81 ms
tpa.min.js
79 ms
fonts.min.js
79 ms
animations.min.js
80 ms
swfobject.min.js
81 ms
mousetrap.min.js
80 ms
tweenEngine.min.js
80 ms
DrawSVGPlugin.min.js
255 ms
react-dom.min.js
80 ms
ScrollToPlugin.min.js
256 ms
widgets.min.js
255 ms
experiment.js
255 ms
wixappsCore.min.js
256 ms
wixappsClassics.min.js
258 ms
wixappsBuilder.min.js
255 ms
zepto.min.js
254 ms
color.min.js
254 ms
react-dom-server.min.js
259 ms
bt
128 ms
dc.js
30 ms
bt
631 ms
liftedshadow_medium.png
263 ms
css
258 ms
latin.css
246 ms
StripShowcase.html
248 ms
hitcounter.galilcloud.wixapps.net
269 ms
ebe118_f1cb3bb564c11ce72871c446d2924d24.html
308 ms
wix.mailchimpapp.com
323 ms
__utm.gif
244 ms
ebe118_396989ee4cbb4cbabcc71279366722f0.png
448 ms
ebe118_9d46a34dc58249f48ae9ba20e7c2bfb9.jpg
449 ms
ebe118_d4256dcf352845f18a5b09c079d4d4e9.png
578 ms
ebe118_77591e2fe4fa40ce9e50d6fc79db703a.png
578 ms
ebe118_b059ed6606b647b7a6eeac84230ffae6.jpg
577 ms
ebe118_217baddd84ac4e3ea2d7d658c6043956.jpg
549 ms
ebe118_fcd7f7c7e09d4ffbb9f56b1a95724f97.jpg
606 ms
ebe118_b7761bbcfc444f89a2f6d769f73f8c1a.jpg
605 ms
ebe118_a8852b97a55e4141a6cacf971d61072b.jpg
681 ms
c9e29ce982c7146d2600e39f8bcb4922.jpg
679 ms
ebe118_8b46c9d46bbc4b94a56e4c8b445d73ef.png
680 ms
ebe118_975b1f87fbe140d7b9da70f8f05596bd.png
679 ms
ebe118_e6276491abfd49849366936bdd95f2b7.jpg
679 ms
ebe118_832b2966df314791a9a901feaa13ae0b.png
679 ms
ebe118_189a76c000d24c1db1c955eaff8bff01.png
726 ms
ebe118_ad1387d75d1147b799b672a5d2d3709d.png
713 ms
ebe118_0dadb51f7ec24251a8c38aeaddd1024d.png
714 ms
ebe118_f1b11aed07ab4a11aab66175909a657b.png
713 ms
0fdef751204647a3bbd7eaa2827ed4f9.png
679 ms
c7d035ba85f6486680c2facedecdcf4d.png
680 ms
04b15d1b030049d1b3746f8ef5a72955.png
724 ms
45bce1d726f64f1999c49feae57f6298.png
725 ms
ebe118_fc219fced8b44b62ba6cadaf684e9385.jpg
797 ms
e0678ef25486466ba65ef6ad47b559e1.png
793 ms
c4392d634a0148fda8b7b2b0ad98293b.png
791 ms
6cc776af25744f77ab9c420b98d1abe6.png
794 ms
203dcdc2ac8b48de89313f90d2a4cda1.png
794 ms
ebe118_f925900c0ad645f686915bfefaa86019.png
797 ms
ebe118_ae2635c734004893ac868c32996f4071.png
826 ms
ebe118_3832b25c01b347599c0c6dfa398ed94f.png
822 ms
ebe118_efb9eb0cf6f04d849164ddbc4fced812.png
824 ms
ebe118_c6d62c86a2914bcc9c30194decf9ab9e.png
823 ms
ebe118_89c47efa5d9f44939dc181f41e04b14a.png
825 ms
ebe118_8b46c9d46bbc4b94a56e4c8b445d73ef.png
846 ms
ebe118_aa68cf7e80d84cb0ab377aa4c1929e81.png
846 ms
bt
144 ms
bt
145 ms
bt
145 ms
shiny2button_bg.png
89 ms
indented_bg.png
99 ms
shiny1button_bg.png
91 ms
ebe118_c2e99343f2514ad99c8c5df8f2d30295.png
863 ms
jquery.min.js
79 ms
jquery.easing-1.3.min.js
66 ms
lodash.min.js
75 ms
Wix.js
769 ms
style.min.css
413 ms
app.min.js
430 ms
page.css
57 ms
animations.css
58 ms
animate.css
60 ms
jquery.min.js
93 ms
wix.min.js
537 ms
jquery.cookie.js
62 ms
lib.js
64 ms
ready.js
65 ms
model.js
64 ms
wix.min.js
846 ms
jquery.min.js
494 ms
styles.css
389 ms
PeTTkHQKj5rUPVxkIGAoaw.ttf
398 ms
j7wx-rRiDuE-JcaZ1ilpKg.ttf
447 ms
5t8vP9Hx2udzw372glmOxA.ttf
478 ms
opensans-bold-webfont.woff
340 ms
opensans-regular-webfont.woff
339 ms
qSdzwh2A4BbNemy78sJLfOSB4-q0KehLImxSVNaiVBQ.ttf
520 ms
c81cca03-5f1a-4252-9950-096e60e2bde9.woff
324 ms
ugc-viewer
54 ms
ebe118_9a9853fe22954f13a5098d6efb401f90.jpg
410 ms
ebe118_d006d6e4f27a494cb03e6353a6aab0d2f000.jpg
403 ms
ebe118_70822b199ed3486ca4d06818d6f9ffba.jpg
298 ms
11062b_240ceadfce144953be3b55434db78e92f000.jpg
278 ms
8d13be_b7d82884c9714afc8b3da5ae4309fd9a.jpg
278 ms
116 ms
nr-852.min.js
108 ms
ebe118_d006d6e4f27a494cb03e6353a6aab0d2f000.jpg
572 ms
ebe118_70822b199ed3486ca4d06818d6f9ffba.jpg
426 ms
css
41 ms
ebe118_9a9853fe22954f13a5098d6efb401f90.jpg
333 ms
11062b_240ceadfce144953be3b55434db78e92f000.jpg
391 ms
8d13be_b7d82884c9714afc8b3da5ae4309fd9a.jpg
932 ms
preloader.GIF
73 ms
7800adffd0
94 ms
css
119 ms
arrow-left.png
39 ms
ebe118_5e572bda66504c3cb25613f7044bc2ce.png
123 ms
ebe118_dcda31346c894081abf69e00efcc8c99.png
175 ms
ebe118_d0c4eef821ec4b5187182e829020cf72.png
188 ms
ebe118_47cd4fe840aa4fe0b06acd10bd22680a.png
190 ms
ebe118_e124b88a12904535812e2fdf4ad8f175.png
273 ms
arrow-right.png
25 ms
abecargo.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.
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
Links do not have a discernible name
abecargo.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
abecargo.com 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
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Abecargo.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Abecargo.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.
abecargo.com
Open Graph description is not detected on the main page of Abecargo. 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: