Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

goteo.org

Goteo.org :: Crowdfunding the commons

Page Load Speed

4 sec in total

First Response

260 ms

Resources Loaded

3.2 sec

Page Rendered

558 ms

goteo.org screenshot

About Website

Visit goteo.org now to see the best up-to-date Goteo content for Spain and also check out these interesting facts you probably never knew about goteo.org

Goteo is an open network for crowdfunding, collaborations and training, leader in social innovation. With 2 rounds and fiscal advantages for donors!

Visit goteo.org

Key Findings

We analyzed Goteo.org page load time and found that the first response time was 260 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

goteo.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value22.9 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value2,850 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.248

50/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

goteo.org

260 ms

en.goteo.org

578 ms

all.css

617 ms

jquery-1.6.4.min.js

477 ms

jquery.fancybox.min.js

286 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Goteo.org, 42% (57 requests) were made to Data.goteo.org and 41% (55 requests) were made to Assets.goteo.org. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Data.goteo.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (21%)

Content Size

5.1 MB

After Optimization

4.0 MB

In fact, the total size of Goteo.org main page is 5.1 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. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 97.4 kB

  • Original 119.7 kB
  • After minification 100.0 kB
  • After compression 22.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 19.7 kB, which is 16% 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 97.4 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 243.3 kB

  • Original 4.0 MB
  • After minification 3.8 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. Goteo images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 272.9 kB

  • Original 427.3 kB
  • After minification 415.3 kB
  • After compression 154.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 272.9 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 444.7 kB

  • Original 528.1 kB
  • After minification 527.9 kB
  • After compression 83.4 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. Goteo.org needs all CSS files to be minified and compressed as it can save up to 444.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (32%)

Requests Now

130

After Optimization

89

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

Accessibility Review

goteo.org accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA progressbar elements do not have accessible names.

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

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

Displays images with incorrect aspect ratio

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goteo.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Goteo.org 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 data is detected on the main page of Goteo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: