5 sec in total
661 ms
4.1 sec
179 ms
Welcome to primur.es homepage info - get ready to check Primur best content right away, or after learning these important things about primur.es
Soluciones integrales y acabados profesionales en cabinas de aseo, aseos auto limpiables, kioscos, cabinas y mobiliario urbano.
Visit primur.esWe analyzed Primur.es page load time and found that the first response time was 661 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
primur.es performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value7.0 s
6/100
25%
Value16.6 s
0/100
10%
Value10,190 ms
0/100
30%
Value0.002
100/100
15%
Value19.7 s
2/100
10%
661 ms
2127 ms
310 ms
329 ms
223 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Primur.es, 92% (60 requests) were made to Primur.eu and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Primur.eu.
Page size can be reduced by 209.7 kB (35%)
595.0 kB
385.3 kB
In fact, the total size of Primur.es main page is 595.0 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. 20% of websites need less resources to load. Images take 304.9 kB which makes up the majority of the site volume.
Potential reduce by 32.9 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 32.9 kB or 78% of the original size.
Potential reduce by 12.4 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. Primur images are well optimized though.
Potential reduce by 108.0 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 108.0 kB or 60% of the original size.
Potential reduce by 56.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. Primur.es needs all CSS files to be minified and compressed as it can save up to 56.4 kB or 82% of the original size.
Number of requests can be reduced by 37 (59%)
63
26
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Primur. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
primur.es
661 ms
primur.eu
2127 ms
system.base.css
310 ms
system.menus.css
329 ms
system.messages.css
223 ms
system.theme.css
346 ms
field.css
232 ms
node.css
335 ms
search.css
349 ms
user.css
411 ms
views.css
438 ms
ctools.css
346 ms
panels.css
360 ms
onecol.css
364 ms
locale.css
413 ms
nice_menus.css
555 ms
nice_menus_default.css
566 ms
reset.css
475 ms
layout.css
479 ms
menu.css
720 ms
style.css
935 ms
fonts.css
595 ms
jquery.js
820 ms
jquery.once.js
662 ms
drupal.js
897 ms
jquery.bgiframe.js
713 ms
jquery.hoverIntent.js
772 ms
superfish.js
827 ms
nice_menus.js
820 ms
googleanalytics.js
881 ms
formdescuento.js
926 ms
carrusel-inicio.js
924 ms
carrusel-producto.js
946 ms
analytics.js
63 ms
ga.js
63 ms
logo.png
110 ms
search.png
118 ms
arrow-right.png
114 ms
kiosco_1900_.jpg
578 ms
cabecera_aseos_2_0.jpg
449 ms
banco_luna_detalle_0.jpg
437 ms
slide-kioscos_0.jpg
327 ms
obra_especial_equipamiento_interior_mercat_les_encants_2.jpg
557 ms
inicio-kioscos_0.jpg
234 ms
cabecera_aseos_0.jpg
350 ms
banco_luna_0.jpg
435 ms
inicio-esp.jpg
467 ms
obra_especial_equipamiento_interior_mercat_les_encant_1.jpg
544 ms
bg-footer-sw.png
547 ms
menu-leaf.png
552 ms
bot-empresa.png
583 ms
bot-catalogo.png
653 ms
bot-certificaciones.png
656 ms
bot-noticias.png
655 ms
logo-once.jpg
667 ms
logo-ceosa.png
693 ms
logo-juegos-once.png
698 ms
logo-fundacion-once.png
761 ms
logo-confortel.png
758 ms
logo-viajes2000.png
765 ms
logo-seguronce.png
778 ms
bg-slide-sw.png
807 ms
bg-slide-h.png
813 ms
collect
20 ms
__utm.gif
11 ms
primur.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
Links do not have a discernible name
primur.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
Page has valid source maps
primur.es SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primur.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Primur.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.
primur.es
Open Graph description is not detected on the main page of Primur. 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: