Tools & Wizards About Us
floodbarriers.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

floodbarriers.com

Flood Barrier Boston | Flood Control Products Florida

Page Load Speed

3.6 sec in total

First Response

105 ms

Resources Loaded

3 sec

Page Rendered

581 ms

floodbarriers.com screenshot

About Website

Click here to check amazing Flood Barrier S content. Otherwise, check out these important facts you probably never knew about floodbarriers.com

Walz & Krenzer Inc. provides Watertight Doors, Watertight Hatches and Flood Barriers of any size, for any location and for any Design Pressure! Call us today!

Visit floodbarriers.com

Key Findings

We analyzed Floodbarriers.com page load time and found that the first response time was 105 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

floodbarriers.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

floodbarriers.com

105 ms

stopfloods.com

2363 ms

js

235 ms

wpforms-full.min.css

16 ms

style.min.css

12 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Floodbarriers.com, 47% (31 requests) were made to Stopfloods.com and 45% (30 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Stopfloods.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (20%)

Content Size

6.1 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Floodbarriers.com main page is 6.1 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. 70% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 234.8 kB

  • Original 276.3 kB
  • After minification 273.1 kB
  • After compression 41.5 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 234.8 kB or 85% of the original size.

Image Optimization

-16%

Potential reduce by 874.1 kB

  • Original 5.3 MB
  • After minification 4.4 MB

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. Obviously, Flood Barrier S needs image optimization as it can save up to 874.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 136.3 kB

  • Original 512.6 kB
  • After minification 512.6 kB
  • After compression 376.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 136.3 kB or 27% of the original size.

CSS Optimization

-16%

Potential reduce by 5.0 kB

  • Original 31.7 kB
  • After minification 31.3 kB
  • After compression 26.6 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. Floodbarriers.com needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (70%)

Requests Now

33

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

floodbarriers.com

floodbarriers.com

105 ms

stopfloods.com

stopfloods.com

2363 ms

js

js

235 ms

wpforms-full.min.css

wpforms-full.min.css

16 ms

style.min.css

style.min.css

12 ms

style.css

style.css

41 ms

frontend-gtag.min.js

frontend-gtag.min.js

22 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

18 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

21 ms

jquery.min.js

jquery.min.js

21 ms

jquery-migrate.min.js

jquery-migrate.min.js

18 ms

scripts.min.js

scripts.min.js

26 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

22 ms

api.js

api.js

98 ms

recaptcha.js

recaptcha.js

25 ms

jquery.fitvids.js

jquery.fitvids.js

22 ms

easypiechart.js

easypiechart.js

25 ms

salvattore.js

salvattore.js

26 ms

frontend-bundle.min.js

frontend-bundle.min.js

26 ms

common.js

common.js

28 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

30 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

32 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

29 ms

gtm.js

gtm.js

227 ms

logo.png

logo.png

129 ms

Tom-Themel-IMG_0559.jpg

Tom-Themel-IMG_0559.jpg

130 ms

pr-firm-icon-8-multicolor-2.png

pr-firm-icon-8-multicolor-2.png

129 ms

pr-firm-icon-10-multicolor-1.png

pr-firm-icon-10-multicolor-1.png

129 ms

pr-firm-icon-7-multicolor-1.png

pr-firm-icon-7-multicolor-1.png

129 ms

Tunnel-Photo-400x250.jpg

Tunnel-Photo-400x250.jpg

129 ms

IMG_2955-website.jpg

IMG_2955-website.jpg

291 ms

P1090713.jpg

P1090713.jpg

304 ms

KFOlCnqEu92Fr1MmEU9fChc-.woff

KFOlCnqEu92Fr1MmEU9fChc-.woff

165 ms

KFOlCnqEu92Fr1MmEU9fChc9.ttf

KFOlCnqEu92Fr1MmEU9fChc9.ttf

202 ms

KFOmCnqEu92Fr1Mu7GxM.woff

KFOmCnqEu92Fr1Mu7GxM.woff

290 ms

KFOmCnqEu92Fr1Mu7GxP.ttf

KFOmCnqEu92Fr1Mu7GxP.ttf

211 ms

KFOlCnqEu92Fr1MmSU5fChc-.woff

KFOlCnqEu92Fr1MmSU5fChc-.woff

213 ms

KFOlCnqEu92Fr1MmSU5fChc9.ttf

KFOlCnqEu92Fr1MmSU5fChc9.ttf

291 ms

KFOkCnqEu92Fr1MmgVxGIzQ.woff

KFOkCnqEu92Fr1MmgVxGIzQ.woff

292 ms

KFOkCnqEu92Fr1MmgVxGIzc.ttf

KFOkCnqEu92Fr1MmgVxGIzc.ttf

288 ms

KFOlCnqEu92Fr1MmWUlfChc-.woff

KFOlCnqEu92Fr1MmWUlfChc-.woff

290 ms

KFOlCnqEu92Fr1MmWUlfChc9.ttf

KFOlCnqEu92Fr1MmWUlfChc9.ttf

291 ms

KFOlCnqEu92Fr1MmYUtfChc-.woff

KFOlCnqEu92Fr1MmYUtfChc-.woff

292 ms

KFOlCnqEu92Fr1MmYUtfChc9.ttf

KFOlCnqEu92Fr1MmYUtfChc9.ttf

293 ms

recaptcha__en.js

recaptcha__en.js

207 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EICuse0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EICuse0mg.woff

175 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EICuse0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EICuse0mj.ttf

175 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSuse0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSuse0mg.woff

174 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSuse0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSuse0mj.ttf

187 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Ebiuse0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Ebiuse0mg.woff

175 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Ebiuse0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Ebiuse0mj.ttf

187 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyuse0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyuse0mg.woff

176 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyuse0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyuse0mj.ttf

176 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyyse0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyyse0mg.woff

177 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyyse0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyyse0mj.ttf

188 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSyse0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSyse0mg.woff

177 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSyse0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSyse0mj.ttf

176 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yyse0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yyse0mg.woff

177 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yyse0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yyse0mj.ttf

179 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSyse0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSyse0mg.woff

178 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSyse0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSyse0mj.ttf

179 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2se0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2se0mg.woff

180 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2se0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2se0mj.ttf

178 ms

modules.ttf

modules.ttf

51 ms

style.min.css

style.min.css

36 ms

style.min.css

style.min.css

32 ms

Accessibility Review

floodbarriers.com accessibility score

86

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

floodbarriers.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

floodbarriers.com SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floodbarriers.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 Floodbarriers.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

floodbarriers.com

Open Graph data is detected on the main page of Flood Barrier S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: