5.1 sec in total
379 ms
4.5 sec
175 ms
Click here to check amazing ESPA content for Russia. Otherwise, check out these important facts you probably never knew about espa.com
Specialists in the design and manufacture of water pumps for pools, wells, irrigation, pressurization and collection. Find the pump you need.
Visit espa.comWe analyzed Espa.com page load time and found that the first response time was 379 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
espa.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value16.4 s
0/100
25%
Value10.8 s
7/100
10%
Value7,680 ms
0/100
30%
Value0.183
66/100
15%
Value16.6 s
5/100
10%
379 ms
703 ms
778 ms
1118 ms
234 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Espa.com, 94% (46 requests) were made to Global.espa.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.7 sec) relates to the external source Global.espa.com.
Page size can be reduced by 507.5 kB (37%)
1.4 MB
862.3 kB
In fact, the total size of Espa.com main page is 1.4 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. 20% of websites need less resources to load. Images take 721.7 kB which makes up the majority of the site volume.
Potential reduce by 33.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 9.7 kB, which is 24% 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 33.7 kB or 84% of the original size.
Potential reduce by 25.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. ESPA images are well optimized though.
Potential reduce by 340.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 340.2 kB or 71% of the original size.
Potential reduce by 107.7 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. Espa.com needs all CSS files to be minified and compressed as it can save up to 107.7 kB or 84% of the original size.
Number of requests can be reduced by 28 (60%)
47
19
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ESPA. 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 9 to 1 for CSS and as a result speed up the page load time.
espa.com
379 ms
703 ms
jquery-1.6.1.min.js
778 ms
jquery-ui-1.8.16.min.js
1118 ms
jquery.multiselect.min.js
234 ms
jquery.fancybox-1.3.4.pack.js
353 ms
jcarousellite_1.0.1.min.js
244 ms
jquery.cycle.all.js
805 ms
jquery.qtip-1.0.0-rc3.min.js
872 ms
jquery.validate-1.9.0.min.js
838 ms
funcions.js
591 ms
jquery.bxslider.min.js
922 ms
normalize.css
1008 ms
main.css
1020 ms
grid.css
1081 ms
estil.css
1481 ms
estil2.css
1144 ms
jquery.fancybox-1.3.4.css
1258 ms
jquery-ui-1.8.9.custom.css
1495 ms
jquery.multiselect.css
1318 ms
ga.js
24 ms
bkg_body.jpg
224 ms
bkg_main.jpg
225 ms
phpthumbgeneratedthumbnailjpg.png
267 ms
btn_idioma.jpg
240 ms
btn_cercador.jpg
247 ms
menu2_sep.png
253 ms
desplegable_fletxa.png
453 ms
bkg_desplegable.png
459 ms
bkg_menu.jpg
473 ms
aqua-nederland.jpg
636 ms
espapool-nueva-gama-piscinas1.jpg
1549 ms
evopoolapp.jpg
1654 ms
viginox-mxo.jpg
714 ms
filterpak-plus.gif
718 ms
multi-25.jpg
739 ms
nueva-gama-espapool.jpg
1135 ms
evopool255x116.jpg
1077 ms
153
1110 ms
video.png
958 ms
rss.png
1182 ms
__utm.gif
52 ms
bkg_pestanya.png
1269 ms
bkg_ratllat.jpg
1290 ms
fletxes.png
1296 ms
puntets_horitzontals.png
1361 ms
bkg_caixa2.jpg
1503 ms
interactiu.png
1491 ms
print.css
239 ms
espa.com 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
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.
espa.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
Missing source maps for large first-party JavaScript
espa.com 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
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Espa.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Espa.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.
espa.com
Open Graph description is not detected on the main page of ESPA. 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: