Tools & Wizards About Us
vigo.org screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

vigo.org

Concello de Vigo. Web oficial da cidade de Vigo

Page Load Speed

9.1 sec in total

First Response

1.9 sec

Resources Loaded

6.9 sec

Page Rendered

227 ms

vigo.org screenshot

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 1.9 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

vigo.org performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

vigo.org

1896 ms

hoxe.vigo.org

1808 ms

vigo4.css

644 ms

sede.css

626 ms

dhtml-horiz5.css

394 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vigo.org, 87% (81 requests) were made to Hoxe.vigo.org and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Vigo.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (47%)

Content Size

2.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 148.0 kB

  • Original 174.0 kB
  • After minification 133.9 kB
  • After compression 25.9 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 40.1 kB, which is 23% 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 148.0 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 43.2 kB

  • Original 979.6 kB
  • After minification 936.3 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. Vigo images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 525.1 kB

  • Original 779.2 kB
  • After minification 778.7 kB
  • After compression 254.1 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 525.1 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 448.7 kB

  • Original 541.6 kB
  • After minification 500.1 kB
  • After compression 92.9 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 448.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 87 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vigo.org

vigo.org

1896 ms

hoxe.vigo.org

hoxe.vigo.org

1808 ms

vigo4.css

vigo4.css

644 ms

sede.css

sede.css

626 ms

dhtml-horiz5.css

dhtml-horiz5.css

394 ms

hoxevigo8.css

hoxevigo8.css

546 ms

ui.tabs5.css

ui.tabs5.css

410 ms

font-awesome.min.css

font-awesome.min.css

912 ms

lightbox.css

lightbox.css

542 ms

rs_embhl_v2_gl_es.js

rs_embhl_v2_gl_es.js

1031 ms

layerslider.css

layerslider.css

1007 ms

jquery.js

jquery.js

1130 ms

greensock.js

greensock.js

1006 ms

layerslider.transitions.js

layerslider.transitions.js

864 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

1106 ms

jquery-ui.min.js

jquery-ui.min.js

1853 ms

jquery-ui.css

jquery-ui.css

1247 ms

bootstrap.min.js

bootstrap.min.js

1417 ms

bootstrap.min.css

bootstrap.min.css

1441 ms

hoxevigo9c.css

hoxevigo9c.css

1228 ms

ga.js

ga.js

31 ms

__utm.gif

__utm.gif

13 ms

collect

collect

70 ms

fnd_cabecra2.png

fnd_cabecra2.png

646 ms

LMnAW0JNYt4

LMnAW0JNYt4

136 ms

portescudovigo.gif

portescudovigo.gif

263 ms

cies.jpg

cies.jpg

1201 ms

turismo.jpg

turismo.jpg

952 ms

logoturismo.png

logoturismo.png

141 ms

raton_sede2.jpg

raton_sede2.jpg

133 ms

flechapeq.gif

flechapeq.gif

268 ms

tramites2.png

tramites2.png

283 ms

c_cidadans120.png

c_cidadans120.png

631 ms

personal.png

personal.png

401 ms

5.png

5.png

691 ms

perfil2.png

perfil2.png

535 ms

edictos.png

edictos.png

668 ms

convocatoria.png

convocatoria.png

740 ms

speaker.png

speaker.png

764 ms

3621159178834.jpg

3621159178834.jpg

805 ms

010.png

010.png

828 ms

15.jpg

15.jpg

868 ms

2861454591231.pgm

2861454591231.pgm

893 ms

2841435833095.jpg

2841435833095.jpg

935 ms

2741330594407.jpg

2741330594407.jpg

966 ms

2801375787630.gif

2801375787630.gif

990 ms

61078239001.jpg

61078239001.jpg

1146 ms

external_link.gif

external_link.gif

1110 ms

2001146139444.gif

2001146139444.gif

1111 ms

2641331715124.jpg

2641331715124.jpg

1250 ms

2671298031301.pgm

2671298031301.pgm

1114 ms

581271681185.jpg

581271681185.jpg

1230 ms

1241061815669.gif

1241061815669.gif

1230 ms

2541265290631.jpg

2541265290631.jpg

1248 ms

2571268121166.jpg

2571268121166.jpg

1394 ms

2661286532861.jpg

2661286532861.jpg

1318 ms

2681300708969.jpg

2681300708969.jpg

1336 ms

2691301403554.jpg

2691301403554.jpg

1362 ms

2731318592838.jpg

2731318592838.jpg

1357 ms

2411238590870.jpg

2411238590870.jpg

1376 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

63 ms

www-embed-player.js

www-embed-player.js

83 ms

skin.css

skin.css

1318 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1593 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

20 ms

ad_status.js

ad_status.js

39 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

71 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

83 ms

2461265007829.jpg

2461265007829.jpg

1226 ms

2511255952916.jpg

2511255952916.jpg

1239 ms

2531259738605.jpg

2531259738605.jpg

1236 ms

2621272450949.jpg

2621272450949.jpg

1126 ms

2701301905689.jpg

2701301905689.jpg

1038 ms

1771118310723.jpg

1771118310723.jpg

992 ms

2421240401003.jpg

2421240401003.jpg

1016 ms

2071149597476.jpg

2071149597476.jpg

988 ms

2431240905350.jpg

2431240905350.jpg

963 ms

1261061816175.gif

1261061816175.gif

955 ms

2231190795066.jpg

2231190795066.jpg

969 ms

1001052290783.gif

1001052290783.gif

979 ms

1641114074240.gif

1641114074240.gif

953 ms

2311213356701.jpg

2311213356701.jpg

927 ms

2261213356747.jpg

2261213356747.jpg

923 ms

1781120555107.gif

1781120555107.gif

923 ms

1971143624136.jpg

1971143624136.jpg

920 ms

banner_pc4.png

banner_pc4.png

941 ms

banner_pc2.png

banner_pc2.png

930 ms

LMnAW0JNYt4

LMnAW0JNYt4

64 ms

banner_pc.png

banner_pc.png

818 ms

bolo_blanco.gif

bolo_blanco.gif

824 ms

sep_listapie.gif

sep_listapie.gif

865 ms

blank.gif

blank.gif

853 ms

skin.png

skin.png

581 ms

Accessibility Review

vigo.org accessibility score

90

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-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

vigo.org SEO score

98

Search Engine Optimization Advices

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

    ISO-8859-1

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

vigo.org

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: