Tools & Wizards About Us

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

vigo.org

Concello de Vigo. Web oficial da cidade de Vigo

Page Load Speed

6 sec in total

First Response

350 ms

Resources Loaded

4.4 sec

Page Rendered

1.3 sec

About Website

Click here to check amazing Vigo content for Spain. Otherwise, check out these important facts you probably never knew about vigo.org

A Web oficial de Vigo, creada polo Concello de Vigo.

Visit vigo.org

Key Findings

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

Performance Metrics

vigo.org performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

vigo.org

350 ms

hoxe.vigo.org

1297 ms

matomo.js

780 ms

css

49 ms

font-awesome.min.css

419 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vigo.org, 55% (60 requests) were made to Hoxe.vigo.org and 20% (22 requests) were made to Axenda-files.vigo.org. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Axenda-files.vigo.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (14%)

Content Size

8.8 MB

After Optimization

7.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vigo.org main page is 8.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. 65% of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 203.4 kB

  • Original 232.7 kB
  • After minification 182.8 kB
  • After compression 29.3 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 49.8 kB, which is 21% 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 203.4 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 550.3 kB

  • Original 7.8 MB
  • After minification 7.3 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. Vigo images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 257.3 kB

  • Original 466.3 kB
  • After minification 436.6 kB
  • After compression 209.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 257.3 kB or 55% of the original size.

CSS Optimization

-85%

Potential reduce by 247.1 kB

  • Original 289.6 kB
  • After minification 215.3 kB
  • After compression 42.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. Vigo.org needs all CSS files to be minified and compressed as it can save up to 247.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (26%)

Requests Now

92

After Optimization

68

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

vigo.org accessibility score

96

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

Links do not have a discernible name

Best Practices

vigo.org best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

vigo.org SEO score

90

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

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

    GL

  • Language Claimed

    GL

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vigo.org can be misinterpreted by Google and other search engines. Our service has detected that Galician is used on the page, and it matches the claimed language. Our system also found out that Vigo.org main page’s claimed encoding is windows-1252. 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 Vigo. 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: