Tools & Wizards About Us
utahfireinfo.gov screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 74

    SEO

    Google-friendlier than
    32% of websites

utahfireinfo.gov

Utah Fire Info

Page Load Speed

1.7 sec in total

First Response

319 ms

Resources Loaded

1.2 sec

Page Rendered

208 ms

utahfireinfo.gov screenshot

About Website

Click here to check amazing Utah Fire Info content for United States. Otherwise, check out these important facts you probably never knew about utahfireinfo.gov

The interagency-led resource for public information about wildfires in the state of Utah.

Visit utahfireinfo.gov

Key Findings

We analyzed Utahfireinfo.gov page load time and found that the first response time was 319 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

utahfireinfo.gov performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

www.utahfireinfo.gov

319 ms

maps

33 ms

extInfoWindow.js

166 ms

styles.css

152 ms

infoWind.css

110 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 29% of them (18 requests) were addressed to the original Utahfireinfo.gov, 32% (20 requests) were made to Maps.google.com and 16% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (330 ms) belongs to the original domain Utahfireinfo.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.8 kB (44%)

Content Size

1.1 MB

After Optimization

633.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 102.1 kB

  • Original 117.5 kB
  • After minification 110.8 kB
  • After compression 15.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 102.1 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 35.8 kB

  • Original 485.0 kB
  • After minification 449.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. Utah Fire Info images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 357.6 kB

  • Original 524.9 kB
  • After minification 509.5 kB
  • After compression 167.3 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 357.6 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 11.2 kB

  • Original 13.2 kB
  • After minification 8.2 kB
  • After compression 2.0 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. Utahfireinfo.gov needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (31%)

Requests Now

62

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.utahfireinfo.gov

www.utahfireinfo.gov

319 ms

maps

maps

33 ms

extInfoWindow.js

extInfoWindow.js

166 ms

styles.css

styles.css

152 ms

infoWind.css

infoWind.css

110 ms

SpryMenuBar.js

SpryMenuBar.js

221 ms

swfobject_modified.js

swfobject_modified.js

223 ms

SpryMenuBarHorizontal.css

SpryMenuBarHorizontal.css

164 ms

get_flash_player.gif

get_flash_player.gif

15 ms

bkg-pg.gif

bkg-pg.gif

65 ms

headerBack.jpg

headerBack.jpg

55 ms

mentoring.png

mentoring.png

56 ms

footer.jpg

footer.jpg

325 ms

9.jpg

9.jpg

330 ms

box-top-h.jpg

box-top-h.jpg

107 ms

box-mid-h.jpg

box-mid-h.jpg

104 ms

widgets.js

widgets.js

8 ms

bkg-tnav-h.jpg

bkg-tnav-h.jpg

94 ms

box-btm-h.jpg

box-btm-h.jpg

155 ms

common.js

common.js

15 ms

map.js

map.js

15 ms

overlay.js

overlay.js

12 ms

util.js

util.js

8 ms

marker.js

marker.js

8 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

188 ms

onion.js

onion.js

23 ms

openhand_8_8.cur

openhand_8_8.cur

78 ms

stats.js

stats.js

20 ms

kh

kh

59 ms

kh

kh

57 ms

controls.js

controls.js

11 ms

kh

kh

77 ms

kh

kh

81 ms

kh

kh

84 ms

kh

kh

77 ms

kh

kh

83 ms

kh

kh

77 ms

kh

kh

81 ms

transparent.png

transparent.png

41 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

82 ms

css

css

45 ms

infowindow.js

infowindow.js

23 ms

google4.png

google4.png

28 ms

mx.png

mx.png

67 ms

rx.png

rx.png

60 ms

mapcnt6.png

mapcnt6.png

32 ms

sv5.png

sv5.png

33 ms

tmapctrl.png

tmapctrl.png

22 ms

cb_scout5.png

cb_scout5.png

22 ms

tmapctrl4.png

tmapctrl4.png

21 ms

imgs8.png

imgs8.png

21 ms

google_white5.png

google_white5.png

19 ms

vt

vt

16 ms

vt

vt

7 ms

vt

vt

9 ms

vt

vt

10 ms

vt

vt

8 ms

vt

vt

10 ms

vt

vt

17 ms

vt

vt

16 ms

vt

vt

11 ms

vt

vt

19 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

36 ms

Accessibility Review

utahfireinfo.gov accessibility score

87

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

utahfireinfo.gov best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

utahfireinfo.gov SEO score

74

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

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

utahfireinfo.gov

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