Tools & Wizards About Us
nashfire.org screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

nashfire.org

Nashville Fire Department | Nashville.gov

Page Load Speed

2 sec in total

First Response

154 ms

Resources Loaded

1.5 sec

Page Rendered

375 ms

nashfire.org screenshot

About Website

Visit nashfire.org now to see the best up-to-date Nash Fire content and also check out these interesting facts you probably never knew about nashfire.org

Official website of the Metropolitan Government of Nashville and Davidson County.

Visit nashfire.org

Key Findings

We analyzed Nashfire.org page load time and found that the first response time was 154 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

nashfire.org performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

nashfire.org

154 ms

Fire-Department.aspx

568 ms

9a28fbeb343717fd07fd627b55f36b19.152.css

188 ms

94214549a3209b4ee00e4c44e9f04cfc.152.js

252 ms

styles.min.css

205 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Nashfire.org, 79% (54 requests) were made to Nashville.gov and 7% (5 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (568 ms) relates to the external source Nashville.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 429.6 kB (37%)

Content Size

1.2 MB

After Optimization

725.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nashfire.org main page is 1.2 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. 40% of websites need less resources to load. Images take 504.8 kB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 43.0 kB

  • Original 76.1 kB
  • After minification 71.7 kB
  • After compression 33.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 43.0 kB or 56% of the original size.

Image Optimization

-6%

Potential reduce by 30.0 kB

  • Original 504.8 kB
  • After minification 474.8 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. Nash Fire images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 243.8 kB

  • Original 430.2 kB
  • After minification 400.0 kB
  • After compression 186.5 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 243.8 kB or 57% of the original size.

CSS Optimization

-79%

Potential reduce by 112.8 kB

  • Original 143.6 kB
  • After minification 140.4 kB
  • After compression 30.8 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. Nashfire.org needs all CSS files to be minified and compressed as it can save up to 112.8 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

65

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nash Fire. 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

nashfire.org

nashfire.org

154 ms

Fire-Department.aspx

Fire-Department.aspx

568 ms

9a28fbeb343717fd07fd627b55f36b19.152.css

9a28fbeb343717fd07fd627b55f36b19.152.css

188 ms

94214549a3209b4ee00e4c44e9f04cfc.152.js

94214549a3209b4ee00e4c44e9f04cfc.152.js

252 ms

styles.min.css

styles.min.css

205 ms

WebResource.axd

WebResource.axd

230 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

297 ms

a1b2a34be0e91de38c30bb162edf3550.152.js

a1b2a34be0e91de38c30bb162edf3550.152.js

162 ms

ptm5bhs.js

ptm5bhs.js

201 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

116 ms

jquery.equal-height-columns.js

jquery.equal-height-columns.js

116 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

118 ms

jquery.cookie.js

jquery.cookie.js

123 ms

jquery.nv.common.js

jquery.nv.common.js

126 ms

jquery-ui.min.js

jquery-ui.min.js

116 ms

element.js

element.js

115 ms

initWidgets.js

initWidgets.js

123 ms

btn-search.gif

btn-search.gif

61 ms

logo-home.png

logo-home.png

67 ms

logo-home-print.png

logo-home-print.png

69 ms

NewAmericans.jpg

NewAmericans.jpg

82 ms

FluVaccination.jpg

FluVaccination.jpg

110 ms

fec.jpg

fec.jpg

113 ms

ebid3.jpg

ebid3.jpg

115 ms

DS-OneStopShop.jpg

DS-OneStopShop.jpg

123 ms

MM-Parthenon.jpg

MM-Parthenon.jpg

134 ms

FordIceCenter.jpg

FordIceCenter.jpg

162 ms

bcycle.jpg

bcycle.jpg

163 ms

Metro3logo.png

Metro3logo.png

181 ms

citizens_guide.jpg

citizens_guide.jpg

181 ms

NashvilleNext.jpg

NashvilleNext.jpg

182 ms

trash_icon.png

trash_icon.png

200 ms

water_icon.png

water_icon.png

221 ms

electric_icon.png

electric_icon.png

222 ms

vehicle_icon.png

vehicle_icon.png

223 ms

White%20-%20Smiling364.jpg

White%20-%20Smiling364.jpg

250 ms

FireLogo200.gif

FireLogo200.gif

252 ms

EMS364

EMS364

304 ms

CUsersbjboddiePicturesnews-articlesfire-pit-resize-364

CUsersbjboddiePicturesnews-articlesfire-pit-resize-364

257 ms

facebook-social.png

facebook-social.png

257 ms

twitter-social.png

twitter-social.png

258 ms

nashville-social.png

nashville-social.png

302 ms

facebook-social.png

facebook-social.png

302 ms

youtube-social.png

youtube-social.png

303 ms

govdelivery-social2.png

govdelivery-social2.png

409 ms

nashville-social.png

nashville-social.png

408 ms

Firenewbanner

Firenewbanner

292 ms

nv-inner-hdr-seal.png

nv-inner-hdr-seal.png

246 ms

bg-utilnav-navy-2016v2.png

bg-utilnav-navy-2016v2.png

247 ms

bg-utilnav-mobileapps2.png

bg-utilnav-mobileapps2.png

248 ms

bg-hr.gif

bg-hr.gif

229 ms

filetype-icons.png

filetype-icons.png

230 ms

bg-footer-shadow.jpg

bg-footer-shadow.jpg

209 ms

ga.js

ga.js

14 ms

translateelement.css

translateelement.css

60 ms

main.js

main.js

165 ms

__utm.gif

__utm.gif

118 ms

DotNetNukeAjaxShared.js

DotNetNukeAjaxShared.js

107 ms

icon-megamenu-arrow-down.gif

icon-megamenu-arrow-down.gif

50 ms

collect

collect

130 ms

widgets.js

widgets.js

113 ms

element_main.js

element_main.js

47 ms

translate_24dp.png

translate_24dp.png

48 ms

l

l

47 ms

cleardot.gif

cleardot.gif

68 ms

print.css

print.css

64 ms

te_ctrl3.gif

te_ctrl3.gif

13 ms

bg-utilnav-translate2.png

bg-utilnav-translate2.png

48 ms

Accessibility Review

nashfire.org accessibility score

100

Accessibility Issues

Best Practices

nashfire.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

nashfire.org SEO score

93

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 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 Nashfire.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 Nashfire.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

nashfire.org

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