Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

fountainmn.org

City of Fountain - Official Website

Page Load Speed

1.3 sec in total

First Response

93 ms

Resources Loaded

987 ms

Page Rendered

268 ms

About Website

Click here to check amazing Fountain Mn content. Otherwise, check out these important facts you probably never knew about fountainmn.org

City Government

Visit fountainmn.org

Key Findings

We analyzed Fountainmn.org page load time and found that the first response time was 93 ms and then it took 1.3 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

fountainmn.org performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value530 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

fountainmn.org

93 ms

fountainmn.org

151 ms

index.html

40 ms

gdprscript.js

376 ms

sites.css

43 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 58% of them (11 requests) were addressed to the original Fountainmn.org, 42% (8 requests) were made to Cdn2.editmysite.com. The less responsive or slowest element that took the longest time to load (376 ms) belongs to the original domain Fountainmn.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.6 kB (12%)

Content Size

1.6 MB

After Optimization

1.4 MB

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

HTML Optimization

-77%

Potential reduce by 19.2 kB

  • Original 24.9 kB
  • After minification 24.5 kB
  • After compression 5.7 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 19.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 4.2 kB

  • Original 961.2 kB
  • After minification 956.9 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. Fountain Mn images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 155.8 kB

  • Original 563.5 kB
  • After minification 554.2 kB
  • After compression 407.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 155.8 kB or 28% of the original size.

CSS Optimization

-22%

Potential reduce by 9.4 kB

  • Original 42.7 kB
  • After minification 41.3 kB
  • After compression 33.2 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. Fountainmn.org needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 22% of the original size.

Requests Breakdown

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

Requests Now

16

After Optimization

11

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

Accessibility Review

fountainmn.org accessibility score

74

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

Best Practices

fountainmn.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fountainmn.org SEO score

85

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

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

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