Tools & Wizards About Us
blancoynegromasivo.com.co screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

blancoynegromasivo.com.co

Blanco y Negro Masivo | Líderes en movilidad sostenible.

Page Load Speed

3.9 sec in total

First Response

106 ms

Resources Loaded

3.4 sec

Page Rendered

417 ms

blancoynegromasivo.com.co screenshot

About Website

Visit blancoynegromasivo.com.co now to see the best up-to-date Blanco Y Negro Masivo content for Colombia and also check out these interesting facts you probably never knew about blancoynegromasivo.com.co

Somos una empresa dedicada a la gestión y operación del sistema de Transporte Masivo de pasajeros en la ciudad de Cali.

Visit blancoynegromasivo.com.co

Key Findings

We analyzed Blancoynegromasivo.com.co page load time and found that the first response time was 106 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

blancoynegromasivo.com.co performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value3,020 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.321

36/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

blancoynegromasivo.com.co

106 ms

css

64 ms

gtranslate-style24.css

20 ms

style.min.css

40 ms

style.min.css

70 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 76% of them (122 requests) were addressed to the original Blancoynegromasivo.com.co, 21% (34 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (241 ms) belongs to the original domain Blancoynegromasivo.com.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 347.3 kB (42%)

Content Size

835.1 kB

After Optimization

487.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Blancoynegromasivo.com.co main page is 835.1 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. Only a small number of websites need less resources to load. Images take 602.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 192.3 kB

  • Original 229.9 kB
  • After minification 218.7 kB
  • After compression 37.6 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 192.3 kB or 84% of the original size.

Image Optimization

-26%

Potential reduce by 154.9 kB

  • Original 602.5 kB
  • After minification 447.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. Obviously, Blanco Y Negro Masivo needs image optimization as it can save up to 154.9 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 21 B

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 2.7 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 108 (87%)

Requests Now

124

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blancoynegromasivo.com.co

blancoynegromasivo.com.co

106 ms

css

css

64 ms

gtranslate-style24.css

gtranslate-style24.css

20 ms

style.min.css

style.min.css

40 ms

style.min.css

style.min.css

70 ms

style.min.css

style.min.css

57 ms

style.min.css

style.min.css

61 ms

style.min.css

style.min.css

62 ms

betterdocs-public.css

betterdocs-public.css

64 ms

simplebar.css

simplebar.css

75 ms

instant-answer.css

instant-answer.css

74 ms

betterdocs-pro-public.css

betterdocs-pro-public.css

75 ms

styles.css

styles.css

76 ms

pageloader.css

pageloader.css

80 ms

rs6.css

rs6.css

80 ms

font-awesome.min.css

font-awesome.min.css

49 ms

sogo-accessibility-public.css

sogo-accessibility-public.css

83 ms

style.css

style.css

84 ms

wpa-style.css

wpa-style.css

86 ms

a11y-toolbar.css

a11y-toolbar.css

88 ms

a11y.css

a11y.css

92 ms

a11y-fontsize.css

a11y-fontsize.css

91 ms

style.css

style.css

132 ms

style.min.css

style.min.css

95 ms

style.min.css

style.min.css

114 ms

dashicons.min.css

dashicons.min.css

128 ms

jetpack.css

jetpack.css

104 ms

jquery.js

jquery.js

129 ms

jquery-migrate.min.js

jquery-migrate.min.js

112 ms

imagesloaded.min.js

imagesloaded.min.js

186 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

188 ms

jquery.throttle.debounce.min.js

jquery.throttle.debounce.min.js

189 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

190 ms

public.js

public.js

192 ms

responsive_preview.js

responsive_preview.js

193 ms

pageloader.js

pageloader.js

194 ms

element.js

element.js

67 ms

e-202425.js

e-202425.js

29 ms

et-core-unified-tb-5406-137-17183236413581.min.css

et-core-unified-tb-5406-137-17183236413581.min.css

190 ms

et-core-unified-137-17183236413581.min.css

et-core-unified-137-17183236413581.min.css

189 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

167 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

148 ms

style.css

style.css

148 ms

rbtools.min.js

rbtools.min.js

148 ms

rs6.min.js

rs6.min.js

169 ms

main.js

main.js

143 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

138 ms

recaptcha.js

recaptcha.js

135 ms

masonry.min.js

masonry.min.js

155 ms

clipboard.min.js

clipboard.min.js

174 ms

betterdocs-public.js

betterdocs-public.js

174 ms

simplebar.js

simplebar.js

174 ms

wp-polyfill.min.js

wp-polyfill.min.js

171 ms

i18n.min.js

i18n.min.js

168 ms

lodash.min.js

lodash.min.js

169 ms

react.min.js

react.min.js

168 ms

react-dom.min.js

react-dom.min.js

186 ms

escape-html.min.js

escape-html.min.js

164 ms

element.min.js

element.min.js

175 ms

hooks.min.js

hooks.min.js

176 ms

underscore.min.js

underscore.min.js

171 ms

wp-util.min.js

wp-util.min.js

158 ms

moment.min.js

moment.min.js

158 ms

dom-ready.min.js

dom-ready.min.js

144 ms

a11y.min.js

a11y.min.js

142 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

85 ms

compose.min.js

compose.min.js

85 ms

deprecated.min.js

deprecated.min.js

86 ms

dom.min.js

dom.min.js

86 ms

keycodes.min.js

keycodes.min.js

86 ms

primitives.min.js

primitives.min.js

83 ms

priority-queue.min.js

priority-queue.min.js

84 ms

redux-routine.min.js

redux-routine.min.js

82 ms

data.min.js

data.min.js

82 ms

rich-text.min.js

rich-text.min.js

82 ms

warning.min.js

warning.min.js

82 ms

components.min.js

components.min.js

109 ms

instant-answer.js

instant-answer.js

85 ms

betterdocs-pro-public.js

betterdocs-pro-public.js

80 ms

scripts.js

scripts.js

80 ms

navigation.js

navigation.js

81 ms

sogo-accessibility-public.js

sogo-accessibility-public.js

62 ms

wpa-toolbar.js

wpa-toolbar.js

62 ms

a11y.js

a11y.js

43 ms

wpa.labels.js

wpa.labels.js

42 ms

longdesc.button.js

longdesc.button.js

42 ms

current-menu-item.js

current-menu-item.js

57 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

57 ms

custom.unified.js

custom.unified.js

79 ms

frontend-bundle.min.js

frontend-bundle.min.js

55 ms

frontend-bundle.min.js

frontend-bundle.min.js

55 ms

common.js

common.js

55 ms

wp-embed.min.js

wp-embed.min.js

42 ms

vanilla-tilt.min.js

vanilla-tilt.min.js

42 ms

frontend.min.js

frontend.min.js

41 ms

lottie.min.js

lottie.min.js

42 ms

frontend.min.js

frontend.min.js

58 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

74 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

73 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

73 ms

swiper.min.js

swiper.min.js

72 ms

frontend.min.js

frontend.min.js

71 ms

elfsight-facebook-feed.js

elfsight-facebook-feed.js

70 ms

jquery.uniform.min.js

jquery.uniform.min.js

157 ms

custom.js

custom.js

158 ms

idle-timer.min.js

idle-timer.min.js

155 ms

Logo-BYN-SVG-02.svg

Logo-BYN-SVG-02.svg

154 ms

transparent.png

transparent.png

153 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

57 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

147 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

146 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

235 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

234 ms

modules.ttf

modules.ttf

178 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

118 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

90 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

178 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

178 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

178 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

179 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

178 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

180 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

179 ms

Fondo-byn.jpg

Fondo-byn.jpg

113 ms

Nuesta-Flota.jpg

Nuesta-Flota.jpg

117 ms

Banner-inferior.jpg

Banner-inferior.jpg

118 ms

whatsapp_logo.svg

whatsapp_logo.svg

114 ms

x_icon.svg

x_icon.svg

114 ms

whatsapp_logo_green.svg

whatsapp_logo_green.svg

115 ms

Logo-Byn-Cuadrado.jpg

Logo-Byn-Cuadrado.jpg

116 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

69 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf

71 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

70 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8Jow.ttf

68 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8Jow.ttf

69 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf

70 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

71 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

72 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8Jow.ttf

71 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8Jow.ttf

73 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

72 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

72 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

75 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

73 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

75 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

77 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

75 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

76 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

77 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

74 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

69 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

70 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

70 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

79 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

80 ms

Personaje-1.png

Personaje-1.png

241 ms

en-us.png

en-us.png

237 ms

fr.png

fr.png

238 ms

es.png

es.png

239 ms

Logo-Blanco-y-Negro-Masivo.jpg

Logo-Blanco-y-Negro-Masivo.jpg

241 ms

Accessibility Review

blancoynegromasivo.com.co accessibility score

82

Accessibility Issues

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

Links do not have a discernible name

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

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.

Best Practices

blancoynegromasivo.com.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

blancoynegromasivo.com.co SEO score

79

Search Engine Optimization Advices

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 Blancoynegromasivo.com.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 Blancoynegromasivo.com.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

blancoynegromasivo.com.co

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