Tools & Wizards About Us
defensibleapp.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    83% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

defensibleapp.com

Defensible Overall Fire Risk Rankings and Near Real Time Heat Detection

Page Load Speed

488 ms in total

First Response

122 ms

Resources Loaded

307 ms

Page Rendered

59 ms

defensibleapp.com screenshot

About Website

Welcome to defensibleapp.com homepage info - get ready to check Defensible App best content right away, or after learning these important things about defensibleapp.com

Every Building's Wildfire Risk all high risk states. Live Fire Data and Maps. California, Oregon, Washington Fire Risk

Visit defensibleapp.com

Key Findings

We analyzed Defensibleapp.com page load time and found that the first response time was 122 ms and then it took 366 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

defensibleapp.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

defensibleapp.com

122 ms

mapbox-gl.js

46 ms

mapbox-gl.css

43 ms

mapbox-gl-geocoder.min.js

49 ms

mapbox-gl-geocoder.css

54 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 22% of them (2 requests) were addressed to the original Defensibleapp.com, 44% (4 requests) were made to Api.mapbox.com and 11% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (122 ms) belongs to the original domain Defensibleapp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.8 kB (63%)

Content Size

28.5 kB

After Optimization

10.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Defensibleapp.com main page is 28.5 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. Only 10% of websites need less resources to load. HTML takes 23.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.6 kB

  • Original 23.8 kB
  • After minification 21.8 kB
  • After compression 6.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 17.6 kB or 74% of the original size.

Image Optimization

-24%

Potential reduce by 199 B

  • Original 828 B
  • After minification 629 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. Obviously, Defensible App needs image optimization as it can save up to 199 B or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 3.9 kB
  • After minification 3.9 kB
  • After compression 3.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

defensibleapp.com

defensibleapp.com

122 ms

mapbox-gl.js

mapbox-gl.js

46 ms

mapbox-gl.css

mapbox-gl.css

43 ms

mapbox-gl-geocoder.min.js

mapbox-gl-geocoder.min.js

49 ms

mapbox-gl-geocoder.css

mapbox-gl-geocoder.css

54 ms

js

js

117 ms

rocket-loader.min.js

rocket-loader.min.js

61 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

103 ms

fire_icon_large.png

fire_icon_large.png

80 ms

Accessibility Review

defensibleapp.com accessibility score

71

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

Internationalization and localization

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

Impact

Issue

High

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

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

Form elements do not have associated labels

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

defensibleapp.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

defensibleapp.com SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

defensibleapp.com

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