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
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

rrc.pt

FCC Construcción Portugal - FCCCO Portugal

Page Load Speed

3.3 sec in total

First Response

141 ms

Resources Loaded

2.7 sec

Page Rendered

361 ms

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 141 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

rrc.pt performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

rrc.pt

141 ms

rrc.pt

110 ms

112 ms

portugal

424 ms

main.css

127 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Rrc.pt, 87% (54 requests) were made to Fccco.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (861 ms) relates to the external source Fccco.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.4 kB (8%)

Content Size

3.3 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-85%

Potential reduce by 142.3 kB

  • Original 167.9 kB
  • After minification 136.6 kB
  • After compression 25.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 31.3 kB, which is 19% 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 142.3 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 76.4 kB

  • Original 2.5 MB
  • After minification 2.4 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

-5%

Potential reduce by 33.6 kB

  • Original 627.8 kB
  • After minification 627.8 kB
  • After compression 594.2 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.

Requests Breakdown

Number of requests can be reduced by 21 (40%)

Requests Now

52

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 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 16 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

141 ms

rrc.pt

rrc.pt

110 ms

112 ms

portugal

portugal

424 ms

main.css

main.css

127 ms

combo

combo

410 ms

api.js

api.js

31 ms

clay.css

clay.css

163 ms

main.css

main.css

169 ms

combo

combo

240 ms

js_loader_config

js_loader_config

138 ms

combo

combo

728 ms

combo

combo

599 ms

combo

combo

673 ms

combo

combo

395 ms

js_bundle_config

js_bundle_config

353 ms

main.css

main.css

511 ms

combo

combo

528 ms

main.js

main.js

477 ms

jquery-ui.min.js

jquery-ui.min.js

673 ms

functions.js

functions.js

587 ms

recaptcha__en.js

recaptcha__en.js

39 ms

analytics.js

analytics.js

59 ms

9ca8e163-1c9f-766e-54ee-fde73428f3aa

9ca8e163-1c9f-766e-54ee-fde73428f3aa

182 ms

b63cf23c-1209-1774-bcc7-239802055cac

b63cf23c-1209-1774-bcc7-239802055cac

182 ms

f7dd75a5-5838-d5ce-bf42-e430e552cd3f

f7dd75a5-5838-d5ce-bf42-e430e552cd3f

181 ms

b02b0743-8787-b8a4-3b95-9dce100ae8a4

b02b0743-8787-b8a4-3b95-9dce100ae8a4

339 ms

e04b23dc-4c54-2666-8fd9-e939ff4e4d46

e04b23dc-4c54-2666-8fd9-e939ff4e4d46

468 ms

e79bf312-54f0-331e-33fe-182926a2d533

e79bf312-54f0-331e-33fe-182926a2d533

704 ms

40d953bd-6116-893a-8ed8-41899f4d3f7b

40d953bd-6116-893a-8ed8-41899f4d3f7b

440 ms

ff7f8f08-97f5-8b8d-e3dd-40b3b28af939

ff7f8f08-97f5-8b8d-e3dd-40b3b28af939

254 ms

81804b77-81c9-c5b2-2657-c79a36dd2d73

81804b77-81c9-c5b2-2657-c79a36dd2d73

315 ms

af01d1f8-6932-4203-a979-12984a0115da

af01d1f8-6932-4203-a979-12984a0115da

415 ms

2f42647b-c06a-38ce-6029-5046308dd8f9

2f42647b-c06a-38ce-6029-5046308dd8f9

438 ms

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

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

468 ms

10ed9cd1-23e0-4731-2df1-39ab8b2ecc35

10ed9cd1-23e0-4731-2df1-39ab8b2ecc35

652 ms

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

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

559 ms

a6d60620-6db5-8b14-90c4-1e827b1061b9

a6d60620-6db5-8b14-90c4-1e827b1061b9

798 ms

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

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

582 ms

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

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

573 ms

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

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

678 ms

06165e9b-a267-4738-835f-a03640f29eda

06165e9b-a267-4738-835f-a03640f29eda

677 ms

8ee7e2e5-69f7-981b-4e7c-22dc493f2006

8ee7e2e5-69f7-981b-4e7c-22dc493f2006

689 ms

9d23735e-21e6-65fb-0f39-48e751d17fc0

9d23735e-21e6-65fb-0f39-48e751d17fc0

759 ms

8857839b-e183-eed4-3133-e4790dbf2d8f

8857839b-e183-eed4-3133-e4790dbf2d8f

784 ms

79e7615d-4a01-4960-cfab-89c8ceea690a

79e7615d-4a01-4960-cfab-89c8ceea690a

784 ms

23d5dea7-9f1e-c9d0-bc9d-51eaaa6408ca

23d5dea7-9f1e-c9d0-bc9d-51eaaa6408ca

789 ms

3437ec7f-8537-9b6a-7e0f-2ad0de09e6b6

3437ec7f-8537-9b6a-7e0f-2ad0de09e6b6

816 ms

icons.svg

icons.svg

743 ms

lato-regular-webfont.woff

lato-regular-webfont.woff

861 ms

852 ms

collect

collect

12 ms

js

js

60 ms

167 ms

botonCookie.png

botonCookie.png

20 ms

fontawesome-alloy.woff

fontawesome-alloy.woff

12 ms

fontawesome-alloy.woff

fontawesome-alloy.woff

137 ms

lato-black-webfont.woff

lato-black-webfont.woff

155 ms

icons.svg

icons.svg

46 ms

icomoon.ttf

icomoon.ttf

42 ms

lato-bold-webfont.woff

lato-bold-webfont.woff

121 ms

108 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: