790 ms in total
33 ms
507 ms
250 ms
Click here to check amazing Foam Cancer content. Otherwise, check out these important facts you probably never knew about foamcancer.com
Chemical-based firefighting foam has been sold for decades because of its effectiveness in extinguishing jet fuel and petroleum fires. However, it may cause various types of cancer — most notably kidn...
Visit foamcancer.comWe analyzed Foamcancer.com page load time and found that the first response time was 33 ms and then it took 757 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.
foamcancer.com performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value7.1 s
6/100
25%
Value3.0 s
94/100
10%
Value1,100 ms
23/100
30%
Value0
100/100
15%
Value6.3 s
61/100
10%
33 ms
56 ms
19 ms
120 ms
119 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Foamcancer.com, 25% (8 requests) were made to D9hhrg4mnvzow.cloudfront.net and 9% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (265 ms) relates to the external source D9hhrg4mnvzow.cloudfront.net.
Page size can be reduced by 79.1 kB (15%)
538.2 kB
459.1 kB
In fact, the total size of Foamcancer.com main page is 538.2 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. 55% of websites need less resources to load. Images take 401.6 kB which makes up the majority of the site volume.
Potential reduce by 45.8 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 45.8 kB or 83% of the original size.
Potential reduce by 268 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. Foam Cancer images are well optimized though.
Potential reduce by 33.0 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 33.0 kB or 42% of the original size.
Potential reduce by 30 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. Foamcancer.com has all CSS files already compressed.
Number of requests can be reduced by 11 (39%)
28
17
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foam Cancer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
foamcancer.com
33 ms
www.foamcancer.com
56 ms
main-7b78720.z.css
19 ms
js
120 ms
ub.js
119 ms
js
190 ms
main.bundle-fed11df.z.js
44 ms
fbevents.js
136 ms
analytics.js
79 ms
56a95368-unsplash-newctag6kpe-firefighter-training-fire_11hc0zk00000000000001o.jpg
265 ms
v
146 ms
77b282cc-unsplash-civuekjoote-lieutenant-observing-the-practice-fire_11hc0zk00000000000001o.jpg
261 ms
css
103 ms
6364112b-logo-elg_102q02q000000000000028.png
102 ms
ae93d23f-attorneys-update-peaple-last-min_107b02k000000000000028.png
209 ms
a7cf2621-logo-2x_102m02m000000000000028.png
95 ms
b3416308-av-martindale-hubbell_102o02t00000000000001o.jpg
98 ms
15fdb0a6-american-association-for-justice_104102d000000000000028.png
208 ms
7687153c-super-lawyers-logo_103r01f000000000000028.png
210 ms
collect
185 ms
sp-2.14.0.js
56 ms
conversion_async.js
159 ms
js
142 ms
542650800023496
200 ms
i
34 ms
4iCs6KVjbNBYlgoKfw7w.woff
50 ms
4iCv6KVjbNBYlgoCxCvjsGyL.woff
58 ms
collect
64 ms
50 ms
87 ms
ga-audiences
50 ms
39 ms
foamcancer.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
foamcancer.com 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
foamcancer.com SEO score
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 Foamcancer.com 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 Foamcancer.com 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.
foamcancer.com
Open Graph description is not detected on the main page of Foam Cancer. 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: