Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fgf-gff.org

Gipuzkoako Futbol Federazioa - GFF | Txapelketak, klubak, albisteak

Page Load Speed

7.9 sec in total

First Response

321 ms

Resources Loaded

6.1 sec

Page Rendered

1.5 sec

fgf-gff.org screenshot

About Website

Click here to check amazing Fgf GFF content for Spain. Otherwise, check out these important facts you probably never knew about fgf-gff.org

FGF-GFF Gipuzkoako Futbola Federazioaren webgune ofiziala. Futbol txapelketa guztien emaitzak eta sailakapenak, klubak, zelaiak, albisteak.

Visit fgf-gff.org

Key Findings

We analyzed Fgf-gff.org page load time and found that the first response time was 321 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fgf-gff.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value6,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

fgf-gff.org

321 ms

index.asp

1131 ms

reset.css

274 ms

header-footer.css

379 ms

style.css

855 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 78% of them (53 requests) were addressed to the original Fgf-gff.org, 6% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Fgf-gff.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 402.3 kB (25%)

Content Size

1.6 MB

After Optimization

1.2 MB

In fact, the total size of Fgf-gff.org 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 51.4 kB

  • Original 62.6 kB
  • After minification 53.2 kB
  • After compression 11.1 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 9.4 kB, which is 15% 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 51.4 kB or 82% of the original size.

Image Optimization

-10%

Potential reduce by 115.2 kB

  • Original 1.2 MB
  • After minification 1.1 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. Fgf GFF images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 82.8 kB

  • Original 140.2 kB
  • After minification 137.8 kB
  • After compression 57.4 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 82.8 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 152.9 kB

  • Original 179.3 kB
  • After minification 161.0 kB
  • After compression 26.3 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. Fgf-gff.org needs all CSS files to be minified and compressed as it can save up to 152.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (31%)

Requests Now

62

After Optimization

43

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fgf GFF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

fgf-gff.org accessibility score

89

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

fgf-gff.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

fgf-gff.org SEO score

86

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

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

    EU

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fgf-gff.org can be misinterpreted by Google and other search engines. Our service has detected that Basque 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 Fgf-gff.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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