Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

presto.es

RIB Spain | Presto: Software de presupuestos para la construcción.

Page Load Speed

3.4 sec in total

First Response

275 ms

Resources Loaded

2.5 sec

Page Rendered

588 ms

presto.es screenshot

About Website

Welcome to presto.es homepage info - get ready to check Presto best content for Spain right away, or after learning these important things about presto.es

RIB Spain es una empresa innovadora en el sector del software para construcción. Ofrece el programa Presto para presupuestos y mediciones así como RIB 4.0 la plataforma empresarial BIM 5D.

Visit presto.es

Key Findings

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

Performance Metrics

presto.es performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

presto.es

275 ms

www.rib-software.es

465 ms

index.php

296 ms

normalize.css

123 ms

main.css

269 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Presto.es, 81% (30 requests) were made to Rib-software.es and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (945 ms) relates to the external source Rib-software.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 825.7 kB (23%)

Content Size

3.6 MB

After Optimization

2.7 MB

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

HTML Optimization

-79%

Potential reduce by 25.3 kB

  • Original 32.1 kB
  • After minification 21.9 kB
  • After compression 6.8 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 10.2 kB, which is 32% 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 25.3 kB or 79% of the original size.

Image Optimization

-17%

Potential reduce by 545.3 kB

  • Original 3.1 MB
  • After minification 2.6 MB

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. Obviously, Presto needs image optimization as it can save up to 545.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 183.0 kB

  • Original 287.7 kB
  • After minification 287.4 kB
  • After compression 104.8 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 183.0 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 72.1 kB

  • Original 86.8 kB
  • After minification 67.5 kB
  • After compression 14.6 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. Presto.es needs all CSS files to be minified and compressed as it can save up to 72.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (39%)

Requests Now

33

After Optimization

20

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

Accessibility Review

presto.es accessibility score

84

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

Heading elements are not in a sequentially-descending order

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

presto.es best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

presto.es SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Presto.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 Presto.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

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