Tools & Wizards About Us
foamfacts.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

foamfacts.com

Page Load Speed

2 sec in total

First Response

75 ms

Resources Loaded

1.2 sec

Page Rendered

718 ms

foamfacts.com screenshot

About Website

Welcome to foamfacts.com homepage info - get ready to check Foamfacts best content for United States right away, or after learning these important things about foamfacts.com

Learn more information about the health & environmental aspects of polystyrene foam through Foam Facts. We also share reliable foam facts related to recycling. Foam recycling is often mistakenly refer...

Visit foamfacts.com

Key Findings

We analyzed Foamfacts.com page load time and found that the first response time was 75 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

foamfacts.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value4,440 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

75 ms

masterslider.css

85 ms

style.css

197 ms

bootstrap.min.css

183 ms

style.css

253 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 43% of them (15 requests) were addressed to the original Foamfacts.com, 14% (5 requests) were made to Fonts.gstatic.com and 9% (3 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (411 ms) relates to the external source Dev.visualwebsiteoptimizer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.1 kB (8%)

Content Size

463.8 kB

After Optimization

428.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foamfacts.com main page is 463.8 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. 45% of websites need less resources to load. Images take 354.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 11.8 kB

  • Original 16.6 kB
  • After minification 13.5 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 3.1 kB, which is 19% 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 11.8 kB or 71% of the original size.

Image Optimization

-2%

Potential reduce by 6.4 kB

  • Original 354.5 kB
  • After minification 348.1 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. Foamfacts images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 11.2 kB

  • Original 79.6 kB
  • After minification 79.3 kB
  • After compression 68.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 11.2 kB or 14% of the original size.

CSS Optimization

-43%

Potential reduce by 5.7 kB

  • Original 13.2 kB
  • After minification 13.2 kB
  • After compression 7.5 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. Foamfacts.com needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (59%)

Requests Now

29

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foamfacts. 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 from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

75 ms

masterslider.css

masterslider.css

85 ms

style.css

style.css

197 ms

bootstrap.min.css

bootstrap.min.css

183 ms

style.css

style.css

253 ms

rte.css

rte.css

252 ms

scroll_animations.css

scroll_animations.css

254 ms

css

css

202 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

242 ms

jquery.validate.min.js

jquery.validate.min.js

239 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

236 ms

scroll_animations.js

scroll_animations.js

313 ms

sharethis.js

sharethis.js

238 ms

otSDKStub.js

otSDKStub.js

235 ms

bootstrap.min.js

bootstrap.min.js

191 ms

4b39781a-d1cd-476c-afad-9ebd883a1113.json

4b39781a-d1cd-476c-afad-9ebd883a1113.json

191 ms

analytics.js

analytics.js

187 ms

j.php

j.php

411 ms

foamfacts_logo_new.png

foamfacts_logo_new.png

194 ms

ff-hero-background.jpg

ff-hero-background.jpg

207 ms

home-container.png

home-container.png

328 ms

img-whychoosefoam.jpg

img-whychoosefoam.jpg

191 ms

img-litter.jpg

img-litter.jpg

191 ms

img-earth.jpg

img-earth.jpg

190 ms

gray-vector.jpg

gray-vector.jpg

208 ms

heating-and-cooling.png

heating-and-cooling.png

291 ms

3329.js

3329.js

288 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

248 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

249 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

290 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

291 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf

290 ms

otBannerSdk.js

otBannerSdk.js

174 ms

collect

collect

141 ms

v.gif

v.gif

33 ms

Accessibility Review

foamfacts.com accessibility score

79

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

foamfacts.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

foamfacts.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foamfacts.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Foamfacts.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.

Social Sharing Optimization

foamfacts.com

Open Graph description is not detected on the main page of Foamfacts. 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: