Tools & Wizards About Us
flowlab.io screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

flowlab.io

Flowlab Game Creator - Make games online

Page Load Speed

1.6 sec in total

First Response

93 ms

Resources Loaded

1.2 sec

Page Rendered

290 ms

flowlab.io screenshot

About Website

Visit flowlab.io now to see the best up-to-date Flowlab content for United States and also check out these interesting facts you probably never knew about flowlab.io

Flowlab is an online game creator. Make your own games to share with friends.

Visit flowlab.io

Key Findings

We analyzed Flowlab.io page load time and found that the first response time was 93 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

flowlab.io performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value4.9 s

64/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

flowlab.io

93 ms

bootstrap.css

35 ms

general.css

31 ms

builder.css

29 ms

css

52 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 30% of them (17 requests) were addressed to the original Flowlab.io, 23% (13 requests) were made to Pbs.twimg.com and 5% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (597 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 781.6 kB (48%)

Content Size

1.6 MB

After Optimization

847.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flowlab.io main page is 1.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. 60% of websites need less resources to load. Images take 674.0 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 24.9 kB

  • Original 35.1 kB
  • After minification 29.8 kB
  • After compression 10.3 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 5.4 kB, which is 15% 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 24.9 kB or 71% of the original size.

Image Optimization

-16%

Potential reduce by 107.9 kB

  • Original 674.0 kB
  • After minification 566.0 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, Flowlab needs image optimization as it can save up to 107.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 344.1 kB

  • Original 553.5 kB
  • After minification 553.2 kB
  • After compression 209.3 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 344.1 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 304.6 kB

  • Original 366.5 kB
  • After minification 363.9 kB
  • After compression 61.9 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. Flowlab.io needs all CSS files to be minified and compressed as it can save up to 304.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (38%)

Requests Now

55

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flowlab.io

flowlab.io

93 ms

bootstrap.css

bootstrap.css

35 ms

general.css

general.css

31 ms

builder.css

builder.css

29 ms

css

css

52 ms

css

css

64 ms

css

css

73 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

31 ms

iframe_api

iframe_api

69 ms

swfobject.js

swfobject.js

30 ms

www-widgetapi.js

www-widgetapi.js

118 ms

ga.js

ga.js

61 ms

bg.png

bg.png

59 ms

all.js

all.js

311 ms

WodYrRIb.jpeg

WodYrRIb.jpeg

122 ms

loader0.js

loader0.js

136 ms

noggin_normal.jpg

noggin_normal.jpg

77 ms

ig-facebook-twitter2_normal.jpg

ig-facebook-twitter2_normal.jpg

101 ms

me.jpg

me.jpg

77 ms

rd_rb.jpg

rd_rb.jpg

93 ms

TechZwnLOGO_normal.jpg

TechZwnLOGO_normal.jpg

77 ms

0EgDip6Q.jpeg

0EgDip6Q.jpeg

77 ms

Capture.PNG

Capture.PNG

93 ms

c15821b511c2b55394fc63ce88a6bebe.jpeg

c15821b511c2b55394fc63ce88a6bebe.jpeg

80 ms

demo-2-thumb.png

demo-2-thumb.png

55 ms

morton.png

morton.png

53 ms

glyphicons-halflings-white.png

glyphicons-halflings-white.png

53 ms

caves.jpg

caves.jpg

66 ms

bananas.png

bananas.png

53 ms

download_on_app_store.png

download_on_app_store.png

52 ms

screenshot.png

screenshot.png

69 ms

facebook.png

facebook.png

69 ms

twitter.png

twitter.png

69 ms

glyphicons-halflings.png

glyphicons-halflings.png

67 ms

collect

collect

121 ms

MP50rOae6XQ

MP50rOae6XQ

48 ms

11507_1395617677337921_1400023302_n.png

11507_1395617677337921_1400023302_n.png

534 ms

12717484_1213713488656008_152927590916078555_n.jpg

12717484_1213713488656008_152927590916078555_n.jpg

597 ms

4495-755-10-7751.js

4495-755-10-7751.js

73 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

11 ms

www-embed-player.js

www-embed-player.js

42 ms

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

38 ms

ad_status.js

ad_status.js

40 ms

c

c

151 ms

4c4pf9mw.jpg

4c4pf9mw.jpg

36 ms

37 ms

xd_arbiter.php

xd_arbiter.php

214 ms

xd_arbiter.php

xd_arbiter.php

418 ms

LAH_n7nM.png

LAH_n7nM.png

5 ms

2xuG-ec_.jpg

2xuG-ec_.jpg

6 ms

nBcAijzu.png

nBcAijzu.png

6 ms

nr-885.min.js

nr-885.min.js

44 ms

inspectlet.js

inspectlet.js

9 ms

application2.js

application2.js

174 ms

1948270662

1948270662

32 ms

xd_arbiter.php

xd_arbiter.php

178 ms

eb70720532

eb70720532

53 ms

Accessibility Review

flowlab.io accessibility score

84

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

flowlab.io best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

flowlab.io SEO score

92

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flowlab.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Flowlab.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

flowlab.io

Open Graph description is not detected on the main page of Flowlab. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: