5.9 sec in total
1 sec
4.4 sec
441 ms
Visit martintxo.com now to see the best up-to-date Martintxo content and also check out these interesting facts you probably never knew about martintxo.com
® Dos conceptos de restaurante: ASADOR y SIDRERÍA. Chuletón a la parrilla, lechales asados, verduras frescas y pescados-mariscos de máxima calidad en Pamplona.
Visit martintxo.comWe analyzed Martintxo.com page load time and found that the first response time was 1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
martintxo.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value13.5 s
0/100
25%
Value12.2 s
3/100
10%
Value970 ms
28/100
30%
Value1.178
1/100
15%
Value16.8 s
5/100
10%
1011 ms
1617 ms
327 ms
217 ms
47 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 66% of them (45 requests) were addressed to the original Martintxo.com, 26% (18 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Martintxo.com.
Page size can be reduced by 1.0 MB (42%)
2.5 MB
1.4 MB
In fact, the total size of Martintxo.com main page is 2.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. 70% of websites need less resources to load. Images take 941.2 kB which makes up the majority of the site volume.
Potential reduce by 258.8 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 258.8 kB or 85% of the original size.
Potential reduce by 226 B
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. Martintxo images are well optimized though.
Potential reduce by 483.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 483.5 kB or 55% of the original size.
Potential reduce by 286.8 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. Martintxo.com needs all CSS files to be minified and compressed as it can save up to 286.8 kB or 86% of the original size.
Number of requests can be reduced by 34 (76%)
45
11
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Martintxo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
martintxo.com
1011 ms
martintxo.com
1617 ms
styles.css
327 ms
style.min.css
217 ms
css
47 ms
style.min.css
127 ms
carousel.min.css
244 ms
style.css
329 ms
ctc-style.css
324 ms
jquery.min.js
434 ms
jquery-migrate.min.js
343 ms
masonry.min.js
356 ms
divi-filter-loadmore.min.js
359 ms
js
68 ms
mediaelementplayer-legacy.min.css
427 ms
wp-mediaelement.min.css
431 ms
index.js
452 ms
index.js
467 ms
scripts.min.js
583 ms
es6-promise.auto.min.js
545 ms
api.js
47 ms
recaptcha.js
550 ms
jquery.fitvids.js
542 ms
frontend-bundle.min.js
566 ms
frontend-bundle.min.js
582 ms
common.js
657 ms
api.js
68 ms
regenerator-runtime.min.js
653 ms
wp-polyfill.min.js
661 ms
index.js
683 ms
carousel.min.js
920 ms
frontend-general.min.js
698 ms
mediaelement-and-player.min.js
1086 ms
mediaelement-migrate.min.js
765 ms
wp-mediaelement.min.js
770 ms
style.css
479 ms
logo_asador_martintxo_NUEVO.png
116 ms
preloader.gif
117 ms
Martintxo-instalaciones0023.jpg
221 ms
captura_video.jpg
345 ms
captura_video4.jpg
639 ms
chuleton-chuleta-pamplona.jpg
230 ms
17W3964_sel_2.jpg
234 ms
17W3821_ok.jpg
333 ms
17W3775.jpg
504 ms
et-divi-dynamic-7-late.css
301 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
23 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
30 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
47 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
55 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
65 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9aX8.ttf
68 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aX8.ttf
68 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9aX8.ttf
68 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9aX8.ttf
68 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8aX8.ttf
68 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6aX8.ttf
75 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6aX8.ttf
76 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6aX8.ttf
74 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16aX8.ttf
74 ms
modules.woff
290 ms
recaptcha__en.js
34 ms
style.min.css
121 ms
modules.woff
132 ms
martintxo.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
Links do not have a discernible name
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.
martintxo.com 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
Issues were logged in the Issues panel in Chrome Devtools
martintxo.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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Martintxo.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 Martintxo.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.
martintxo.com
Open Graph data is detected on the main page of Martintxo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: