6.5 sec in total
356 ms
5.2 sec
881 ms
Click here to check amazing FPP content for Portugal. Otherwise, check out these important facts you probably never knew about fpp.pt
A FPP orienta e regulamenta as competições de hóquei em patins, patinagem artística, patinagem de velocidade, hóquei em linha e Skate em Portugal.
Visit fpp.ptWe analyzed Fpp.pt page load time and found that the first response time was 356 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fpp.pt performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value43.7 s
0/100
25%
Value10.2 s
8/100
10%
Value170 ms
92/100
30%
Value0.463
19/100
15%
Value18.7 s
3/100
10%
356 ms
1781 ms
334 ms
336 ms
492 ms
Our browser made a total of 168 requests to load all elements on the main page. We found that 84% of them (141 requests) were addressed to the original Fpp.pt, 8% (14 requests) were made to Ajax.aspnetcdn.com and 2% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Fpp.pt.
Page size can be reduced by 2.5 MB (32%)
7.8 MB
5.3 MB
In fact, the total size of Fpp.pt main page is 7.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 442.5 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 153.3 kB, which is 29% 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 442.5 kB or 84% of the original size.
Potential reduce by 1.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, FPP needs image optimization as it can save up to 1.6 MB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 414.0 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 414.0 kB or 74% of the original size.
Potential reduce by 57.7 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. Fpp.pt needs all CSS files to be minified and compressed as it can save up to 57.7 kB or 84% of the original size.
Number of requests can be reduced by 23 (14%)
162
139
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FPP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fpp.pt
356 ms
www.fpp.pt
1781 ms
font-awesome.min.css
334 ms
style.css
336 ms
jquery-2.2.0.min.js
492 ms
masonry.pkgd.min.js
381 ms
imagesloaded.pkgd.min.js
255 ms
fpp.js
366 ms
Backgrounds.css
55 ms
Tabs.css
84 ms
css
62 ms
WebForms.js
30 ms
MicrosoftAjax.debug.js
118 ms
MicrosoftAjaxWebForms.debug.js
95 ms
Localization.Resources.debug.js
94 ms
ComponentSet.debug.js
94 ms
Common.debug.js
93 ms
BaseScripts.debug.js
91 ms
Tabs.debug.js
94 ms
DynamicPopulate.debug.js
95 ms
Compat.Timer.debug.js
94 ms
AnimationScripts.debug.js
93 ms
Accordion.debug.js
138 ms
banner-txt-small.png
283 ms
00000894.jpg
381 ms
00000895.jpg
356 ms
00000896.jpg
444 ms
00000897.jpg
568 ms
00000898.jpg
379 ms
00000893.jpg
356 ms
00000149.jpg
668 ms
icon1.png
458 ms
00000148.jpg
606 ms
00000079.jpg
826 ms
icon2.png
556 ms
00000147.jpg
901 ms
00000145.jpg
779 ms
icon3.png
719 ms
00000141.jpg
728 ms
00000005.jpg
782 ms
00000140.jpg
1051 ms
00000113.jpg
841 ms
00000138.jpg
1010 ms
icon0.png
896 ms
ir2016.jpg
942 ms
014.png
953 ms
002.png
1008 ms
007.png
1014 ms
009.png
1055 ms
008.png
1063 ms
010.png
1119 ms
012.png
1119 ms
004.png
1120 ms
005.png
1160 ms
011.png
1165 ms
001.png
1173 ms
006.png
1229 ms
sdk.js
309 ms
003.png
1219 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
52 ms
013.png
1164 ms
widgets.js
46 ms
7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf
46 ms
analytics.js
114 ms
fontawesome-webfont.woff
1009 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
47 ms
collect
115 ms
SF%20Digital%20Readout%20Medium.ttf
926 ms
134 ms
020.png
926 ms
xd_arbiter.php
215 ms
xd_arbiter.php
426 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.pt.html
44 ms
097.png
969 ms
094.png
929 ms
098.png
908 ms
093.png
935 ms
061.png
841 ms
064.png
833 ms
026.png
853 ms
099.png
792 ms
jot.html
2 ms
065.png
746 ms
096.png
777 ms
062.png
729 ms
063.png
731 ms
031.png
747 ms
032.png
730 ms
034.png
674 ms
068.png
719 ms
067.png
674 ms
069.png
668 ms
028.png
674 ms
017.png
672 ms
021.png
672 ms
072.png
681 ms
070.png
678 ms
030.png
673 ms
033.png
675 ms
049.png
677 ms
045.png
676 ms
050.png
682 ms
080.png
681 ms
084.png
673 ms
043.png
676 ms
085.png
677 ms
046.png
677 ms
022.png
671 ms
083.png
668 ms
086.png
650 ms
044.png
677 ms
019.png
675 ms
082.png
675 ms
052.png
680 ms
055.png
679 ms
058.png
673 ms
089.png
675 ms
027.png
675 ms
092.png
672 ms
054.png
679 ms
057.png
677 ms
090.png
675 ms
087.png
676 ms
091.png
677 ms
075.png
675 ms
077.png
681 ms
038.png
678 ms
041.png
678 ms
074.png
674 ms
076.png
677 ms
036.png
677 ms
079.png
676 ms
018.png
675 ms
078.png
674 ms
073.png
674 ms
039.png
674 ms
016.png
674 ms
015.png
676 ms
000.png
674 ms
056.png
675 ms
053.png
675 ms
037.png
675 ms
042.png
674 ms
103.png
675 ms
106.png
674 ms
101.png
674 ms
109.png
675 ms
102.png
676 ms
104.png
674 ms
105.png
673 ms
108.png
672 ms
107.png
674 ms
HP-red.png
675 ms
25_3.png
675 ms
00_1.png
676 ms
21_2.png
674 ms
01_1.png
674 ms
09_1.png
675 ms
PV-red.png
679 ms
13_3.png
683 ms
PA-red.png
677 ms
13_1.png
674 ms
13_2.png
674 ms
reno.png
674 ms
lacatoni.png
678 ms
luso.png
677 ms
hotelluso.png
681 ms
ribbon.png
679 ms
fpp.pt accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fpp.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fpp.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fpp.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 Fpp.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.
fpp.pt
Open Graph data is detected on the main page of FPP. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: