Tools & Wizards About Us
proin.es screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

proin.es

PROIN

Page Load Speed

8.3 sec in total

First Response

470 ms

Resources Loaded

7.5 sec

Page Rendered

249 ms

proin.es screenshot

About Website

Welcome to proin.es homepage info - get ready to check PROIN best content right away, or after learning these important things about proin.es

Proin, Procedimientos Integrados. Automatización y Control de Plantas de fabricación de hormigon preparado, prefabricados, morteros, canteras, asfaltos,

Visit proin.es

Key Findings

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

Performance Metrics

proin.es performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.242

51/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

proin.es

470 ms

www.proin.es

5410 ms

accordianfrontpagecore.css

366 ms

mootools.js

506 ms

caption.js

296 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 96% of them (55 requests) were addressed to the original Proin.es, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Proin.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.3 kB (34%)

Content Size

486.9 kB

After Optimization

322.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Proin.es main page is 486.9 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. 25% of websites need less resources to load. Images take 265.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 17.9 kB

  • Original 23.4 kB
  • After minification 21.9 kB
  • After compression 5.4 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 17.9 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 18.4 kB

  • Original 265.3 kB
  • After minification 246.9 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. PROIN images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 84.5 kB

  • Original 146.5 kB
  • After minification 143.4 kB
  • After compression 62.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 84.5 kB or 58% of the original size.

CSS Optimization

-84%

Potential reduce by 43.4 kB

  • Original 51.8 kB
  • After minification 42.2 kB
  • After compression 8.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. Proin.es needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (45%)

Requests Now

55

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proin.es

proin.es

470 ms

www.proin.es

www.proin.es

5410 ms

accordianfrontpagecore.css

accordianfrontpagecore.css

366 ms

mootools.js

mootools.js

506 ms

caption.js

caption.js

296 ms

general.css

general.css

348 ms

template.css

template.css

435 ms

rokslidestrip.css

rokslidestrip.css

334 ms

light.css

light.css

470 ms

menustyle3-light.css

menustyle3-light.css

471 ms

rokzoom.css

rokzoom.css

486 ms

mootools-release-1.11.js

mootools-release-1.11.js

686 ms

rokslidestrip.js

rokslidestrip.js

583 ms

rokzoom.js

rokzoom.js

583 ms

fondo_raya.png

fondo_raya.png

129 ms

main-t.png

main-t.png

161 ms

main-tl.png

main-tl.png

174 ms

main-tr.png

main-tr.png

178 ms

blank.png

blank.png

141 ms

logo.png

logo.png

383 ms

path-logo.png

path-logo.png

231 ms

conex.jpg

conex.jpg

370 ms

proinlab.jpg

proinlab.jpg

376 ms

calculo.jpg

calculo.jpg

379 ms

despacho.jpg

despacho.jpg

495 ms

G4.jpg

G4.jpg

436 ms

trazabilidad.jpg

trazabilidad.jpg

474 ms

centralizacion.jpg

centralizacion.jpg

480 ms

concret.jpg

concret.jpg

493 ms

serv_tecn_p.jpg

serv_tecn_p.jpg

496 ms

module-br.png

module-br.png

556 ms

module-tr.png

module-tr.png

581 ms

module-bl.png

module-bl.png

591 ms

module-tl.png

module-tl.png

583 ms

menu3-line.png

menu3-line.png

591 ms

menu3-sideactive-tab-r.png

menu3-sideactive-tab-r.png

598 ms

menu3-sideactive-tab-l.png

menu3-sideactive-tab-l.png

657 ms

menu3-dot.png

menu3-dot.png

682 ms

st.png

st.png

710 ms

aplicacion_hormigonero.png

aplicacion_hormigonero.png

819 ms

catalogo.png

catalogo.png

718 ms

teleasistencia.jpg

teleasistencia.jpg

720 ms

donwloadsp.png

donwloadsp.png

766 ms

servicios_proin.png

servicios_proin.png

784 ms

arrow_down.png

arrow_down.png

811 ms

readon.png

readon.png

818 ms

main-b.png

main-b.png

818 ms

main-bl.png

main-bl.png

858 ms

main-br.png

main-br.png

885 ms

ga.js

ga.js

6 ms

__utm.gif

__utm.gif

11 ms

blank.png

blank.png

120 ms

zoom-shadow1.png

zoom-shadow1.png

128 ms

zoom-shadow3.png

zoom-shadow3.png

129 ms

zoom-shadow4.png

zoom-shadow4.png

130 ms

zoom-shadow6.png

zoom-shadow6.png

129 ms

zoom-shadow8.png

zoom-shadow8.png

128 ms

Accessibility Review

proin.es accessibility score

83

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

proin.es best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

proin.es SEO score

76

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proin.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Proin.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

proin.es

Open Graph description is not detected on the main page of PROIN. 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: