Access minneapolismn.gov. City of Minneapolis

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value23.4 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,430 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.326

35/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

minneapolismn.gov

255 ms

sitenavigationfunctions.js

129 ms

sitenavigation.js

317 ms

wcm.toggle.js

129 ms

ssajax.js

159 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 71% of them (62 requests) were addressed to the original Minneapolismn.gov, 13% (11 requests) were made to V.qwikcast.tv and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (606 ms) belongs to the original domain Minneapolismn.gov.

Content Size

2.2 MB

After Optimization

1.1 MB

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

HTML Optimization

-79%

Potential reduce by 46.5 kB

Original 58.7 kB
After minification 49.0 kB
After compression 12.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 46.5 kB or 79% of the original size.

Image Optimization

-22%

Potential reduce by 240.1 kB

Original 1.1 MB
After minification 845.1 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. Obviously, Minneapolis Mn needs image optimization as it can save up to 240.1 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 583.3 kB

Original 798.4 kB
After minification 719.0 kB
After compression 215.1 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 583.3 kB or 73% of the original size.

CSS Optimization

-82%

Potential reduce by 239.7 kB

Original 290.8 kB
After minification 282.9 kB
After compression 51.1 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. Minneapolismn.gov needs all CSS files to be minified and compressed as it can save up to 239.7 kB or 82% of the original size.

Requests Now

After Optimization

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Minneapolis 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 23 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.