Tools & Wizards About Us
floodmaps.fema.gov screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

floodmaps.fema.gov

FEMA Floodmaps | FEMA.gov

Page Load Speed

779 ms in total

First Response

101 ms

Resources Loaded

566 ms

Page Rendered

112 ms

floodmaps.fema.gov screenshot

About Website

Click here to check amazing Floodmaps FEMA content for United States. Otherwise, check out these important facts you probably never knew about floodmaps.fema.gov

Visit floodmaps.fema.gov

Key Findings

We analyzed Floodmaps.fema.gov page load time and found that the first response time was 101 ms and then it took 678 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

floodmaps.fema.gov performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

floodmaps.fema.gov

101 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

37 ms

css_qlad9M_6nfgKeqGUb_j6kXU2ooL3y2Xnrr-UoFqOpqc.css

85 ms

css_e-x4wyIysA6rGG0rFaXnQ3Sgx10OrZ1McUgscEeMpO8.css

42 ms

css_F1rmX5o6woNr2e3S2Dn0hG1q3QQrdGbUjE7eKW8tOtI.css

168 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Floodmaps.fema.gov, 76% (29 requests) were made to Fema.gov and 11% (4 requests) were made to Ct5.addthis.com. The less responsive or slowest element that took the longest time to load (168 ms) relates to the external source Fema.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 777.0 kB (74%)

Content Size

1.0 MB

After Optimization

272.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Floodmaps.fema.gov main page is 1.0 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. 50% of websites need less resources to load. Javascripts take 590.3 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 36.0 kB

  • Original 49.8 kB
  • After minification 45.3 kB
  • After compression 13.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 36.0 kB or 72% of the original size.

Image Optimization

-41%

Potential reduce by 26.4 kB

  • Original 64.1 kB
  • After minification 37.7 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. Obviously, Floodmaps FEMA needs image optimization as it can save up to 26.4 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 435.4 kB

  • Original 590.3 kB
  • After minification 484.0 kB
  • After compression 154.9 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 435.4 kB or 74% of the original size.

CSS Optimization

-81%

Potential reduce by 279.2 kB

  • Original 344.9 kB
  • After minification 336.4 kB
  • After compression 65.7 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. Floodmaps.fema.gov needs all CSS files to be minified and compressed as it can save up to 279.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (57%)

Requests Now

37

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floodmaps FEMA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

floodmaps.fema.gov

floodmaps.fema.gov

101 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

37 ms

css_qlad9M_6nfgKeqGUb_j6kXU2ooL3y2Xnrr-UoFqOpqc.css

css_qlad9M_6nfgKeqGUb_j6kXU2ooL3y2Xnrr-UoFqOpqc.css

85 ms

css_e-x4wyIysA6rGG0rFaXnQ3Sgx10OrZ1McUgscEeMpO8.css

css_e-x4wyIysA6rGG0rFaXnQ3Sgx10OrZ1McUgscEeMpO8.css

42 ms

css_F1rmX5o6woNr2e3S2Dn0hG1q3QQrdGbUjE7eKW8tOtI.css

css_F1rmX5o6woNr2e3S2Dn0hG1q3QQrdGbUjE7eKW8tOtI.css

168 ms

css_O6I4r6bli_as9-XSzn6AENQFVSaBY1DuaGqWddmX3Ok.css

css_O6I4r6bli_as9-XSzn6AENQFVSaBY1DuaGqWddmX3Ok.css

50 ms

css

css

25 ms

js_W17R0p1eaTrv8TlQ8hA9UJ61vhqpMbsuockS_wRla7c.js

js_W17R0p1eaTrv8TlQ8hA9UJ61vhqpMbsuockS_wRla7c.js

70 ms

js_THcwq4G882w3Eb1HklHrvzGAKa_-1g_0QbuBqjMhaV4.js

js_THcwq4G882w3Eb1HklHrvzGAKa_-1g_0QbuBqjMhaV4.js

74 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

132 ms

js_dfLdRkJzxu7RPLa8i_bSatluvtse7RphkxhAnx8LBpw.js

js_dfLdRkJzxu7RPLa8i_bSatluvtse7RphkxhAnx8LBpw.js

70 ms

js_Z0caIMq9WQ-aZ_ayVgRW-ORHYhzs1jpvjYSGfjjeip0.js

js_Z0caIMq9WQ-aZ_ayVgRW-ORHYhzs1jpvjYSGfjjeip0.js

71 ms

js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js

js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js

71 ms

js_vccNxmUat-77RTSOFBBzRS3Jq2yX3UzUMeCC7NCbZRg.js

js_vccNxmUat-77RTSOFBBzRS3Jq2yX3UzUMeCC7NCbZRg.js

73 ms

js_VMoiZWZ6HzS5HVx8h0M514bTVBorLQoESBt_7Epa9m8.js

js_VMoiZWZ6HzS5HVx8h0M514bTVBorLQoESBt_7Epa9m8.js

74 ms

floodmaps.css

floodmaps.css

31 ms

js_AZ9y0PShar4GyPuQUcAgecHmIwX4TUOo0HFPa06mnF0.js

js_AZ9y0PShar4GyPuQUcAgecHmIwX4TUOo0HFPa06mnF0.js

45 ms

js_x7i9_K8_u7Lf_Pr4XToSxjCDPT7-3IXdc15I1723_SU.js

js_x7i9_K8_u7Lf_Pr4XToSxjCDPT7-3IXdc15I1723_SU.js

49 ms

addthis_widget.js

addthis_widget.js

58 ms

fema-logo-main.png

fema-logo-main.png

14 ms

nav_blue.png

nav_blue.png

7 ms

search_blue.png

search_blue.png

8 ms

globe_blue.png

globe_blue.png

107 ms

icon_share.png

icon_share.png

6 ms

icon_facebook.png

icon_facebook.png

66 ms

icon_twitter.png

icon_twitter.png

12 ms

icon_linkedin.png

icon_linkedin.png

12 ms

icon_googleplus.png

icon_googleplus.png

12 ms

icon_tumblr.png

icon_tumblr.png

14 ms

icon_usflag.gif

icon_usflag.gif

14 ms

chevron-right-blue.gif

chevron-right-blue.gif

22 ms

chevron-right-orange.gif

chevron-right-orange.gif

23 ms

core032.js

core032.js

34 ms

widget092.css

widget092.css

6 ms

widgetIE67002.css

widgetIE67002.css

14 ms

nr-768.min.js

nr-768.min.js

16 ms

sh098.html

sh098.html

11 ms

877b02039c

877b02039c

46 ms

Accessibility Review

floodmaps.fema.gov accessibility score

97

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

Best Practices

floodmaps.fema.gov best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

floodmaps.fema.gov SEO score

83

Search Engine Optimization Advices

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 Floodmaps.fema.gov 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 Floodmaps.fema.gov 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

floodmaps.fema.gov

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