6.9 sec in total
1.1 sec
5.5 sec
303 ms
Click here to check amazing MTP content for Spain. Otherwise, check out these important facts you probably never knew about mtp.es
Aseguramiento de la calidad QA, Experiencia de usuario UX, Ciberseguridad, devOps y Formación. Más de 23 años de historia nos respaldan.
Visit mtp.esWe analyzed Mtp.es page load time and found that the first response time was 1.1 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mtp.es performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value16.8 s
0/100
25%
Value13.1 s
2/100
10%
Value9,210 ms
0/100
30%
Value0.005
100/100
15%
Value23.1 s
1/100
10%
1083 ms
233 ms
228 ms
231 ms
231 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 86% of them (115 requests) were addressed to the original Mtp.es, 5% (7 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Mtp.es.
Page size can be reduced by 1.6 MB (54%)
2.9 MB
1.3 MB
In fact, the total size of Mtp.es main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 49.6 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 49.6 kB or 81% of the original size.
Potential reduce by 63.9 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. MTP images are well optimized though.
Potential reduce by 721.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 721.9 kB or 71% of the original size.
Potential reduce by 756.6 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. Mtp.es needs all CSS files to be minified and compressed as it can save up to 756.6 kB or 86% of the original size.
Number of requests can be reduced by 59 (72%)
82
23
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MTP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
mtp.es
1083 ms
k2.css
233 ms
font-awesome.min.css
228 ms
animate.min.css
231 ms
sppagebuilder.css
231 ms
settings.css
231 ms
dynamic-captions.css
337 ms
static-captions.css
342 ms
owl.carousel.css
344 ms
owl.theme.css
344 ms
css
38 ms
bootstrap.min.css
344 ms
font-awesome.min.css
345 ms
legacy.css
451 ms
template.css
455 ms
modal.css
564 ms
dropdown_css3.css
569 ms
mootools-core.js
575 ms
core.js
578 ms
jquery.min.js
578 ms
jquery-noconflict.js
578 ms
jquery-migrate.min.js
675 ms
k2.js
680 ms
jquery.themepunch.tools.min.js
688 ms
jquery.themepunch.revolution.min.js
693 ms
owl.carousel.js
689 ms
sppagebuilder.js
692 ms
bootstrap.min.js
789 ms
jquery.sticky.js
794 ms
main.js
801 ms
jquery.nav.js
802 ms
jquery.countdown.js
807 ms
jquery.blueimp-gallery.min.js
804 ms
css
65 ms
mtp.css
691 ms
font-awesome.min.css
854 ms
sppagebuilder.css
1005 ms
animate.min.css
1077 ms
settings.css
971 ms
k2.css
962 ms
dynamic-captions.css
639 ms
static-captions.css
746 ms
owl.theme.css
858 ms
owl.carousel.css
863 ms
bootstrap.min.css
1188 ms
font-awesome.min.css
1076 ms
legacy.css
865 ms
template.css
1536 ms
blueimp-gallery.min.css
887 ms
jbcookies.css
961 ms
preset1.css
966 ms
bootstrap-image-gallery.min.css
999 ms
modal.css
976 ms
dropdown_css3.css
972 ms
mootools-core.js
1190 ms
core.js
999 ms
jquery.min.js
1180 ms
jquery-noconflict.js
1071 ms
jquery-migrate.min.js
975 ms
k2.js
1009 ms
jquery.themepunch.tools.min.js
1187 ms
owl.carousel.js
1186 ms
jquery.themepunch.revolution.min.js
1381 ms
sppagebuilder.js
1291 ms
bootstrap.min.js
1089 ms
jquery.sticky.js
1221 ms
main.js
1215 ms
jquery.nav.js
1213 ms
jquery.blueimp-gallery.min.js
1296 ms
jquery.countdown.js
1296 ms
mtp.css
1202 ms
bootstrap-image-gallery.min.js
118 ms
mootools-more.js
120 ms
modal.js
120 ms
dropdown.js
122 ms
bootstrap-image-gallery.min.js
1021 ms
mootools-more.js
1357 ms
modal.js
1058 ms
dropdown.js
1124 ms
css
15 ms
css
25 ms
css
29 ms
analytics.js
70 ms
banner3.png
267 ms
home-aboutus-2.png
382 ms
qa-full.png
851 ms
cx-full.png
846 ms
cs-full.png
846 ms
ap-full.png
845 ms
bs-full.png
844 ms
fondo1.png
329 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
63 ms
DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff
63 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
64 ms
EInbV5DfGHOiMmvb1Xr-hqRDOzjiPcYnFooOUGCOsRk.woff
64 ms
fontawesome-webfont.woff
377 ms
fontawesome-webfont.woff
394 ms
bH7276GfdCjMjApa_dkG6bO3LdcAZYWl9Si6vvxL-qU.woff
214 ms
qpy-UiLNKP-VfOdbcs6r6-vvDin1pK8aKteLpeZ5c0A.woff
252 ms
HqHm7BVC_nzzTui2lzQTDbO3LdcAZYWl9Si6vvxL-qU.woff
250 ms
index.php
297 ms
collect
156 ms
twitter.png
153 ms
linkedin.png
154 ms
youtube.png
153 ms
banner2.png
574 ms
banner1b.png
686 ms
logo.png
127 ms
banner4.png
572 ms
logo-mtp-mobile.png
239 ms
loader.gif
286 ms
coloredbg.png
287 ms
bullet.png
353 ms
large_left.png
403 ms
large_right.png
402 ms
banner3.png
913 ms
home-aboutus-2.png
514 ms
index.php
827 ms
k2.css
119 ms
mootools-core.js
340 ms
core.js
127 ms
jquery.min.js
229 ms
jquery-noconflict.js
131 ms
jquery-migrate.min.js
131 ms
k2.js
228 ms
bootstrap.min.js
230 ms
jq.min.js
383 ms
system.css
238 ms
bootstrap.min.css
452 ms
frontend-edit.css
362 ms
template.css
792 ms
facileforms.js
363 ms
iframe.css
447 ms
IcoMoon.woff
118 ms
mtp.es accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
mtp.es 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
mtp.es 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
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 Mtp.es 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 Mtp.es 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.
mtp.es
Open Graph description is not detected on the main page of MTP. 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: