4.7 sec in total
88 ms
3.8 sec
773 ms
Visit fossa.io now to see the best up-to-date FOSSA content for India and also check out these interesting facts you probably never knew about fossa.io
Protect your software against open source risks including license violations, vulnerabilities, and supply chain threats.
Visit fossa.ioWe analyzed Fossa.io page load time and found that the first response time was 88 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fossa.io performance score
name
value
score
weighting
Value12.2 s
0/100
10%
Value15.5 s
0/100
25%
Value65.3 s
0/100
10%
Value74,390 ms
0/100
30%
Value0.066
97/100
15%
Value112.0 s
0/100
10%
88 ms
272 ms
473 ms
509 ms
466 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fossa.io, 13% (15 requests) were made to Fossa.com and 10% (12 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source App.fossa.com.
Page size can be reduced by 555.7 kB (59%)
934.3 kB
378.6 kB
In fact, the total size of Fossa.io main page is 934.3 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. 75% 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. HTML takes 776.1 kB which makes up the majority of the site volume.
Potential reduce by 547.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. 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 547.9 kB or 71% of the original size.
Potential reduce by 38 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. FOSSA images are well optimized though.
Potential reduce by 7.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 7.8 kB or 11% of the original size.
Potential reduce by 0 B
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. Fossa.io has all CSS files already compressed.
Number of requests can be reduced by 43 (47%)
92
49
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FOSSA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
fossa.com
88 ms
fossa-website-live.62d4c13ab.min.css
272 ms
webfont.js
473 ms
js
509 ms
jquery-3.5.1.min.dc5e7f18c8.js
466 ms
fossa-website-live.5f7a84d56.js
501 ms
css
277 ms
heap-2076844838.js
189 ms
munchkin.js
189 ms
analytics.js
1275 ms
munchkin.js
1232 ms
n9fz3b2fvhb6.js
1545 ms
roundtrip.js
1365 ms
hotjar-2340185.js
1534 ms
forms.js
1534 ms
j.php
1362 ms
5f6b592d61bad828d3fc3fee_link-arrow-white.svg
1177 ms
docs
1442 ms
register
1870 ms
fossa.com
1077 ms
547934
1869 ms
5f4d9ea2592c16d9a2b0f7da_logo-FOSSA-night-blue.svg
1144 ms
5f6228554d5916ab534d9be3_l%26c-nav.svg
1176 ms
5f6228554d591622724d9bed_vuln-nav.svg
1174 ms
5f6228554d591680594d9bee_risk-nav.svg
1166 ms
5f6228554d5916a8a44d9be7_dilligence-nav.svg
1163 ms
5f6228554d5916dc944d9bec_compliance-nav.svg
1176 ms
5f6228554d59165e9b4d9bf1_for-partners-nav.svg
1190 ms
5f6228554d5916b7374d9bf0_for-industries-nav.svg
1209 ms
5f6228554d5916314f4d9bef_for-role-nav.svg
1207 ms
601c16b044086862f691da08_Permissive-licenses.svg
1227 ms
5f7783d01f65bca534073080_Getting%E2%80%A8Started.png
1225 ms
5f6228554d591693504d9be6_docs-nav.svg
1220 ms
5f6228554d591648ba4d9be0_blog-nav.svg
1221 ms
5f75edb772ab346f36fb94eb_tldr-nav.svg
1232 ms
5f6228554d591614624d9be2_resources-nav.svg
1231 ms
5fcaa6d8700e86e89b970668_events-icon.svg
1236 ms
5f6228554d591634084d9be8_about-nav.svg
1236 ms
5f6228554d5916b5ea4d9bea_customers-nav.svg
1237 ms
5f6228554d5916129f4d9be4_careers-nav.png
1291 ms
5f6228554d59163e9d4d9beb_partners-nav.svg
1242 ms
5fd0f4176fb966427401a85a_news-icon.svg
1281 ms
5f6228554d591685ee4d9be1_contact-nav.svg
1234 ms
61bbd12aabdcb958a289d728_confluent-logo-with-BG.svg
1239 ms
61a10ab3199e425296b8a0b9_snap-logo-whiteBG.svg
1234 ms
61a10ab25870662f20422e93_slack-logo-whiteBG.svg
1381 ms
61a10ab223015c693fa2d678_twitter-logo-with-whiteBG.svg
1350 ms
61a10ab24f56294c99b41541_uber-logo-with-whiteBG.svg
1294 ms
61a10ab3524b4225dff47c2f_uipath-logo-with-whiteBG.svg
1292 ms
62bca052ad44d40a064acf74_value%2001.svg
1379 ms
62bca0526aadca75e330f70e_value%2002.svg
1375 ms
62bca052ede6bf59175bfcfb_value%2003.svg
1376 ms
5f68c790c1904347df327164_link-arrow.svg
1386 ms
604b711c5b8dbc9624d6ec13_Moonfare%20Logo%20Black.svg
1388 ms
604b76bd294a81e384c4c582_Puppet_Logo.svg
1443 ms
5f4da147ed38da4f31b46ee8_zendesk-logo-grey.svg
1618 ms
5f4d9ea2592c1633eeb0f7d7_OpenSauceTwo-SemiBold.ttf
419 ms
5f4d9ea2592c167054b0f7ce_OpenSauceTwo-ExtraBold.ttf
505 ms
5f4d9ea2592c1668c8b0f7ca_OpenSauceTwo-Black.ttf
514 ms
5f4d9ea2592c162547b0f7d3_OpenSauceTwo-Medium.ttf
831 ms
5f4d9ea2592c16f40ab0f7d6_OpenSauceTwo-Regular.ttf
748 ms
5f4d9ea2592c16999eb0f7d1_OpenSauceTwo-Light.ttf
747 ms
5f4d9ea2592c16a154b0f7c9_iAWriterQuattroS-Regular.ttf
749 ms
5f4d9ea2592c160f40b0f7c6_iAWriterQuattroS-Bold.ttf
830 ms
9BAAAAAQAAAAFtwAAAAAAAAAKABQAHgAyAEYAjACiAL4BFgE2AY4AAAABAAAADAA8AAMAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADQAAAAEAAAAAAAIABwCWAAEAAAAAAAMADQBIAAEAAAAAAAQADQCrAAEAAAAAAAUACwAnAAEAAAAAAAYADQBvAAEAAAAAAAoAGgDSAAMAAQQJAAEAGgANAAMAAQQJAAIADgCdAAMAAQQJAAMAGgBVAAMAAQQJAAQAGgC4AAMAAQQJAAUAFgAyAAMAAQQJAAYAGgB8AAMAAQQJAAoANADsd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzUmVndWxhcgBSAGUAZwB1AGwAYQByd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
16 ms
request-demo
114 ms
collect
110 ms
visitWebPage
304 ms
619feb14ccaf097d3a7b980a_8hero-animation.json
357 ms
6206e360df13bc34e1d06b1d_data2.json
510 ms
62151b5dc09f3b094331b79d_data2.json
436 ms
622a6e31ce48f5103a164a93_devs.json
413 ms
5f776ebf3f2f32afd1f3c089_verizon-logo.svg
693 ms
5f846adbe6016e34510f09d3_Group%20380.svg
693 ms
5f846ada21b8010c07bfce6d_Group%20383.svg
690 ms
announcing-private-beta-risk-intelligence
88 ms
collect
685 ms
v.gif
373 ms
HIVJNWTLHRFJLNP72U2QZ4
471 ms
index.js
424 ms
modules.cbd9768ba80ba0be5b17.js
512 ms
157 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
249 ms
fbevents.js
180 ms
VPUM6BGYHZFV3IXA64674L
152 ms
out
152 ms
out
79 ms
out
79 ms
out
150 ms
out
150 ms
out
180 ms
out
180 ms
out
179 ms
out
179 ms
ga-audiences
200 ms
risk-intelligence-addon
136 ms
tap.php
174 ms
Pug
150 ms
open-source-license-compliance
63 ms
ip-counsel-compliance-kit
65 ms
sync
28 ms
rum
24 ms
pixel
36 ms
open-source-vulnerability-management
46 ms
xuid
9 ms
in
6 ms
bounce
13 ms
22 ms
2424547574430956
78 ms
continuous-compliance
28 ms
sd
139 ms
due-diligence
65 ms
shift-left-risk-mitigation
41 ms
software-bill-materials-management
23 ms
customers
52 ms
fossa.io accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<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
Links do not have a discernible name
fossa.io 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
fossa.io 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
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fossa.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 Fossa.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.
fossa.io
Open Graph data is detected on the main page of FOSSA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: