Tools & Wizards About Us

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

flowingly.io

Flowingly | Process & Workflow Software For Teams

Page Load Speed

8.3 sec in total

First Response

449 ms

Resources Loaded

6.6 sec

Page Rendered

1.2 sec

About Website

Welcome to flowingly.io homepage info - get ready to check Flowingly best content right away, or after learning these important things about flowingly.io

Unlock Team Productivity. Streamline Approvals. Increase Compliance. Easy To Use, No-Code Process Mapping & Workflow Automation Platform.

Visit flowingly.io

Key Findings

We analyzed Flowingly.io page load time and found that the first response time was 449 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

flowingly.io performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value5,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.512

15/100

15%

TTI (Time to Interactive)

Value31.8 s

0/100

10%

Network Requests Diagram

flowingly.io

449 ms

flowingly.io

1382 ms

front.min.css

24 ms

swiper-bundle.min.css

35 ms

font-awesome.min.css

33 ms

Our browser made a total of 173 requests to load all elements on the main page. We found that 46% of them (79 requests) were addressed to the original Flowingly.io, 23% (39 requests) were made to Fonts.gstatic.com and 14% (25 requests) were made to Assets.storylane.io. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Flowingly.io.

Page Optimization Overview & Recommendations

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

Content Size

10.6 MB

After Optimization

10.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flowingly.io main page is 10.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.1 MB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 331.8 kB

  • Original 514.3 kB
  • After minification 506.8 kB
  • After compression 182.5 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 331.8 kB or 65% of the original size.

Image Optimization

-3%

Potential reduce by 280.2 kB

  • Original 9.1 MB
  • After minification 8.8 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. Flowingly images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 13.2 kB

  • Original 856.7 kB
  • After minification 856.7 kB
  • After compression 843.6 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

-3%

Potential reduce by 4.0 kB

  • Original 150.5 kB
  • After minification 148.5 kB
  • After compression 146.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. Flowingly.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 84 (69%)

Requests Now

122

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

flowingly.io accessibility score

85

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

flowingly.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

flowingly.io SEO score

89

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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