Tools & Wizards About Us
projectwildfire.org screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

projectwildfire.org

Project Wildfire – Partnerships in Mitigation

Page Load Speed

6.3 sec in total

First Response

1 sec

Resources Loaded

4.8 sec

Page Rendered

496 ms

projectwildfire.org screenshot

About Website

Welcome to projectwildfire.org homepage info - get ready to check Project Wildfire best content right away, or after learning these important things about projectwildfire.org

Preventing deaths, injuries, property loss and environmental damage resulting from wildfires in Deschutes County

Visit projectwildfire.org

Key Findings

We analyzed Projectwildfire.org page load time and found that the first response time was 1 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

projectwildfire.org performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

www.projectwildfire.org

1048 ms

wp-emoji-release.min.js

114 ms

formidablepro.css

171 ms

swipebox.css

178 ms

bootstrap.css

157 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 80% of them (61 requests) were addressed to the original Projectwildfire.org, 5% (4 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Projectwildfire.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (35%)

Content Size

3.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Projectwildfire.org main page is 3.4 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. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 27.3 kB

  • Original 35.7 kB
  • After minification 34.1 kB
  • After compression 8.3 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 27.3 kB or 77% of the original size.

Image Optimization

-18%

Potential reduce by 424.9 kB

  • Original 2.3 MB
  • After minification 1.9 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, Project Wildfire needs image optimization as it can save up to 424.9 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 500.6 kB

  • Original 704.3 kB
  • After minification 631.6 kB
  • After compression 203.7 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 500.6 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 233.7 kB

  • Original 279.6 kB
  • After minification 251.0 kB
  • After compression 45.9 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. Projectwildfire.org needs all CSS files to be minified and compressed as it can save up to 233.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (76%)

Requests Now

72

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.projectwildfire.org

www.projectwildfire.org

1048 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

114 ms

formidablepro.css

formidablepro.css

171 ms

swipebox.css

swipebox.css

178 ms

bootstrap.css

bootstrap.css

157 ms

front.css

front.css

151 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

166 ms

wp-mediaelement.css

wp-mediaelement.css

190 ms

css

css

36 ms

css

css

43 ms

style.css

style.css

228 ms

sidebar-content.css

sidebar-content.css

257 ms

supersized.css

supersized.css

255 ms

supersized.shutter.css

supersized.shutter.css

253 ms

editor-style.css

editor-style.css

255 ms

main.css

main.css

268 ms

jetpack.css

jetpack.css

308 ms

jquery.js

jquery.js

402 ms

jquery-migrate.min.js

jquery-migrate.min.js

328 ms

jquery.swipebox.min.js

jquery.swipebox.min.js

341 ms

api.js

api.js

57 ms

scripts.js

scripts.js

333 ms

scripts-general.js

scripts-general.js

332 ms

spin.js

spin.js

371 ms

jquery.spin.js

jquery.spin.js

386 ms

tiled-gallery.js

tiled-gallery.js

443 ms

jquery.easing.min.js

jquery.easing.min.js

433 ms

supersized.3.2.7.min.js

supersized.3.2.7.min.js

434 ms

supersized.shutter.js

supersized.shutter.js

471 ms

fotorama.js

fotorama.js

534 ms

lightbox.js

lightbox.js

476 ms

css

css

38 ms

style_base.css

style_base.css

503 ms

skt_script.js

skt_script.js

504 ms

infinity.js

infinity.js

508 ms

jquery.cycle.js

jquery.cycle.js

573 ms

slideshow-shortcode.js

slideshow-shortcode.js

573 ms

photon.js

photon.js

617 ms

devicepx-jetpack.js

devicepx-jetpack.js

19 ms

jetpack-carousel.js

jetpack-carousel.js

667 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

671 ms

gprofiles.js

gprofiles.js

71 ms

e-201611.js

e-201611.js

20 ms

wp-mediaelement.js

wp-mediaelement.js

620 ms

wpgroho.js

wpgroho.js

535 ms

wp-embed.min.js

wp-embed.min.js

508 ms

css

css

14 ms

recaptcha__en.js

recaptcha__en.js

35 ms

close.png

close.png

208 ms

loading.gif

loading.gif

206 ms

prev.png

prev.png

206 ms

next.png

next.png

206 ms

bg-black.png

bg-black.png

208 ms

thumb-back.png

thumb-back.png

209 ms

thumb-forward.png

thumb-forward.png

223 ms

progress-back.png

progress-back.png

241 ms

pause.png

pause.png

708 ms

back.png

back.png

709 ms

forward.png

forward.png

706 ms

PW-website-logo-reversed-2.png

PW-website-logo-reversed-2.png

728 ms

nav-icon.png

nav-icon.png

707 ms

header-bottom-shape2.png

header-bottom-shape2.png

707 ms

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

6 ms

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

9 ms

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

10 ms

hovercard.css

hovercard.css

30 ms

services.css

services.css

52 ms

menu_sub_icon.png

menu_sub_icon.png

575 ms

g.gif

g.gif

6 ms

rows-burned.jpg

rows-burned.jpg

402 ms

def-space-in-action.png

def-space-in-action.png

875 ms

Shevlin-Fire-Pic-w-Treatment.jpg

Shevlin-Fire-Pic-w-Treatment.jpg

353 ms

B-B-Complex-Fire-020.jpg

B-B-Complex-Fire-020.jpg

466 ms

IMG_0373.jpg

IMG_0373.jpg

1516 ms

progress.gif

progress.gif

88 ms

progress-bar.png

progress-bar.png

72 ms

Accessibility Review

projectwildfire.org accessibility score

84

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

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

Links do not have a discernible name

Best Practices

projectwildfire.org 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

projectwildfire.org SEO score

92

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

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 Projectwildfire.org 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 Projectwildfire.org 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

projectwildfire.org

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