12.1 sec in total
2.5 sec
9.1 sec
487 ms
Visit merkopolis.com now to see the best up-to-date Merkopolis content and also check out these interesting facts you probably never knew about merkopolis.com
Plataforma de apoyo al pequeño comercio
Visit merkopolis.comWe analyzed Merkopolis.com page load time and found that the first response time was 2.5 sec and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
merkopolis.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value7.0 s
6/100
25%
Value13.1 s
2/100
10%
Value1,910 ms
8/100
30%
Value0.069
96/100
15%
Value15.4 s
7/100
10%
2500 ms
425 ms
10 ms
16 ms
277 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 85% of them (63 requests) were addressed to the original Merkopolis.com, 8% (6 requests) were made to Maps.google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Merkopolis.com.
Page size can be reduced by 1.7 MB (69%)
2.4 MB
745.7 kB
In fact, the total size of Merkopolis.com main page is 2.4 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. 50% of websites need less resources to load. HTML takes 1.8 MB which makes up the majority of the site volume.
Potential reduce by 1.4 MB
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 1.4 MB or 81% of the original size.
Potential reduce by 33.0 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, Merkopolis needs image optimization as it can save up to 33.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 216.5 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 216.5 kB or 62% of the original size.
Number of requests can be reduced by 24 (33%)
73
49
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Merkopolis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
merkopolis.com
2500 ms
merkopolis.css
425 ms
jquery.min.js
10 ms
jquery-ui.js
16 ms
tooltip.js
277 ms
functions.js
271 ms
jquery.cookie.js
280 ms
anythingslider.css
208 ms
jquery.anythingslider.js
386 ms
jquery.anythingslider.video.js
391 ms
tabla_precios.css
208 ms
js
37 ms
bg-body.gif
106 ms
bg-header-top.png
258 ms
arrow-down.png
106 ms
bg-header.png
102 ms
bg-mk.png
298 ms
logo-merkopolis.png
302 ms
icono-phone-24.png
1123 ms
btn-menu-bg.png
256 ms
btn-menu-publicar-bg.png
257 ms
100-premios-es.png
310 ms
bg-wrapper-home.png
311 ms
bg-top-home.jpg
456 ms
btn-merkobonos-main.png
390 ms
bg-slider.png
399 ms
home-merkobono-slider.jpg
611 ms
home-pagina-slider.jpg
411 ms
home-campania-slider.jpg
677 ms
timthumb.php
616 ms
timthumb.php
1716 ms
timthumb.php
673 ms
timthumb.php
730 ms
timthumb.php
1837 ms
merkobonos-icos.png
775 ms
tick-mark.png
773 ms
filtro-merkobonos.js
101 ms
museo_slab_700-webfont.woff
902 ms
museo700-regular-webfont.woff
931 ms
bullet-list.png
736 ms
sep-featured-footer.png
849 ms
featured-footer-1.png
896 ms
featured-footer-2.png
921 ms
featured-footer-4.png
945 ms
bg-footer.png
998 ms
btn-iphone-es.png
1018 ms
btn-android-es.png
1047 ms
sep-footer.png
1074 ms
logo-footer.png
1102 ms
arrow-top.png
1115 ms
overlay.png
1149 ms
ga.js
82 ms
busquedas_merkobonos_resul.php
1371 ms
cats-select-merkobono.php
2535 ms
cats-container-merkobono.php
2458 ms
zona-select-merkobono.php
6065 ms
__utm.gif
13 ms
zona-container-merkobono.php
1650 ms
idioma-select-merkobono.php
2016 ms
museo300-regular-webfont.woff
1731 ms
bolitas-slider.png
1746 ms
ribbon-new-es.png
1751 ms
slider-home-left.png
1754 ms
slider-home-right.png
1829 ms
bg-tabs.png
1797 ms
tab-normal.png
1731 ms
tab-active.png
1739 ms
common.js
4 ms
util.js
24 ms
stats.js
23 ms
AuthenticationService.Authenticate
56 ms
shetland.css
111 ms
map.js
41 ms
marker.js
39 ms
merkopolis.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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>).
merkopolis.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
Detected JavaScript libraries
Browser errors were logged to the console
merkopolis.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
ES
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Merkopolis.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 Merkopolis.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
merkopolis.com
Open Graph description is not detected on the main page of Merkopolis. 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: