3.2 sec in total
279 ms
2.6 sec
317 ms
Click here to check amazing FEP content for Portugal. Otherwise, check out these important facts you probably never knew about fep.pt
Site Institucional da FEP - Federação Equestre Portuguesa. A FEP - Federação Equestre Portuguesa foi fundada em 1927, e obteve o reconhecimento como entidade de utilidade pública desportiva em 1977. R...
Visit fep.ptWe analyzed Fep.pt page load time and found that the first response time was 279 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fep.pt performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value10.4 s
0/100
25%
Value7.4 s
28/100
10%
Value550 ms
54/100
30%
Value0.294
40/100
15%
Value12.5 s
14/100
10%
279 ms
680 ms
191 ms
380 ms
85 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 84% of them (73 requests) were addressed to the original Fep.pt, 5% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (854 ms) belongs to the original domain Fep.pt.
Page size can be reduced by 199.2 kB (12%)
1.6 MB
1.4 MB
In fact, the total size of Fep.pt main page is 1.6 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. 65% of websites need less resources to load. Images take 883.4 kB which makes up the majority of the site volume.
Potential reduce by 65.8 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 20.8 kB, which is 27% 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 65.8 kB or 85% of the original size.
Potential reduce by 112.7 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. Obviously, FEP needs image optimization as it can save up to 112.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 20.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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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.
Number of requests can be reduced by 27 (34%)
80
53
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fep.pt
279 ms
www.fep.pt
680 ms
css
191 ms
js
380 ms
js
85 ms
WebResource.axd
374 ms
ScriptResource.axd
500 ms
ScriptResource.axd
375 ms
js
557 ms
scripts.js
376 ms
js
506 ms
fileHelper.js
498 ms
js
574 ms
application.js
508 ms
jquery.fep-tab.js
573 ms
js
652 ms
jquery.validate.min.js
584 ms
jquery.validate.unobtrusive.min.js
584 ms
globalize.js
684 ms
globalize.culture.pt-PT.js
649 ms
jquery.validate.globalize.js
683 ms
app.js
682 ms
Utilities.js
683 ms
api.js
52 ms
css
54 ms
css
70 ms
addthis_widget.js
64 ms
cookieconsent.min.js
49 ms
ga.js
88 ms
Logo_v2.png
361 ms
142.png
358 ms
150.png
357 ms
162.png
358 ms
171.png
358 ms
181.png
361 ms
188.png
423 ms
196.png
422 ms
204.png
422 ms
368.png
422 ms
100.png
422 ms
Icons_Obstaculos.png
425 ms
Icons_Volteio.png
514 ms
Icons_Trabalho.png
512 ms
Icons_TREC.png
512 ms
Icons_Atrelagem.png
511 ms
Icons_CCE.png
513 ms
Icons_Ensino.png
514 ms
Icons_Raides.png
603 ms
Icons_Horseball.png
603 ms
carousel.jpg
854 ms
ipdj.png
525 ms
fei.png
526 ms
fei_cleansports.png
527 ms
__utm.gif
18 ms
eef.png
587 ms
igeq.png
553 ms
RSS.ashx
568 ms
logo_ADoP.png
536 ms
Logo%20Haier_Inverted.jpg
546 ms
partner.png
624 ms
142.png
562 ms
150.png
536 ms
162.png
538 ms
171.png
557 ms
181.png
617 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
51 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
51 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
52 ms
fontawesome-webfont.woff
712 ms
recaptcha__en.js
64 ms
188.png
541 ms
196.png
540 ms
204.png
555 ms
368.png
613 ms
100.png
635 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
65 ms
1.jpg
635 ms
2.jpg
574 ms
3.jpg
583 ms
4.jpg
641 ms
Add1.jpg
646 ms
Ensino.png
657 ms
Obstaculos.png
640 ms
search.png
568 ms
MediaHandler.ashx
366 ms
MediaHandler.ashx
425 ms
light-bottom.css
14 ms
fep.pt accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fep.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
fep.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Fep.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 Fep.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.
fep.pt
Open Graph description is not detected on the main page of FEP. 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: