Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

next.boston.gov

Boston Digital Service | Boston.gov

Page Load Speed

1.2 sec in total

First Response

52 ms

Resources Loaded

892 ms

Page Rendered

233 ms

next.boston.gov screenshot

About Website

Visit next.boston.gov now to see the best up-to-date Next Boston content for United States and also check out these interesting facts you probably never knew about next.boston.gov

Our team is focused on partnering with City departments to improve service delivery across the City. We’re a cross-functional team with a mission to: improve the user experience of existing digital se...

Visit next.boston.gov

Key Findings

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

Performance Metrics

next.boston.gov performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

next.boston.gov

52 ms

kjpJhfqQnMotdcfYiaCT1ZxjXf4JQu895X5ZO67ORmjfe7wffFHN4UJLFRbh52jhWD9uweJ3FDByZQsKweBR5QZcZQqtF28yjUTdiaiaOco8pYb0jcNDieN0OciziKU0ZWyXOc4zSaszdKo1dajCdcmtie4zSaszdKoDSWmyScmDSeBRZPoRdhXCHKo0ZWyXjcNDieN0O1FUiABkZWF3jAF8OcFzdPJwSY4zpe8ljPu0daZyJyBKScB0ZeN0OAikdas8SaBuZPJ4Z1mXiW4yOWgXH6qJtKGbMg62JMJ7fbKzMsMMeMb6MKG4fJCgIMMjgkMfH6qJtkGbMg6FJMJ7fbK3MsMMeMt6MKG4fJ3gIMMjIPMfH6qJl8MbMs6IJMJ7fbKt9gMgeMS6MKG4fJBmIMJjgkMfH6qJ689bMy6sJMHbM-01r76B.js

75 ms

70 ms

next.boston.gov

199 ms

common-c2cb21af65f6d18bb4c6-min.js

79 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 11% of them (3 requests) were addressed to the original Next.boston.gov, 44% (12 requests) were made to Use.typekit.net and 26% (7 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (201 ms) belongs to the original domain Next.boston.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.7 kB (24%)

Content Size

266.8 kB

After Optimization

204.1 kB

In fact, the total size of Next.boston.gov main page is 266.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 174.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 60.6 kB

  • Original 75.2 kB
  • After minification 66.9 kB
  • After compression 14.6 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 8.4 kB, which is 11% 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 60.6 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 2.1 kB

  • Original 174.5 kB
  • After minification 172.4 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. Next Boston images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 4 (25%)

Requests Now

16

After Optimization

12

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

Accessibility Review

next.boston.gov accessibility score

89

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

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

next.boston.gov best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

next.boston.gov SEO score

91

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

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 Next.boston.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 Next.boston.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

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