Tools & Wizards About Us
santander.gov.co screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

santander.gov.co

Sede Electrónica de la Gobernación de Santander

Page Load Speed

3.4 sec in total

First Response

670 ms

Resources Loaded

1.4 sec

Page Rendered

1.3 sec

santander.gov.co screenshot

About Website

Click here to check amazing Santander content for Colombia. Otherwise, check out these important facts you probably never knew about santander.gov.co

Sede Electrónica de la Gobernación de Santander que reúne todos los trámites y servicios en línea para los ciudadanos

Visit santander.gov.co

Key Findings

We analyzed Santander.gov.co page load time and found that the first response time was 670 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

santander.gov.co performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

79/100

10%

LCP (Largest Contentful Paint)

Value20.6 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value9,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.509

16/100

15%

TTI (Time to Interactive)

Value29.5 s

0/100

10%

Network Requests Diagram

santander.gov.co

670 ms

jquery_cookie.js

37 ms

functions.min.js

44 ms

functions_home.min.js

36 ms

logo_gov_co.png

46 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 21% of them (14 requests) were addressed to the original Santander.gov.co, 50% (34 requests) were made to Static.cdninstagram.com and 18% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (670 ms) belongs to the original domain Santander.gov.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.4 kB (32%)

Content Size

475.7 kB

After Optimization

321.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Santander.gov.co main page is 475.7 kB. 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 334.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 122.3 kB

  • Original 138.6 kB
  • After minification 105.9 kB
  • After compression 16.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 32.7 kB, which is 24% 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 122.3 kB or 88% of the original size.

Image Optimization

-9%

Potential reduce by 31.5 kB

  • Original 334.0 kB
  • After minification 302.5 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. Santander images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 609 B

  • Original 3.0 kB
  • After minification 3.0 kB
  • After compression 2.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 609 B or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (67%)

Requests Now

67

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

santander.gov.co

santander.gov.co

670 ms

jquery_cookie.js

jquery_cookie.js

37 ms

functions.min.js

functions.min.js

44 ms

functions_home.min.js

functions_home.min.js

36 ms

logo_gov_co.png

logo_gov_co.png

46 ms

bloqueheader5085.png

bloqueheader5085.png

43 ms

1400x920.gif

1400x920.gif

43 ms

400x400.gif

400x400.gif

72 ms

1200x400.gif

1200x400.gif

72 ms

cargando.gif

cargando.gif

85 ms

200x200.gif

200x200.gif

85 ms

bloquefooder5087.png

bloquefooder5087.png

101 ms

logo-colombia.svg

logo-colombia.svg

77 ms

logo-govco-footer.svg

logo-govco-footer.svg

105 ms

page.php

page.php

103 ms

578 ms

0CbgYal93sn.css

0CbgYal93sn.css

14 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

21 ms

xjg1QNQguf-.js

xjg1QNQguf-.js

44 ms

eQ3e44cCeXh.js

eQ3e44cCeXh.js

45 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

19 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

50 ms

p55HfXW__mM.js

p55HfXW__mM.js

48 ms

G95XClHFDrT.js

G95XClHFDrT.js

52 ms

q5lR_mVVI9t.js

q5lR_mVVI9t.js

48 ms

438275014_764960355761713_4485998332928544274_n.jpg

438275014_764960355761713_4485998332928544274_n.jpg

44 ms

554t-O9EjCU.js

554t-O9EjCU.js

10 ms

4Za9TE_Wiy4.js

4Za9TE_Wiy4.js

10 ms

416158272_696206189303797_7447556538554431512_n.jpg

416158272_696206189303797_7447556538554431512_n.jpg

18 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

6 ms

8fhWdj8G4So.css

8fhWdj8G4So.css

21 ms

4wodkHgz95w.css

4wodkHgz95w.css

26 ms

snKx9A7Oph7.css

snKx9A7Oph7.css

37 ms

JCnGKbSmOoI.css

JCnGKbSmOoI.css

40 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

44 ms

416338427_1047099793223901_3627588230462946670_n.jpg

416338427_1047099793223901_3627588230462946670_n.jpg

31 ms

p55HfXW__mM.js

p55HfXW__mM.js

16 ms

f6KaEh61WWT.js

f6KaEh61WWT.js

17 ms

oNTNBe5bTAQ.js

oNTNBe5bTAQ.js

18 ms

uxCgKtj0hr3.js

uxCgKtj0hr3.js

19 ms

iqfdoYyqQ9O.js

iqfdoYyqQ9O.js

24 ms

cEM8HumdxpH.js

cEM8HumdxpH.js

27 ms

Fr4HmeXv7jo.js

Fr4HmeXv7jo.js

28 ms

0yactC7tM6g.js

0yactC7tM6g.js

32 ms

kLfY7stKZT-.js

kLfY7stKZT-.js

34 ms

oTfO5Z4us6k.js

oTfO5Z4us6k.js

34 ms

LKe0QsbLPt9.js

LKe0QsbLPt9.js

34 ms

S4NkjxS2EE7.js

S4NkjxS2EE7.js

33 ms

J1VbMx8qJ8X.js

J1VbMx8qJ8X.js

35 ms

wVwiWkGNqwG.js

wVwiWkGNqwG.js

34 ms

-7gfuo3bx25.js

-7gfuo3bx25.js

45 ms

4eTYn9pxF9T.js

4eTYn9pxF9T.js

46 ms

FeYbAhiQLN7.js

FeYbAhiQLN7.js

47 ms

HrjVc9-xUhR.js

HrjVc9-xUhR.js

46 ms

GIlJjyzEguQ.js

GIlJjyzEguQ.js

44 ms

t1rKC1fVSR_.js

t1rKC1fVSR_.js

47 ms

5-CNhD1hzUM.js

5-CNhD1hzUM.js

48 ms

HDiX03ZTkcn.js

HDiX03ZTkcn.js

47 ms

ieEpjC_gTvk.js

ieEpjC_gTvk.js

52 ms

d4BDatS3XIp.js

d4BDatS3XIp.js

50 ms

JaMJqU2pGNO.js

JaMJqU2pGNO.js

50 ms

izc1ABDFhxb.js

izc1ABDFhxb.js

48 ms

IbEU6o3x0eh.js

IbEU6o3x0eh.js

48 ms

KyCDJh5Z2FZ.js

KyCDJh5Z2FZ.js

47 ms

437041018_25158305413784429_1451331601584418777_n.jpg

437041018_25158305413784429_1451331601584418777_n.jpg

70 ms

442461605_457421023451131_251993201364970947_n.heic

442461605_457421023451131_251993201364970947_n.heic

90 ms

442431651_971972411244399_5507899921364179471_n.jpg

442431651_971972411244399_5507899921364179471_n.jpg

64 ms

vdsCkHHQ_Yz.png

vdsCkHHQ_Yz.png

48 ms

Accessibility Review

santander.gov.co accessibility score

81

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

santander.gov.co best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

santander.gov.co SEO score

91

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Santander.gov.co can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Santander.gov.co 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

santander.gov.co

Open Graph data is detected on the main page of Santander. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: