2.6 sec in total
200 ms
2.1 sec
270 ms
Welcome to ezflofoam.com homepage info - get ready to check Ezflo Foam best content right away, or after learning these important things about ezflofoam.com
Reduce Your Shipping Costs! Packing foam and packaging systems by EZ-Flow can save you money! Offering a full line of chemicals & equipment.
Visit ezflofoam.comWe analyzed Ezflofoam.com page load time and found that the first response time was 200 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
ezflofoam.com performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value7.7 s
3/100
25%
Value9.8 s
10/100
10%
Value1,750 ms
10/100
30%
Value0.256
48/100
15%
Value21.9 s
1/100
10%
200 ms
160 ms
355 ms
29 ms
61 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 34% of them (36 requests) were addressed to the original Ezflofoam.com, 40% (42 requests) were made to Fonts.gstatic.com and 7% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (793 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 220.6 kB (4%)
5.3 MB
5.1 MB
In fact, the total size of Ezflofoam.com main page is 5.3 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. Only a small number of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 214.7 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 214.7 kB or 85% 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. Ezflo Foam images are well optimized though.
Potential reduce by 5.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 276 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. Ezflofoam.com has all CSS files already compressed.
Number of requests can be reduced by 34 (61%)
56
22
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezflo Foam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
ezflofoam.com
200 ms
www.ezflofoam.com
160 ms
www.ezflofoam.com
355 ms
wpsc-front-end-styles.css
29 ms
js
61 ms
js
106 ms
et-divi-customizer-global.min.css
33 ms
ez-flow-foam-logo.png
36 ms
K-pOPlRPl6U
165 ms
ClLk6XE0iZS79
609 ms
mediaelementplayer-legacy.min.css
33 ms
wp-mediaelement.min.css
33 ms
jquery.min.js
71 ms
jquery-migrate.min.js
71 ms
bundle.js
71 ms
hooks.min.js
70 ms
wordlift-cloud.js
114 ms
scripts.min.js
116 ms
jquery.fitvids.js
112 ms
magnific-popup.js
113 ms
easypiechart.js
110 ms
salvattore.js
111 ms
common.js
114 ms
mediaelement-and-player.min.js
117 ms
mediaelement-migrate.min.js
114 ms
wp-mediaelement.min.js
115 ms
Header-Image-6-2.png
118 ms
Header-Image-9.png
119 ms
Header-Image-7-2.png
122 ms
Header-Image-10.png
127 ms
Header-Image-8-2.png
126 ms
Header-Image-11.png
124 ms
Button-Equipment2-1-300x300.png
130 ms
Button-Spray-Foam-1-300x300.png
127 ms
Button-Applications3-300x300.png
139 ms
Button-Distributors-300x300.png
136 ms
Info-Pod-1.png
134 ms
www-player.css
12 ms
www-embed-player.js
31 ms
base.js
125 ms
ad_status.js
188 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk338xcDhrH.woff
188 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk338xcDhrE.ttf
427 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk37cxcDhrH.woff
426 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk37cxcDhrE.ttf
430 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk3M8tcDhrH.woff
495 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk3M8tcDhrE.ttf
480 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk3CstcDhrH.woff
428 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk3CstcDhrE.ttf
426 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYw.woff
426 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf
427 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYw.woff
428 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf
430 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYw.woff
430 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf
428 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYw.woff
429 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf
435 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYw.woff
437 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf
436 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYw.woff
435 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf
437 ms
modules.woff
138 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRZ-Rdv.woff
437 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRZ-Rds.ttf
642 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRZ-Rdv.woff
437 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRZ-Rds.ttf
492 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDRZ-Rdv.woff
437 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDRZ-Rds.ttf
437 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTnTRZ-Rdv.woff
641 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTnTRZ-Rds.ttf
639 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTBjNZ-Rdv.woff
645 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTBjNZ-Rds.ttf
740 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNZ-Rdv.woff
739 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNZ-Rds.ttf
719 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTajNZ-Rdv.woff
719 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTajNZ-Rds.ttf
739 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDNZ-Rdv.woff
730 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDNZ-Rds.ttf
793 ms
Create
381 ms
ZkUM7HQKzcKWL-DM3yo4WGnr3mDsumI-oijucI1qrYc.js
134 ms
embed.js
49 ms
ClLk6XE0iZS79
298 ms
jquery.min.js
64 ms
id
249 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDJZ-Rdv.woff
612 ms
embed
450 ms
style.min.css
212 ms
generate_204
67 ms
K-pOPlRPl6U
233 ms
dynamic.php
302 ms
css2
225 ms
ClLk6XE0iZS79
224 ms
submit-orange.png
377 ms
jquery-ui.min.js
56 ms
dynamic.php
377 ms
bottom.png
465 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDJZ-Rds.ttf
376 ms
style.min.css
257 ms
js
245 ms
none.png
154 ms
id
154 ms
S6uyw4BMUTPHvxk.ttf
96 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf
96 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
97 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
95 ms
ezflofoam.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ezflofoam.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ezflofoam.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
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 Ezflofoam.com 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 Ezflofoam.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.
ezflofoam.com
Open Graph data is detected on the main page of Ezflo Foam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: