Tools & Wizards About Us
rrc.pt screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

rrc.pt

FCC Construcción Portugal - FCCCO Portugal

Page Load Speed

8.6 sec in total

First Response

501 ms

Resources Loaded

7 sec

Page Rendered

1.1 sec

rrc.pt screenshot

About Website

Click here to check amazing Rrc content. Otherwise, check out these important facts you probably never knew about rrc.pt

A FCC Construcción, líder internacional em infraestruturas do Grupo FCC Serviços ao Cidadão, está presente em Portugal há mais de 20 anos com obras tão significativas como a autoestrada Transmontana, ...

Visit rrc.pt

Key Findings

We analyzed Rrc.pt page load time and found that the first response time was 501 ms and then it took 8.1 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

rrc.pt performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value22.0 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value21.2 s

1/100

10%

Network Requests Diagram

rrc.pt

501 ms

1740 ms

aui.css

942 ms

main.css

836 ms

main.css

729 ms

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

Page Optimization Overview & Recommendations

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

Content Size

3.8 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rrc.pt main page is 3.8 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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 70.4 kB

  • Original 83.9 kB
  • After minification 65.4 kB
  • After compression 13.6 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 18.5 kB, which is 22% 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 70.4 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 28.2 kB

  • Original 2.8 MB
  • After minification 2.8 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. Rrc images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 131.8 kB

  • Original 199.6 kB
  • After minification 199.6 kB
  • After compression 67.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 131.8 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 642.7 kB

  • Original 756.7 kB
  • After minification 756.6 kB
  • After compression 114.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. Rrc.pt needs all CSS files to be minified and compressed as it can save up to 642.7 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

50

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rrc.pt

rrc.pt

501 ms

1740 ms

aui.css

aui.css

942 ms

main.css

main.css

836 ms

main.css

main.css

729 ms

main.css

main.css

723 ms

main.css

main.css

726 ms

main.css

main.css

724 ms

barebone.jsp

barebone.jsp

1344 ms

main.css

main.css

1234 ms

top.js

top.js

1124 ms

main.js

main.js

744 ms

main.js

main.js

852 ms

main.js

main.js

943 ms

bottom.js

bottom.js

1042 ms

analytics.js

analytics.js

150 ms

bluePixel.png

bluePixel.png

249 ms

d348a6e4-d89e-45e7-bf76-425cb18cc887

d348a6e4-d89e-45e7-bf76-425cb18cc887

352 ms

3f6cde57-eb26-4bbc-b168-a11ad6216503

3f6cde57-eb26-4bbc-b168-a11ad6216503

234 ms

b3e4cad5-b499-41f9-9cda-12d4f868dee0

b3e4cad5-b499-41f9-9cda-12d4f868dee0

235 ms

9e46e552-0c41-4594-84db-803e376058b9

9e46e552-0c41-4594-84db-803e376058b9

233 ms

a9d9bdda-563e-4f2c-a4f9-e6ae2a749710

a9d9bdda-563e-4f2c-a4f9-e6ae2a749710

280 ms

cf0fb539-ceba-4649-8bf8-ebc2cf630d93

cf0fb539-ceba-4649-8bf8-ebc2cf630d93

422 ms

b02b0743-8787-b8a4-3b95-9dce100ae8a4

b02b0743-8787-b8a4-3b95-9dce100ae8a4

1353 ms

e04b23dc-4c54-2666-8fd9-e939ff4e4d46

e04b23dc-4c54-2666-8fd9-e939ff4e4d46

1759 ms

71a0aff1-aa1e-1366-f1b4-8c54ea5d7412

71a0aff1-aa1e-1366-f1b4-8c54ea5d7412

1555 ms

8ecfbe30-bc7f-7ac0-6e15-42fb345c1493

8ecfbe30-bc7f-7ac0-6e15-42fb345c1493

1378 ms

cbe03fc9-a22d-4dce-ae36-953069868ff5

cbe03fc9-a22d-4dce-ae36-953069868ff5

982 ms

d0131354-0282-418d-ad05-36f50ea3bcef

d0131354-0282-418d-ad05-36f50ea3bcef

1051 ms

ea3641ef-fe8b-8593-cacc-9f8048c0996d

ea3641ef-fe8b-8593-cacc-9f8048c0996d

1409 ms

c19dd7f3-e89c-55fa-ce94-459576b3433d

c19dd7f3-e89c-55fa-ce94-459576b3433d

1564 ms

9c7fdfae-93e3-0f4e-ebe0-920361ad281a

9c7fdfae-93e3-0f4e-ebe0-920361ad281a

1867 ms

af01d1f8-6932-4203-a979-12984a0115da

af01d1f8-6932-4203-a979-12984a0115da

1900 ms

35a1a5cd-fbf8-a0bb-6538-1f7533f6d008

35a1a5cd-fbf8-a0bb-6538-1f7533f6d008

2029 ms

c87abbf3-4ee3-4f19-8f4b-63b6919a7c5f

c87abbf3-4ee3-4f19-8f4b-63b6919a7c5f

2075 ms

d8cd5826-1884-06c5-ac92-f9e0f43fbb7e

d8cd5826-1884-06c5-ac92-f9e0f43fbb7e

1887 ms

226ce69b-167e-4d99-8aae-59d05f1da78c

226ce69b-167e-4d99-8aae-59d05f1da78c

2089 ms

925a2b1b-b2f2-7980-6dc3-58eda148b6c5

925a2b1b-b2f2-7980-6dc3-58eda148b6c5

2191 ms

3fb1f7c9-8c75-42f4-af03-b68bf78aadea

3fb1f7c9-8c75-42f4-af03-b68bf78aadea

2113 ms

8e978c83-39d7-49fa-80a1-264a32910d66

8e978c83-39d7-49fa-80a1-264a32910d66

2121 ms

7ceac273-7f32-4385-8eb1-a932117e8cd3

7ceac273-7f32-4385-8eb1-a932117e8cd3

2252 ms

06165e9b-a267-4738-835f-a03640f29eda

06165e9b-a267-4738-835f-a03640f29eda

2298 ms

0d8e35f2-f385-4b79-669f-68f31ab4773a

0d8e35f2-f385-4b79-669f-68f31ab4773a

2317 ms

386df062-df8f-2ffa-172a-ae1f077c9bde

386df062-df8f-2ffa-172a-ae1f077c9bde

2342 ms

6a1198a4-178d-75cc-d605-d3eea0b22dd5

6a1198a4-178d-75cc-d605-d3eea0b22dd5

2343 ms

lato-regular-webfont.woff

lato-regular-webfont.woff

2444 ms

2256 ms

collect

collect

66 ms

icomoon.ttf

icomoon.ttf

2275 ms

fontawesome-alloy.woff

fontawesome-alloy.woff

2489 ms

lato-black-webfont.woff

lato-black-webfont.woff

2519 ms

lato-bold-webfont.woff

lato-bold-webfont.woff

2519 ms

Accessibility Review

rrc.pt accessibility score

98

Accessibility Issues

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

Links do not have a discernible name

Best Practices

rrc.pt best practices score

83

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

Page has valid source maps

SEO Factors

rrc.pt SEO score

93

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rrc.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Rrc.pt 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

rrc.pt

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