Access respondtodisaster.org. Respond to Disaster - Disaster Preparedness, Recovery and Insurance

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value2.3 s

98/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.069

96/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

respondtodisaster.org

66 ms

respondtodisaster.org

365 ms

style.css

13 ms

logo.jpg

30 ms

topbanner.jpg

51 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Respondtodisaster.org and no external sources were called. The less responsive or slowest element that took the longest time to load (365 ms) belongs to the original domain Respondtodisaster.org.

Content Size

98.1 kB

After Optimization

93.3 kB

In fact, the total size of Respondtodisaster.org main page is 98.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 92.7 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 3.4 kB

Original 5.4 kB
After minification 5.4 kB
After compression 2.1 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 3.4 kB or 62% of the original size.

Image Optimization

-2%

Potential reduce by 1.5 kB

Original 92.7 kB
After minification 91.2 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. Respond To Disaster images are well optimized though.

Requests Now

After Optimization

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Respond To Disaster. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Respondtodisaster.org 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 Respondtodisaster.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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