853 ms in total
37 ms
385 ms
431 ms
Click here to check amazing Flo content for United States. Otherwise, check out these important facts you probably never knew about flo.health
At Flo, we aim to improve the health and wellbeing of every girl, woman, and person who menstruates worldwide.
Visit flo.healthWe analyzed Flo.health page load time and found that the first response time was 37 ms and then it took 816 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.
flo.health performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value8.4 s
2/100
25%
Value2.8 s
96/100
10%
Value360 ms
72/100
30%
Value0
100/100
15%
Value7.8 s
45/100
10%
37 ms
64 ms
54 ms
16 ms
42 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 65% of them (17 requests) were addressed to the original Flo.health, 15% (4 requests) were made to Unpkg.com and 8% (2 requests) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (92 ms) relates to the external source Consent.cookiebot.com.
Page size can be reduced by 306.5 kB (64%)
475.7 kB
169.1 kB
In fact, the total size of Flo.health main page is 475.7 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. 25% of websites need less resources to load. HTML takes 293.1 kB which makes up the majority of the site volume.
Potential reduce by 218.2 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 218.2 kB or 74% of the original size.
Potential reduce by 0 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. Flo images are well optimized though.
Potential reduce by 88.4 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 88.4 kB or 75% of the original size.
Number of requests can be reduced by 5 (31%)
16
11
The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flo. 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 as a result speed up the page load time.
flo.health
37 ms
flo.health
64 ms
swiper-bundle.min.css
54 ms
img_flo_app_s.png
16 ms
iOS_1024_cut%201.svg
42 ms
Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917%201.svg
78 ms
google-play-badge%201.svg
43 ms
instagram-new.svg
40 ms
facebook-new.svg
38 ms
twitter-new.svg
36 ms
linkedin-new.svg
52 ms
rocket-loader.min.js
42 ms
swiper-bundle.min.css
19 ms
uc.js
69 ms
oboto-regular.woff
50 ms
oboto-medium.woff
66 ms
roboto-bold.woff
31 ms
roboto-black.woff
32 ms
configuration.js
58 ms
cc.js
92 ms
ScrollMagic.min.js
44 ms
bc-v4.min.html
55 ms
roboto-regular.ttf
18 ms
roboto-medium.ttf
26 ms
swiper-bundle.min.js
28 ms
swiper-bundle.min.js
22 ms
flo.health accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
flo.health best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
flo.health SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flo.health 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 Flo.health 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.
flo.health
Open Graph description is not detected on the main page of Flo. 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: