81.5 sec in total
731 ms
43.8 sec
37 sec
Click here to check amazing DOMINION content for Spain. Otherwise, check out these important facts you probably never knew about dominion.es
Somos una compañía global de servicios y proyectos integrales. Descubre por qué DOMINION.
Visit dominion.esWe analyzed Dominion.es page load time and found that the first response time was 731 ms and then it took 80.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 24 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
dominion.es performance score
name
value
score
weighting
Value17.4 s
0/100
10%
Value25.9 s
0/100
25%
Value26.2 s
0/100
10%
Value4,080 ms
1/100
30%
Value0.068
96/100
15%
Value26.5 s
0/100
10%
731 ms
655 ms
700 ms
311 ms
667 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dominion.es, 3% (3 requests) were made to Cookie-cdn.cookiepro.com and 2% (2 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.9 sec) relates to the external source Dominion-global.com.
Page size can be reduced by 1.0 MB (49%)
2.1 MB
1.1 MB
In fact, the total size of Dominion.es main page is 2.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 53.5 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 53.5 kB or 82% of the original size.
Potential reduce by 16.8 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. DOMINION images are well optimized though.
Potential reduce by 45.2 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 45.2 kB or 62% of the original size.
Potential reduce by 904.3 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. Dominion.es needs all CSS files to be minified and compressed as it can save up to 904.3 kB or 87% of the original size.
Number of requests can be reduced by 47 (67%)
70
23
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DOMINION. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
731 ms
OtAutoBlock.js
655 ms
otSDKStub.js
700 ms
busqueda.css
311 ms
font-awesome-5.min.css
667 ms
font-awesome-v4-shims.css
1457 ms
animate.min.css
1625 ms
sppagebuilder.css
3074 ms
proyectos.css
1452 ms
page-1.css
1319 ms
content.css
1320 ms
bootstrap.min.css
2472 ms
font-awesome.min.css
2229 ms
fa-v4-shims.css
1743 ms
template.css
1948 ms
default.css
2225 ms
owl.carousel.min.css
2223 ms
owl.theme.default.min.css
2800 ms
aos.css
2891 ms
evo-calendar.css
3657 ms
template.css
3501 ms
fonts-style.css
3820 ms
master.min.css
4589 ms
template.css
3822 ms
chosen.css
3823 ms
jquery.min.js
4070 ms
jquery-noconflict.js
4064 ms
jquery-migrate.min.js
4066 ms
jquery.parallax.js
4067 ms
sppagebuilder.js
4183 ms
distribuidorbasico.js
4185 ms
proyectos.min.js
4185 ms
popper.min.js
4326 ms
bootstrap.min.js
4327 ms
main.js
4329 ms
owl.carousel.min.js
4329 ms
aos.js
4510 ms
ScrollMagic.min.js
4404 ms
js
1184 ms
debug.addIndicators.min.js
4324 ms
animation.gsap.min.js
4284 ms
gsap.min.js
0 ms
fee1058b-5766-431a-aec9-139da7d55217.json
508 ms
Chart.bundle.min.js
0 ms
jquery.mobile-events.min.js
5883 ms
eurolandtoolsintegrationobject.js
5758 ms
main-menu.js
0 ms
menu.js
0 ms
custom.js
0 ms
lightbox.js
0 ms
dominion-global.js
0 ms
site-animation.js
0 ms
formularios.js
0 ms
popup-video.js
0 ms
interactivo.js
0 ms
agenda.js
0 ms
graficas.js
0 ms
acordeon.js
0 ms
load-yt-video.js
0 ms
iframe.js
0 ms
filtros.js
0 ms
testimonio.js
0 ms
distribuidor-basico.js
0 ms
linea-temporal.js
0 ms
mootools-core.js
0 ms
core.js
0 ms
mootools-more.js
0 ms
chosen.jquery.min.js
0 ms
logo.svg
3941 ms
ic-menu-hamburguesa.svg
4224 ms
marca-dominion.svg
4222 ms
construccion_industria.jpg
4476 ms
boton-flechaderecha.png
4319 ms
dominion-energia-home.jpg
4607 ms
telecomunicaciones_dominion_areas_de_actividad.jpg
4472 ms
dominion-infraestructuras-home.jpg
4810 ms
home-smart-house.jpg
4600 ms
Mikel_Barandiaran_DOMINION.jpg
4679 ms
arboles_bosque_esg.jpg
4676 ms
icon-ubicacion.png
4472 ms
marca-dominion.png
4676 ms
ic-user-blue.svg
4677 ms
two-businessmen-with-laptop-on-business-meeting-pbz4ej3-1.jpg
5338 ms
ic_transformacion.svg
4818 ms
ic_energia.svg
4927 ms
ic_telecomunicaciones.svg
5042 ms
ic_industria.svg
5045 ms
ic_infraestructuras.svg
5174 ms
ic_hogar.svg
5337 ms
ic-lupa.svg
5513 ms
cerrar.svg
5391 ms
arrow-up.svg
5469 ms
el-soco-dominion-case.jpg
5631 ms
gen_204
2940 ms
Barlow-Medium.ttf
1887 ms
Barlow-Regular.ttf
2043 ms
Barlow-Light.ttf
2047 ms
Barlow-Thin.ttf
2047 ms
fa-solid-900.woff
1976 ms
fa-solid-900.woff
1971 ms
fa-regular-400.woff
1971 ms
fa-regular-400.woff
2121 ms
fa-brands-400.woff
2122 ms
fa-brands-400.woff
2124 ms
4695 ms
dominion.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
Image elements do not have [alt] attributes
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.
dominion.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
Browser errors were logged to the console
dominion.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
Image elements do not have [alt] attributes
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 Dominion.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 Dominion.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.
dominion.es
Open Graph description is not detected on the main page of DOMINION. 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: