Tools & Wizards About Us
propamsa.es screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

propamsa.es

Propamsa - Soluciones especiales para la construcción

Page Load Speed

5.5 sec in total

First Response

349 ms

Resources Loaded

3.8 sec

Page Rendered

1.3 sec

propamsa.es screenshot

About Website

Visit propamsa.es now to see the best up-to-date Propamsa content for Spain and also check out these interesting facts you probably never knew about propamsa.es

Propamsa ofrece un servicio 360 a los profesionales del sector de la construcción. Más de 85 años innovando en productos y soluciones para construcción.

Visit propamsa.es

Key Findings

We analyzed Propamsa.es page load time and found that the first response time was 349 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

propamsa.es performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value3,560 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

propamsa.es

349 ms

www.propamsa.es

538 ms

1205 ms

style.min.css

295 ms

styles.css

83 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Propamsa.es, 82% (58 requests) were made to Molins.es and 8% (6 requests) were made to Cdn-mol-web-pro-fccrfzgbedcxa3fn.a02.azurefd.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Molins.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 201.8 kB (50%)

Content Size

400.5 kB

After Optimization

198.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Propamsa.es main page is 400.5 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. 45% of websites need less resources to load. HTML takes 208.0 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 186.8 kB

  • Original 208.0 kB
  • After minification 129.6 kB
  • After compression 21.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 78.4 kB, which is 38% 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 186.8 kB or 90% of the original size.

JavaScript Optimization

-8%

Potential reduce by 10.0 kB

  • Original 125.5 kB
  • After minification 125.5 kB
  • After compression 115.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 5.0 kB

  • Original 67.0 kB
  • After minification 66.8 kB
  • After compression 62.0 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. Propamsa.es has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (97%)

Requests Now

66

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Propamsa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

propamsa.es

propamsa.es

349 ms

www.propamsa.es

www.propamsa.es

538 ms

1205 ms

style.min.css

style.min.css

295 ms

styles.css

styles.css

83 ms

woocommerce-layout.css

woocommerce-layout.css

165 ms

woocommerce.css

woocommerce.css

252 ms

wpb_wmca_style.css

wpb_wmca_style.css

248 ms

style.css

style.css

247 ms

style.css

style.css

245 ms

style-index.css

style-index.css

249 ms

jquery.min.js

jquery.min.js

53 ms

jquery-migrate.min.js

jquery-migrate.min.js

45 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

247 ms

add-to-cart.min.js

add-to-cart.min.js

323 ms

js.cookie.min.js

js.cookie.min.js

324 ms

woocommerce.min.js

woocommerce.min.js

324 ms

jquery.cookie.js

jquery.cookie.js

324 ms

jquery.navgoco.min.js

jquery.navgoco.min.js

325 ms

custom.js

custom.js

325 ms

wc-blocks.css

wc-blocks.css

400 ms

non-critical-script.js

non-critical-script.js

403 ms

lazysizes.min.js

lazysizes.min.js

401 ms

index.js

index.js

400 ms

index.js

index.js

400 ms

sourcebuster.min.js

sourcebuster.min.js

400 ms

order-attribution.min.js

order-attribution.min.js

481 ms

accordion-init.js

accordion-init.js

480 ms

api.js

api.js

46 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

38 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

54 ms

wp-polyfill.min.js

wp-polyfill.min.js

56 ms

index.js

index.js

479 ms

frontend.js

frontend.js

482 ms

v2.js

v2.js

51 ms

slick.min.js

slick.min.js

480 ms

lazyload.min.js

lazyload.min.js

560 ms

_module.css

_module.css

326 ms

_module.css

_module.css

327 ms

_module.css

_module.css

328 ms

_module.css

_module.css

331 ms

_reset.css

_reset.css

83 ms

_fonts.css

_fonts.css

206 ms

_variables.css

_variables.css

82 ms

_text.css

_text.css

82 ms

_transitions.css

_transitions.css

83 ms

_structure.css

_structure.css

83 ms

_footer.css

_footer.css

163 ms

_header.css

_header.css

163 ms

_accordion.css

_accordion.css

161 ms

_blocks.css

_blocks.css

163 ms

_breadcrumb.css

_breadcrumb.css

166 ms

_cards.css

_cards.css

242 ms

_carousel.css

_carousel.css

243 ms

_filters.css

_filters.css

243 ms

_forms.css

_forms.css

244 ms

_highlights.css

_highlights.css

244 ms

_modal.css

_modal.css

282 ms

_pager.css

_pager.css

322 ms

_sections.css

_sections.css

324 ms

_table.css

_table.css

323 ms

_home.css

_home.css

323 ms

_news.css

_news.css

324 ms

_products.css

_products.css

362 ms

_search.css

_search.css

401 ms

_statics.css

_statics.css

401 ms

gtm.js

gtm.js

94 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

114 ms

molins.woff

molins.woff

153 ms

be.js

be.js

146 ms

loader.js

loader.js

500 ms

Accessibility Review

propamsa.es accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

propamsa.es best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

propamsa.es SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Propamsa.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 Propamsa.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.

Social Sharing Optimization

propamsa.es

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: