3.2 sec in total
349 ms
2.5 sec
315 ms
Welcome to enebe.com homepage info - get ready to check ENEBE best content for Spain right away, or after learning these important things about enebe.com
Visit enebe.comWe analyzed Enebe.com page load time and found that the first response time was 349 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
enebe.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value6.6 s
8/100
25%
Value6.3 s
41/100
10%
Value30 ms
100/100
30%
Value0.019
100/100
15%
Value5.7 s
69/100
10%
349 ms
991 ms
194 ms
265 ms
298 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 75% of them (33 requests) were addressed to the original Enebe.com, 23% (10 requests) were made to Use.typekit.net and 2% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (991 ms) belongs to the original domain Enebe.com.
Page size can be reduced by 558.7 kB (31%)
1.8 MB
1.2 MB
In fact, the total size of Enebe.com main page is 1.8 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 23.2 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 6.4 kB, which is 22% 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 23.2 kB or 79% of the original size.
Potential reduce by 57.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. ENEBE images are well optimized though.
Potential reduce by 253.1 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 253.1 kB or 69% of the original size.
Potential reduce by 225.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. Enebe.com needs all CSS files to be minified and compressed as it can save up to 225.4 kB or 84% of the original size.
Number of requests can be reduced by 16 (47%)
34
18
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ENEBE. 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.
enebe.com
349 ms
www.enebe.com
991 ms
language-selector.css
194 ms
sgk0cve.js
265 ms
modernizr.js
298 ms
settings.css
327 ms
styles.f6413c85.min.css
630 ms
style.css
217 ms
adora.css
431 ms
landing.css
289 ms
jquery.js
648 ms
jquery-migrate.min.js
389 ms
jquery.themepunch.tools.min.js
690 ms
jquery.themepunch.revolution.min.js
513 ms
bootstrap.js
585 ms
scripts.d1e3d952.min.js
539 ms
sitepress.js
527 ms
scrollReveal.min.js
570 ms
www.enebe.com
144 ms
wp-emoji-release.min.js
363 ms
logo-enebe-group.png
101 ms
es.png
112 ms
en.png
113 ms
bg-hero.jpg
540 ms
enebe1.jpg
112 ms
dosier.jpg
111 ms
invertex.jpg
191 ms
banner-enebe-2015-300x216.jpg
199 ms
bg-dossier-elegance.jpg
209 ms
catalogo-corporativo.png
318 ms
catalogo-empresa.png
540 ms
catalogo-invertex1.png
485 ms
catalogo-padel-2015.png
397 ms
arrow-down.png
312 ms
catalogo-elegance.png
518 ms
7GzvysT_A4EM3wEMO3USKgQPmE5wfHwwoltI59n0iW6ffV_VMUMdeMJ6Mk6g5MFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
66 ms
cXsBsbBKmM4gcnsiPOl5FRNd3APCOpU8_pFjdA1x1ybffJVbMUMdeMJ6Mk6g5Mmfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
66 ms
MgrFnfOfAjTImex9j-8l2_Gm4lKXxsFh150emrADeYSffJWbMUMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
88 ms
xtn8NK5yPlTlLsY1RDXYOYaCgNvADjcggziXMSMFci9ffJLbMUMdeMJ6Mk6g5M8fb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
118 ms
8tdCg0A1LcjOmJS3O2Tb0FRfvpUJuY8Jz8vIXfP_j0JffJObMUMdeMJ6Mk6g5Mufb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
46 ms
Zg-W5A9yW4_VAcm6YnZmv-k70BUmvmTaHLu8-E3sY2JffJQbMUMdeMJ6Mk6g5MNfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
68 ms
vJznQQlh2Flv_9KmgL8gAdwHFtSJbmPunmFt8V5QXFqffJdbMUMdeMJ6Mk6g5gBfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
74 ms
QQ2mdOXdbcTFtVJEwEr37zptBNHG42xfw6uBJi_vLFvffJRbMUMdeMJ6Mk6g5gFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
75 ms
p.gif
133 ms
enebe.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.
enebe.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
General
Impact
Issue
Detected JavaScript libraries
enebe.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 Enebe.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 Enebe.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.
enebe.com
Open Graph description is not detected on the main page of ENEBE. 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: