Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

fep.pt

FEP, Federação Equestre Portuguesa, Competições, Saltos, C.C.E., Ensino

Page Load Speed

3.2 sec in total

First Response

279 ms

Resources Loaded

2.6 sec

Page Rendered

317 ms

fep.pt screenshot

About Website

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

Key Findings

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

Performance Metrics

fep.pt performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.294

40/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

fep.pt

279 ms

www.fep.pt

680 ms

css

191 ms

js

380 ms

js

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 Optimization Overview & Recommendations

Page size can be reduced by 199.2 kB (12%)

Content Size

1.6 MB

After Optimization

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.

HTML Optimization

-85%

Potential reduce by 65.8 kB

  • Original 77.6 kB
  • After minification 56.8 kB
  • After compression 11.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.

Image Optimization

-13%

Potential reduce by 112.7 kB

  • Original 883.4 kB
  • After minification 770.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.

JavaScript Optimization

-4%

Potential reduce by 20.7 kB

  • Original 574.2 kB
  • After minification 574.0 kB
  • After compression 553.5 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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 60.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.

Requests Breakdown

Number of requests can be reduced by 27 (34%)

Requests Now

80

After Optimization

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.

Accessibility Review

fep.pt accessibility score

86

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fep.pt best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fep.pt SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

Social Sharing Optimization

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: