Access glastonbury-ct.gov. Glastonbury, CT | Welcome to the Town of Glastonbury, Connecticut

name

value

score

weighting

FCP (First Contentful Paint)

Value11.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value2,230 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.0 s

5/100

10%

glastonbury-ct.gov

46 ms

www.glastonburyct.gov

30 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Glastonbury-ct.gov, 50% (1 request) were made to Glastonburyct.gov. The less responsive or slowest element that took the longest time to load (46 ms) belongs to the original domain Glastonbury-ct.gov.

Content Size

1.0 MB

After Optimization

955.2 kB

In fact, the total size of Glastonbury-ct.gov main page is 1.0 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-30%

Potential reduce by 93 B

Original 313 B
After minification 309 B
After compression 220 B

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 93 B or 30% of the original size.

Image Optimization

-7%

Potential reduce by 72.9 kB

Original 1.0 MB
After minification 933.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. Glastonbury CT images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 3.8 kB

Original 25.4 kB
After minification 22.5 kB
After compression 21.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 3.8 kB or 15% of the original size.

CSS Optimization

-34%

Potential reduce by 177 B

Original 517 B
After minification 475 B
After compression 340 B

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. Glastonbury-ct.gov needs all CSS files to be minified and compressed as it can save up to 177 B or 34% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

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.

High

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

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

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 Glastonbury-ct.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 Glastonbury-ct.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

glastonbury-ct.gov

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