5.5 sec in total
501 ms
4.4 sec
636 ms
Visit comarch.es now to see the best up-to-date Comarch content and also check out these interesting facts you probably never knew about comarch.es
Comarch es fabricante de soluciones informáticas e integrador. Desde 1993, Comarch ayuda a clientes a lograr una mayor rentabilidad y sacar provecho de las soluciones y productos modernos, usando una ...
Visit comarch.esWe analyzed Comarch.es page load time and found that the first response time was 501 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
comarch.es performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value15.3 s
0/100
25%
Value8.8 s
16/100
10%
Value2,040 ms
7/100
30%
Value0
100/100
15%
Value14.1 s
10/100
10%
501 ms
523 ms
1340 ms
522 ms
58 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 78% of them (42 requests) were addressed to the original Comarch.es, 6% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Comarch.es.
Page size can be reduced by 97.6 kB (12%)
794.7 kB
697.1 kB
In fact, the total size of Comarch.es main page is 794.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 544.0 kB which makes up the majority of the site volume.
Potential reduce by 92.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 92.6 kB or 86% of the original size.
Potential reduce by 4.6 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, Comarch needs image optimization as it can save up to 4.6 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 239 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 132 B
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. Comarch.es has all CSS files already compressed.
Number of requests can be reduced by 32 (76%)
42
10
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Comarch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
comarch.es
501 ms
comarch.es
523 ms
www.comarch.es
1340 ms
prod.styles.css
522 ms
js
58 ms
loading.scripts.js
848 ms
cookieInfo-1.9.9.min.js
696 ms
prod.scripts.js
1202 ms
double-click.js
387 ms
ga.js
388 ms
google-maps.js
606 ms
utm.js
606 ms
analytics.js
149 ms
gtm.js
149 ms
comarch_logo.svg
430 ms
clm.jpg
432 ms
1920x640_FutureConnections23.21x21.aed741de.jpg
432 ms
1920x640_slider_Predictions_2024.21x21.a21ae1c4.jpg
433 ms
loyalty-in-retail.21x21.8cd4df5d.jpg
433 ms
ai_ml_wp.21x21.3816eae9.jpg
444 ms
esef-es-informes-1920x640.21x21.4eedece8.jpg
446 ms
baner_1920x400_a2.21x21.622f0de5.jpg
446 ms
bp.21x21.c81a381b.png
464 ms
jetblue.21x21.ca4f9a5a.png
481 ms
grupo_tvcable.21x21.ef0e4cfe.png
500 ms
puntos.21x21.7ed3982b.png
502 ms
255x150_Telefonica_new.21x21.b052254b.jpg
505 ms
heathrow.21x21.e78a641a.png
594 ms
metro-digital.21x21.a1e5eb4f.png
613 ms
255x150_Vodafone.21x21.a9d1c3cc.png
631 ms
lead-content__background-6.21x21.3ae311e6.jpg
637 ms
736x440_Gartner1023.21x21.29d5ebc6.jpg
637 ms
736x440_Gartner202023.21x21.81df43d7.jpg
724 ms
736x440_Gartner2023.21x21.378e406b.jpg
742 ms
comarch-logo-black.svg
761 ms
64 ms
roboto-regular.woff
784 ms
roboto-medium.woff
916 ms
roboto-bold.woff
727 ms
interface-icon.woff
747 ms
roboto-regular_italic.woff
888 ms
roboto-medium_italic.woff
914 ms
roboto-bold_italic.woff
858 ms
CA-font.woff
1256 ms
collect
19 ms
collect
33 ms
js
52 ms
28 ms
ga-audiences
19 ms
mtc.js
1035 ms
insight.min.js
61 ms
translate_2.json
601 ms
li_sync
24 ms
print.css
132 ms
comarch.es accessibility score
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
button, link, and menuitem elements do not have accessible names.
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
comarch.es 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
comarch.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Comarch.es 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 Comarch.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.
comarch.es
Open Graph description is not detected on the main page of Comarch. 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: