3.2 sec in total
403 ms
2.7 sec
120 ms
Visit marlex.net now to see the best up-to-date Marlex content for Spain and also check out these interesting facts you probably never knew about marlex.net
Acercamos el talento a las empresas. Publicamos nuevas ofertas de trabajo cada día y seleccionamos los mejores profesionales para nuestros clientes.
Visit marlex.netWe analyzed Marlex.net page load time and found that the first response time was 403 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
marlex.net performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value8.0 s
2/100
25%
Value7.2 s
30/100
10%
Value4,840 ms
0/100
30%
Value0.459
19/100
15%
Value14.2 s
9/100
10%
403 ms
113 ms
212 ms
333 ms
232 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 84% of them (38 requests) were addressed to the original Marlex.net, 9% (4 requests) were made to Click.cat and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Marlex.net.
Page size can be reduced by 168.4 kB (61%)
276.4 kB
108.0 kB
In fact, the total size of Marlex.net main page is 276.4 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. 30% of websites need less resources to load. Javascripts take 181.4 kB which makes up the majority of the site volume.
Potential reduce by 10.7 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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 10.7 kB or 73% of the original size.
Potential reduce by 15.5 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, Marlex needs image optimization as it can save up to 15.5 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 119.8 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 119.8 kB or 66% of the original size.
Potential reduce by 22.4 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. Marlex.net needs all CSS files to be minified and compressed as it can save up to 22.4 kB or 86% of the original size.
Number of requests can be reduced by 16 (39%)
41
25
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marlex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
marlex.net
403 ms
reseter.css
113 ms
lib.css
212 ms
jquery-2.1.1.min.js
333 ms
bootstrap.js
232 ms
_lib.js
228 ms
detect-mobile-desktop.js
328 ms
module_00.php
226 ms
interficie.php
120 ms
helpers.php
109 ms
tipografies.php
128 ms
alertes.js
118 ms
jquery.cookie.js
113 ms
detectarBrowser.js
115 ms
acceptar_cookies.js
112 ms
cookie-html.js
110 ms
bgWeb.gif
445 ms
logo.gif
128 ms
ett.png
126 ms
sel.png
127 ms
arrow-grey.png
127 ms
arrow-orange.png
126 ms
eurogrup_btn.png
235 ms
marlex_btn.png
238 ms
dosier-corporatiu-btn.gif
236 ms
xarxa-oficines.gif
230 ms
con-icon.png
231 ms
fil.png
337 ms
gtg.png
334 ms
cfm.png
343 ms
dosier-corporatiu.png
345 ms
good-to-great.png
353 ms
treballa-a-marlex.png
439 ms
ga.js
25 ms
yanonekaffeesatz-light-webfont.svg
1198 ms
duepuntozero.svg
923 ms
yanonekaffeesatz-regular-webfont.svg
1306 ms
yanonekaffeesatz-bold-webfont.svg
1354 ms
_iniJQ2.js
482 ms
__utm.gif
25 ms
collect
62 ms
duepuntozero.woff
226 ms
yanonekaffeesatz-light-webfont.woff
226 ms
style-cookies.css
107 ms
jquery.cookie.js
212 ms
marlex.net 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.
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
Form elements do not have associated labels
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.
marlex.net 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
Missing source maps for large first-party JavaScript
marlex.net 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
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 Marlex.net 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 Marlex.net 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.
marlex.net
Open Graph description is not detected on the main page of Marlex. 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: