7.6 sec in total
420 ms
6.4 sec
812 ms
Welcome to fpf.pt homepage info - get ready to check FPF best content for Portugal right away, or after learning these important things about fpf.pt
Consulte informação relativa a seleções nacionais, competições, eventos e notícias relacionadas com o mundo do futebol português. Mantenha-se atualizado!
Visit fpf.ptWe analyzed Fpf.pt page load time and found that the first response time was 420 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fpf.pt performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value13.0 s
0/100
25%
Value10.0 s
9/100
10%
Value3,130 ms
2/100
30%
Value1.598
0/100
15%
Value12.5 s
14/100
10%
420 ms
517 ms
2371 ms
202 ms
276 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 91% of them (122 requests) were addressed to the original Fpf.pt, 2% (3 requests) were made to Ajax.googleapis.com and 2% (3 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Fpf.pt.
Page size can be reduced by 1.6 MB (58%)
2.8 MB
1.2 MB
In fact, the total size of Fpf.pt main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 287.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. This page needs HTML code to be minified as it can gain 72.4 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 287.4 kB or 93% of the original size.
Potential reduce by 17.1 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. FPF images are well optimized though.
Potential reduce by 877.7 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 877.7 kB or 69% of the original size.
Potential reduce by 441.5 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. Fpf.pt needs all CSS files to be minified and compressed as it can save up to 441.5 kB or 87% of the original size.
Number of requests can be reduced by 64 (52%)
122
58
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FPF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fpf.pt
420 ms
www.fpf.pt
517 ms
2371 ms
hotjar-313796.js
202 ms
default.css
276 ms
skin.css
435 ms
container.css
200 ms
portal.css
199 ms
home.css
221 ms
jquery.min.js
21 ms
jquery-ui.min.js
24 ms
WebForms.js
20 ms
MicrosoftAjax.js
7 ms
MicrosoftAjaxWebForms.js
8 ms
Module.js
210 ms
Module.js
213 ms
js.cookie.js
231 ms
dnn.modalpopup.js
227 ms
Module.js
261 ms
angular.min.js
479 ms
App.js
295 ms
MainController.js
311 ms
ServiceManager.js
320 ms
dnncore.js
343 ms
angular.min.js
603 ms
FeedsController.js
495 ms
angular-locale_pt-pt.js
1702 ms
angular-sanitize.js
50 ms
responsive-img.min.js
411 ms
jquery.magnific-popup.min.js
400 ms
jquery.cycle2.min.js
400 ms
jquery.cycle2.swipe.min.js
400 ms
jquery.cycle2.carousel.min.js
419 ms
jquery.selectric.min.js
419 ms
freewall.js
420 ms
jquery.ui.datepicker-pt-PT.js
462 ms
jquery.ui.datepicker-en-US.js
463 ms
clipboard.min.js
534 ms
jquery.validate.js
534 ms
jquery.validate.unobtrusive.min.js
534 ms
js.cookie.js
567 ms
functions.js
567 ms
main.js
645 ms
modules-7579e9ce0bcb2fbf460db394bab8dbd6.js
52 ms
roboto-regular-webfont.woff
499 ms
dc.js
84 ms
fpf-logo.png
255 ms
fpf-logo-text.png
256 ms
fpf-logo-text-print.png
256 ms
ico-indicadores.png
257 ms
ico-resultados.png
480 ms
ico-fpftv.png
472 ms
ico-media.png
481 ms
ico-bilheteira_branco-2.png
481 ms
ico-shop.png
482 ms
logo_VAR.png
484 ms
logo_FPF_branco_4.png
483 ms
logo_FPF_preto_3.png
484 ms
logo_FPF_branco_CORRETO.png
483 ms
fpf-gray.png
485 ms
feed1x1.png
485 ms
fpf-color.png
694 ms
fpf-white.png
693 ms
LigaNos.jpg
693 ms
_AN_9778.JPG
692 ms
transparent_5x5.png
690 ms
ico-facebook.png
692 ms
ico-twitter.png
701 ms
ico-youtube.png
684 ms
ico-instagram.png
684 ms
nike_footer.png
682 ms
samsung_footer.png
639 ms
hertz_footer.png
639 ms
__utm.gif
66 ms
ico-linkedin.png
619 ms
supporter-fifa.png
587 ms
supporter-uefa.png
586 ms
fpf-gray.png
586 ms
wingman-logo.png
553 ms
header-bg.png
645 ms
header-left-mask.png
548 ms
header-right-mask.png
548 ms
search-icon.png
546 ms
burger-icon.png
544 ms
imagem_VAR.png
560 ms
bebasneue_regular-webfont.woff
656 ms
bebasneue_bold-webfont.woff
526 ms
robotocondensed-regular-webfont.woff
525 ms
bebasneue_book-webfont.woff
533 ms
roboto-italic-webfont.woff
523 ms
integridade_v3.jpg
429 ms
candidaturas_infraestruturas.jpg
696 ms
selecao_verde.jpg
696 ms
fundo_boletim_correto.png
696 ms
button-arrow.png
697 ms
bg-half-white-left.png
696 ms
bg-half-white-right.png
695 ms
icon-share.png
487 ms
icon-play.png
488 ms
bg-half-grey-left.png
487 ms
bg-half-grey-right.png
488 ms
button-plus.png
487 ms
lvl1-down.png
486 ms
lvl-plus.png
487 ms
robotocondensed-bold-webfont.woff
503 ms
roboto-bold-webfont.woff
582 ms
roboto-medium-webfont.woff
582 ms
searchIcon.png
613 ms
searchCancelButton.png
611 ms
close-icon.png
611 ms
default-loading.gif
610 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
575 ms
nationalTeamAndCompetitionsResults.html
332 ms
internationalPlayerResults.html
387 ms
playerResults.html
404 ms
newsResults.html
409 ms
matchesAndEventsResults.html
441 ms
galleryResults.html
341 ms
callupsResults.html
450 ms
documentsResults.html
456 ms
button-loading.gif
218 ms
croppedImage_59432_20170929183515.jpg
192 ms
bb-left-corner-type-B.png
93 ms
bb-right-corner-type-B.png
98 ms
croppedImage_68987_20170929145652.jpg
111 ms
170925sh6_1.JPG
177 ms
croppedImage_68964_20170929141629.jpg
193 ms
croppedImage_68967_20170929130249.JPG
288 ms
amarelo.jpg
200 ms
Jose%20Paisana_2017%20(2).jpg
265 ms
bernardo_basileia.jpg
270 ms
97050de88e30499596b173ab6f323a07bece3d6aabf04ac9ae6c9d5f6839b7b1.jpg
280 ms
SAM_3066_1.JPG
287 ms
Jorge%20Braz_sorteio.jpg
354 ms
fpf.pt accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fpf.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fpf.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fpf.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 Fpf.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.
fpf.pt
Open Graph description is not detected on the main page of FPF. 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: