Tools & Wizards About Us
flow.cl screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

flow.cl

Flow - Plataforma de pagos online - Chile

Page Load Speed

754 ms in total

First Response

28 ms

Resources Loaded

457 ms

Page Rendered

269 ms

flow.cl screenshot

About Website

Click here to check amazing Flow content for Chile. Otherwise, check out these important facts you probably never knew about flow.cl

Flow es una plataforma de pagos online que te permite emitir y recibir pagos electrónicos vía múltiples medios de pago

Visit flow.cl

Key Findings

We analyzed Flow.cl page load time and found that the first response time was 28 ms and then it took 726 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

flow.cl performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value3.0 s

93/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

flow.cl

28 ms

www.flow.cl

154 ms

gtm.js

66 ms

bootstrap.3.3.7.min.css

47 ms

forms.css

96 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 79% of them (44 requests) were addressed to the original Flow.cl, 14% (8 requests) were made to Resources.flow.cl and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (234 ms) belongs to the original domain Flow.cl.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.2 kB (6%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flow.cl main page is 1.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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 79.3 kB

  • Original 107.2 kB
  • After minification 96.6 kB
  • After compression 28.0 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 79.3 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 15.5 kB

  • Original 1.3 MB
  • After minification 1.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. Flow images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 66 B

  • Original 48.9 kB
  • After minification 48.9 kB
  • After compression 48.8 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.

CSS Optimization

-1%

Potential reduce by 450 B

  • Original 33.0 kB
  • After minification 33.0 kB
  • After compression 32.5 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. Flow.cl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (25%)

Requests Now

51

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flow.cl

flow.cl

28 ms

www.flow.cl

www.flow.cl

154 ms

gtm.js

gtm.js

66 ms

bootstrap.3.3.7.min.css

bootstrap.3.3.7.min.css

47 ms

forms.css

forms.css

96 ms

flow.css

flow.css

99 ms

menu.css

menu.css

90 ms

footer.css

footer.css

99 ms

font-awesome.4.7.0.min.css

font-awesome.4.7.0.min.css

95 ms

css

css

46 ms

inicio.css

inicio.css

97 ms

lightslider.min.css

lightslider.min.css

99 ms

jun24-cuotas-d.jpg

jun24-cuotas-d.jpg

208 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

119 ms

bootstrap.3.3.7.min.js

bootstrap.3.3.7.min.js

116 ms

lightslider.min.js

lightslider.min.js

115 ms

home.js

home.js

108 ms

footer.js

footer.js

115 ms

logo-flow.svg

logo-flow.svg

202 ms

link-pago.svg

link-pago.svg

210 ms

carro-compra.svg

carro-compra.svg

212 ms

mall.svg

mall.svg

214 ms

venta-presencial.svg

venta-presencial.svg

217 ms

redes-sociales.svg

redes-sociales.svg

215 ms

soluciones-empresariales.svg

soluciones-empresariales.svg

218 ms

forma-recurrente.svg

forma-recurrente.svg

221 ms

web-sistema.svg

web-sistema.svg

221 ms

reembolso.svg

reembolso.svg

222 ms

info-tecnica2.svg

info-tecnica2.svg

227 ms

info-tecnica.svg

info-tecnica.svg

225 ms

conveniente.svg

conveniente.svg

223 ms

agil.svg

agil.svg

227 ms

seguro.svg

seguro.svg

229 ms

webpay.png

webpay.png

230 ms

servipag.png

servipag.png

230 ms

multicaja.png

multicaja.png

231 ms

mach.png

mach.png

230 ms

redpay.png

redpay.png

231 ms

ver-todos.png

ver-todos.png

231 ms

chek.png

chek.png

232 ms

jun24-cuotas-m.jpg

jun24-cuotas-m.jpg

210 ms

jun24-faq-d.jpg

jun24-faq-d.jpg

203 ms

jun24-faq-m.jpg

jun24-faq-m.jpg

205 ms

jun24-flowpay-d.jpg

jun24-flowpay-d.jpg

215 ms

jun24-flowpay-m.jpg

jun24-flowpay-m.jpg

205 ms

jun24-pagospe-d.jpg

jun24-pagospe-d.jpg

213 ms

jun24-pagospe-m.jpg

jun24-pagospe-m.jpg

223 ms

sitelock.png

sitelock.png

234 ms

logo-pci-flow.png

logo-pci-flow.png

193 ms

premio_ecommerce_award_98x56.png

premio_ecommerce_award_98x56.png

159 ms

fondo-flow.jpg

fondo-flow.jpg

172 ms

bloque2.jpg

bloque2.jpg

156 ms

controls.png

controls.png

44 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

44 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

54 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

52 ms

Accessibility Review

flow.cl accessibility score

75

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

Image elements do not have [alt] attributes

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

flow.cl best practices score

83

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

SEO Factors

flow.cl SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Flow.cl 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 Flow.cl 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

flow.cl

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