Tools & Wizards About Us
franklintn.gov screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

franklintn.gov

City of Franklin, TN | Home

Page Load Speed

2.5 sec in total

First Response

408 ms

Resources Loaded

1.9 sec

Page Rendered

203 ms

franklintn.gov screenshot

About Website

Welcome to franklintn.gov homepage info - get ready to check Franklin TN best content for United States right away, or after learning these important things about franklintn.gov

Visit franklintn.gov

Key Findings

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

Performance Metrics

franklintn.gov performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value22.5 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value5,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.263

47/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

Network Requests Diagram

franklintn.gov

408 ms

StyleBundleDesignTheme.cssbnd

335 ms

StyleBundleDesignTheme.cssbnd

212 ms

StyleBundleFrontendExtra.cssbnd

219 ms

ScriptBundleFAllInOne.jsbnd

556 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 83% of them (49 requests) were addressed to the original Franklintn.gov, 7% (4 requests) were made to Translate.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (640 ms) belongs to the original domain Franklintn.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 300.5 kB (17%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Franklintn.gov main page is 1.8 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 64.2 kB

  • Original 81.0 kB
  • After minification 77.8 kB
  • After compression 16.8 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 64.2 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 60.2 kB

  • Original 1.4 MB
  • After minification 1.4 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. Franklin TN images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 175.9 kB

  • Original 278.8 kB
  • After minification 278.8 kB
  • After compression 102.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 175.9 kB or 63% of the original size.

CSS Optimization

-4%

Potential reduce by 162 B

  • Original 3.8 kB
  • After minification 3.8 kB
  • After compression 3.7 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. Franklintn.gov has all CSS files already compressed.

Requests Breakdown

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

Requests Now

58

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

franklintn.gov

franklintn.gov

408 ms

StyleBundleDesignTheme.cssbnd

StyleBundleDesignTheme.cssbnd

335 ms

StyleBundleDesignTheme.cssbnd

StyleBundleDesignTheme.cssbnd

212 ms

StyleBundleFrontendExtra.cssbnd

StyleBundleFrontendExtra.cssbnd

219 ms

ScriptBundleFAllInOne.jsbnd

ScriptBundleFAllInOne.jsbnd

556 ms

x-small.css

x-small.css

158 ms

element.js

element.js

54 ms

StyleBundleSingleDropDown.cssbnd

StyleBundleSingleDropDown.cssbnd

188 ms

StyleBundleSingleDropDown.cssbnd

StyleBundleSingleDropDown.cssbnd

232 ms

ScriptBundleVisionFrontend.jsbnd

ScriptBundleVisionFrontend.jsbnd

231 ms

analytics.js

analytics.js

36 ms

messagebox_strip.gif

messagebox_strip.gif

94 ms

bg_strip.jpg

bg_strip.jpg

95 ms

bg_top.jpg

bg_top.jpg

595 ms

bg_bottom.jpg

bg_bottom.jpg

392 ms

spacer.gif

spacer.gif

96 ms

logo.png

logo.png

95 ms

sitemap.gif

sitemap.gif

145 ms

contact.gif

contact.gif

146 ms

top_nav_bottom.png

top_nav_bottom.png

143 ms

translateelement.css

translateelement.css

81 ms

main.js

main.js

87 ms

ShowImage

ShowImage

382 ms

ShowImage

ShowImage

244 ms

ShowImage

ShowImage

379 ms

ShowImage

ShowImage

196 ms

ShowImage

ShowImage

276 ms

ShowImage

ShowImage

330 ms

ShowImage

ShowImage

354 ms

ShowImage

ShowImage

410 ms

ShowImage

ShowImage

433 ms

ShowImage

ShowImage

436 ms

ShowImage

ShowImage

457 ms

ShowImage

ShowImage

461 ms

ShowImage

ShowImage

487 ms

ShowImage

ShowImage

516 ms

ShowImage

ShowImage

518 ms

ShowImage

ShowImage

545 ms

ShowImage

ShowImage

545 ms

ShowImage

ShowImage

566 ms

ShowImage

ShowImage

601 ms

ShowImage

ShowImage

598 ms

ShowImage

ShowImage

622 ms

ShowImage

ShowImage

624 ms

ShowImage

ShowImage

640 ms

collect

collect

40 ms

collect

collect

107 ms

element_main.js

element_main.js

52 ms

collage_top.png

collage_top.png

567 ms

collage_right.png

collage_right.png

592 ms

btn_prev.png

btn_prev.png

560 ms

btn_next.png

btn_next.png

583 ms

translate_24dp.png

translate_24dp.png

55 ms

l

l

43 ms

cleardot.gif

cleardot.gif

41 ms

Print.cssbnd

Print.cssbnd

69 ms

Print.cssbnd

Print.cssbnd

73 ms

collage_prev.png

collage_prev.png

82 ms

collage_next.png

collage_next.png

82 ms

Accessibility Review

franklintn.gov accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

[role]s are not contained by their required parent element

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

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

franklintn.gov best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

franklintn.gov SEO score

75

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

Content Best Practices

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

Impact

Issue

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

    EN

  • Encoding

    UTF-8

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

franklintn.gov

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