Tools & Wizards About Us
fpr.pt screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

fpr.pt

PORTUGAL RUGBY

Page Load Speed

4.2 sec in total

First Response

863 ms

Resources Loaded

3.1 sec

Page Rendered

246 ms

fpr.pt screenshot

About Website

Welcome to fpr.pt homepage info - get ready to check Fpr best content for Portugal right away, or after learning these important things about fpr.pt

DEFAULT_META_DESC

Visit fpr.pt

Key Findings

We analyzed Fpr.pt page load time and found that the first response time was 863 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

fpr.pt performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value2,770 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.456

19/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

fpr.pt

863 ms

fpr.css

571 ms

Main.js

465 ms

jquery-1.3.2.min.js

661 ms

jquery.loadmask.css

222 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 98% of them (97 requests) were addressed to the original Fpr.pt, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (914 ms) belongs to the original domain Fpr.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 263.4 kB (30%)

Content Size

866.2 kB

After Optimization

602.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fpr.pt main page is 866.2 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. 30% of websites need less resources to load. Images take 578.8 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 81.8 kB

  • Original 92.4 kB
  • After minification 70.9 kB
  • After compression 10.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 21.5 kB, which is 23% 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 81.8 kB or 89% of the original size.

Image Optimization

-8%

Potential reduce by 48.5 kB

  • Original 578.8 kB
  • After minification 530.3 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. Fpr images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 79.4 kB

  • Original 131.4 kB
  • After minification 114.9 kB
  • After compression 51.9 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 79.4 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 53.6 kB

  • Original 63.7 kB
  • After minification 48.9 kB
  • After compression 10.1 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. Fpr.pt needs all CSS files to be minified and compressed as it can save up to 53.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (17%)

Requests Now

98

After Optimization

81

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fpr. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fpr.pt

fpr.pt

863 ms

fpr.css

fpr.css

571 ms

Main.js

Main.js

465 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

661 ms

jquery.loadmask.css

jquery.loadmask.css

222 ms

jquery.loadmask.min.js

jquery.loadmask.min.js

223 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

552 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

551 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

543 ms

ddlevelsmenu-base.css

ddlevelsmenu-base.css

572 ms

ddlevelsmenu-topbar.css

ddlevelsmenu-topbar.css

653 ms

ddlevelsmenu.js

ddlevelsmenu.js

769 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

681 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

675 ms

fundo.jpg

fundo.jpg

335 ms

twitter_btn.png

twitter_btn.png

116 ms

facebook_btn.png

facebook_btn.png

114 ms

home_v2_btn3.png

home_v2_btn3.png

117 ms

separador_menu.png

separador_menu.png

118 ms

federacao_v2_btn.png

federacao_v2_btn.png

117 ms

leis_jogo_v2_btn.png

leis_jogo_v2_btn.png

236 ms

regulamentos_v2_btn.png

regulamentos_v2_btn.png

225 ms

competicoes_v2_btn.png

competicoes_v2_btn.png

230 ms

seleccoes_v2_btn.png

seleccoes_v2_btn.png

233 ms

formacao_v2_btn.png

formacao_v2_btn.png

227 ms

desenvolvimento_v2_btn.png

desenvolvimento_v2_btn.png

335 ms

arbitragem_v2_btn.png

arbitragem_v2_btn.png

338 ms

links_v2_btn.png

links_v2_btn.png

337 ms

pesquisa_input.png

pesquisa_input.png

339 ms

ok_btn.png

ok_btn.png

344 ms

10604001_807260892711924_329835914787902461_o.jpg

10604001_807260892711924_329835914787902461_o.jpg

446 ms

back-col-tab-classificacao.jpg

back-col-tab-classificacao.jpg

458 ms

classificacao.jpg

classificacao.jpg

459 ms

cgd_2015.png

cgd_2015.png

470 ms

agenda.jpg

agenda.jpg

446 ms

rugbyAntiDoping.jpg

rugbyAntiDoping.jpg

475 ms

destaque.jpg

destaque.jpg

554 ms

JP_sub18.jpg

JP_sub18.jpg

557 ms

linhaGrande.jpg

linhaGrande.jpg

566 ms

_JLP9516.jpg

_JLP9516.jpg

676 ms

noticias.jpg

noticias.jpg

580 ms

citroen.jpg

citroen.jpg

597 ms

ler_rugby.jpg

ler_rugby.jpg

663 ms

title_keeprugbyonside.png

title_keeprugbyonside.png

677 ms

kro-rectangle-ptbr.gif

kro-rectangle-ptbr.gif

801 ms

ondejogar.jpg

ondejogar.jpg

688 ms

onde_jogar.png

onde_jogar.png

707 ms

acessoReservado.jpg

acessoReservado.jpg

774 ms

logo_caixa_lobinhos.png

logo_caixa_lobinhos.png

786 ms

logo_caixa_lobinhos_gr.png

logo_caixa_lobinhos_gr.png

914 ms

analytics.js

analytics.js

23 ms

collect

collect

13 ms

tabela_classificacao.asp

tabela_classificacao.asp

709 ms

parceiros_principais.gif

parceiros_principais.gif

711 ms

logo_cgd_2015.png

logo_cgd_2015.png

777 ms

logo_superbock.gif

logo_superbock.gif

792 ms

logo_jogos_santa_casa.png

logo_jogos_santa_casa.png

807 ms

parceiros_oficiais.gif

parceiros_oficiais.gif

706 ms

logo_citroen.gif

logo_citroen.gif

708 ms

patrocinador_oficial_material_desportivo.png

patrocinador_oficial_material_desportivo.png

782 ms

logo_samurai.png

logo_samurai.png

797 ms

parceiros_institucionais.gif

parceiros_institucionais.gif

799 ms

logo_cml.png

logo_cml.png

707 ms

logo_ipdj.gif

logo_ipdj.gif

721 ms

logo_Instituto_Implantologia.png

logo_Instituto_Implantologia.png

719 ms

fornecedores_oficiais.gif

fornecedores_oficiais.gif

795 ms

logo_pousadas.gif

logo_pousadas.gif

801 ms

logo_hoteis_aa.gif

logo_hoteis_aa.gif

815 ms

logo_gilbert.gif

logo_gilbert.gif

705 ms

logo_vitalis.gif

logo_vitalis.gif

730 ms

logo_quadrantes.gif

logo_quadrantes.gif

722 ms

logo_banana-da-madeira.png

logo_banana-da-madeira.png

797 ms

Logo_Vit&Pro.png

Logo_Vit&Pro.png

782 ms

logo_medicar.png

logo_medicar.png

798 ms

logo_europcar.png

logo_europcar.png

737 ms

logo_gravymedal.png

logo_gravymedal.png

758 ms

logo_fac_corpo.gif

logo_fac_corpo.gif

738 ms

logo_wolfcare.png

logo_wolfcare.png

792 ms

Logo_PanricoDonuts.png

Logo_PanricoDonuts.png

768 ms

logo_sportspartner.gif

logo_sportspartner.gif

735 ms

logo_pms.png

logo_pms.png

734 ms

logo_utilteam.png

logo_utilteam.png

736 ms

logo_fruut.png

logo_fruut.png

754 ms

logo_cision_2015.png

logo_cision_2015.png

769 ms

Logo_quinta_coro.png

Logo_quinta_coro.png

714 ms

gradienteVerm.jpg

gradienteVerm.jpg

721 ms

ajax-loader.gif

ajax-loader.gif

720 ms

gradienteAzul.jpg

gradienteAzul.jpg

705 ms

pdficon_small.png

pdficon_small.png

335 ms

competicoes.jpg

competicoes.jpg

723 ms

boletim_informativo.jpg

boletim_informativo.jpg

708 ms

multimedia.jpg

multimedia.jpg

695 ms

LerRugbyBackground.jpg

LerRugbyBackground.jpg

700 ms

fundo_parceiros_principais.gif

fundo_parceiros_principais.gif

711 ms

fundo_parceiros_oficiais.gif

fundo_parceiros_oficiais.gif

706 ms

fundo_parceiros_institucionais.gif

fundo_parceiros_institucionais.gif

728 ms

fundo_fornecedores_oficiais.gif

fundo_fornecedores_oficiais.gif

697 ms

arrow-right.gif

arrow-right.gif

681 ms

fpr_print.css

fpr_print.css

119 ms

Accessibility Review

fpr.pt accessibility score

80

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fpr.pt SEO score

79

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

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

fpr.pt

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