Tools & Wizards About Us
flowcards.io screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

flowcards.io

UI Flow Cards ― Construct web pages with ease, using UI Flow Cards

Page Load Speed

3 sec in total

First Response

272 ms

Resources Loaded

2 sec

Page Rendered

766 ms

flowcards.io screenshot

About Website

Visit flowcards.io now to see the best up-to-date Flow Cards content and also check out these interesting facts you probably never knew about flowcards.io

163 neatly organized UI Flow Cards, contain all the different wireframes you need to construct web pages. In Figma, Sketch and Adobe Illustrator formats.

Visit flowcards.io

Key Findings

We analyzed Flowcards.io page load time and found that the first response time was 272 ms and then it took 2.7 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

flowcards.io performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value2,260 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.669

8/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

flowcards.io

272 ms

flowcards.io

587 ms

bootstrap.min.css

471 ms

style.css

436 ms

css

145 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 43% of them (9 requests) were addressed to the original Flowcards.io, 19% (4 requests) were made to Assets.gumroad.com and 14% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (590 ms) belongs to the original domain Flowcards.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.8 kB (73%)

Content Size

364.6 kB

After Optimization

99.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flowcards.io main page is 364.6 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. 40% of websites need less resources to load. CSS take 178.8 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 50.6 kB

  • Original 56.5 kB
  • After minification 47.1 kB
  • After compression 5.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 9.3 kB, which is 17% 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 50.6 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 95 B
  • After minification 95 B

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 Cards images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 70.6 kB

  • Original 129.2 kB
  • After minification 129.2 kB
  • After compression 58.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 70.6 kB or 55% of the original size.

CSS Optimization

-80%

Potential reduce by 143.6 kB

  • Original 178.8 kB
  • After minification 176.4 kB
  • After compression 35.2 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. Flowcards.io needs all CSS files to be minified and compressed as it can save up to 143.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (71%)

Requests Now

14

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flowcards.io

flowcards.io

272 ms

flowcards.io

flowcards.io

587 ms

bootstrap.min.css

bootstrap.min.css

471 ms

style.css

style.css

436 ms

css

css

145 ms

js

js

194 ms

gumroad.js

gumroad.js

418 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

590 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

589 ms

blocs.min.js

blocs.min.js

533 ms

lazysizes.min.js

lazysizes.min.js

534 ms

analytics.js

analytics.js

157 ms

lazyload-ph.png

lazyload-ph.png

166 ms

overlay-a916235d43d9d7113b92.js

overlay-a916235d43d9d7113b92.js

493 ms

overlay-9325a7da.css

overlay-9325a7da.css

337 ms

collect

collect

38 ms

2sDfZG1Wl4LcnbuKgE0g.woff

2sDfZG1Wl4LcnbuKgE0g.woff

190 ms

2sDcZG1Wl4LcnbuCJW8zZmW_.woff

2sDcZG1Wl4LcnbuCJW8zZmW_.woff

190 ms

2sDcZG1Wl4LcnbuCNWgzZmW_.woff

2sDcZG1Wl4LcnbuCNWgzZmW_.woff

191 ms

19db990205089207b039.woff2

19db990205089207b039.woff2

63 ms

f301b7100da17db3c2c0.woff2

f301b7100da17db3c2c0.woff2

61 ms

Accessibility Review

flowcards.io accessibility score

76

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

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

High

Links do not have a discernible name

Best Practices

flowcards.io best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

flowcards.io SEO score

92

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

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

flowcards.io

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