Tools & Wizards About Us
greaterbostonstage.org screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

greaterbostonstage.org

Vibrant Professional Theatre - Greater Boston Stage

Page Load Speed

2.6 sec in total

First Response

11 ms

Resources Loaded

1.2 sec

Page Rendered

1.4 sec

greaterbostonstage.org screenshot

About Website

Welcome to greaterbostonstage.org homepage info - get ready to check Greater Boston Stage best content for United States right away, or after learning these important things about greaterbostonstage.org

The Greater Boston Stage Company provides vibrant professional theatre and kids education to the communities surrounding Stoneham.

Visit greaterbostonstage.org

Key Findings

We analyzed Greaterbostonstage.org page load time and found that the first response time was 11 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

greaterbostonstage.org performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value21.1 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

greaterbostonstage.org

11 ms

www.greaterbostonstage.org

49 ms

js

137 ms

mediaelementplayer-legacy.min.css

18 ms

wp-mediaelement.min.css

30 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 67% of them (64 requests) were addressed to the original Greaterbostonstage.org, 19% (18 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (985 ms) relates to the external source Cdn.rlets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 455.1 kB (22%)

Content Size

2.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greaterbostonstage.org main page is 2.1 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. Only a small number of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 168.7 kB

  • Original 196.3 kB
  • After minification 189.4 kB
  • After compression 27.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. 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 168.7 kB or 86% of the original size.

Image Optimization

-17%

Potential reduce by 246.9 kB

  • Original 1.5 MB
  • After minification 1.2 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. Obviously, Greater Boston Stage needs image optimization as it can save up to 246.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-7%

Potential reduce by 13.9 kB

  • Original 203.7 kB
  • After minification 203.7 kB
  • After compression 189.8 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.

CSS Optimization

-13%

Potential reduce by 25.7 kB

  • Original 201.0 kB
  • After minification 201.0 kB
  • After compression 175.3 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. Greaterbostonstage.org needs all CSS files to be minified and compressed as it can save up to 25.7 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (86%)

Requests Now

65

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greaterbostonstage.org

greaterbostonstage.org

11 ms

www.greaterbostonstage.org

www.greaterbostonstage.org

49 ms

js

js

137 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

18 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

30 ms

style.css

style.css

48 ms

dashicons.min.css

dashicons.min.css

89 ms

css

css

163 ms

genericons.css

genericons.css

71 ms

font-awesome.min.css

font-awesome.min.css

80 ms

all.min.css

all.min.css

83 ms

all.min.css

all.min.css

72 ms

style.min.css

style.min.css

90 ms

theme.min.css

theme.min.css

100 ms

header-footer.min.css

header-footer.min.css

109 ms

frontend-lite.min.css

frontend-lite.min.css

101 ms

post-6.css

post-6.css

101 ms

elementor-icons.min.css

elementor-icons.min.css

97 ms

swiper.min.css

swiper.min.css

114 ms

frontend-lite.min.css

frontend-lite.min.css

121 ms

global.css

global.css

122 ms

post-10.css

post-10.css

123 ms

post-854.css

post-854.css

127 ms

post-61.css

post-61.css

119 ms

css

css

179 ms

fontawesome.min.css

fontawesome.min.css

148 ms

solid.min.css

solid.min.css

153 ms

regular.min.css

regular.min.css

152 ms

brands.min.css

brands.min.css

154 ms

frontend-gtag.min.js

frontend-gtag.min.js

155 ms

jquery.min.js

jquery.min.js

155 ms

jquery-migrate.min.js

jquery-migrate.min.js

157 ms

79c07a63-196c-481f-875f-59894373f049

79c07a63-196c-481f-875f-59894373f049

128 ms

4d84075996df47493139981.js

4d84075996df47493139981.js

985 ms

up.js

up.js

127 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

156 ms

widget-icon-list.min.css

widget-icon-list.min.css

160 ms

signup-form-widget.min.js

signup-form-widget.min.js

167 ms

animations.min.css

animations.min.css

152 ms

w.js

w.js

121 ms

tracks-callables.js

tracks-callables.js

154 ms

hello-frontend.min.js

hello-frontend.min.js

153 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

153 ms

hoverIntent.min.js

hoverIntent.min.js

154 ms

maxmegamenu.js

maxmegamenu.js

156 ms

public.js

public.js

155 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

162 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

143 ms

webpack.runtime.min.js

webpack.runtime.min.js

118 ms

frontend-modules.min.js

frontend-modules.min.js

102 ms

hooks.min.js

hooks.min.js

96 ms

i18n.min.js

i18n.min.js

86 ms

frontend.min.js

frontend.min.js

89 ms

waypoints.min.js

waypoints.min.js

88 ms

core.min.js

core.min.js

88 ms

frontend.min.js

frontend.min.js

79 ms

elements-handlers.min.js

elements-handlers.min.js

79 ms

gtm.js

gtm.js

264 ms

gtm.js

gtm.js

610 ms

masked-dots@2x.png

masked-dots@2x.png

485 ms

ms-bg.svg

ms-bg.svg

442 ms

Untitled-design-21-copy-2.png

Untitled-design-21-copy-2.png

836 ms

yc-bg.svg

yc-bg.svg

261 ms

se-bg.svg

se-bg.svg

353 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

564 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

563 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

562 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

562 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

566 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

565 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

620 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

622 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

622 ms

fa-solid-900.woff

fa-solid-900.woff

353 ms

fa-solid-900.ttf

fa-solid-900.ttf

478 ms

fa-solid-900.woff

fa-solid-900.woff

357 ms

fa-regular-400.woff

fa-regular-400.woff

355 ms

fa-regular-400.ttf

fa-regular-400.ttf

355 ms

fa-regular-400.woff

fa-regular-400.woff

523 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

618 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf

621 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf

621 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf

641 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf

641 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf

639 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf

640 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf

642 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf

642 ms

fa-brands-400.woff

fa-brands-400.woff

558 ms

fa-brands-400.ttf

fa-brands-400.ttf

557 ms

fa-brands-400.woff

fa-brands-400.woff

559 ms

wARDj0u

wARDj0u

6 ms

g.gif

g.gif

548 ms

Boston-Stage-Logo-RGB@2x-po894y8ecwlo3xoumda6zx3dyno3drxplpg4j7dufs.png

Boston-Stage-Logo-RGB@2x-po894y8ecwlo3xoumda6zx3dyno3drxplpg4j7dufs.png

405 ms

underscore-min.js

underscore-min.js

193 ms

Accessibility Review

greaterbostonstage.org accessibility score

95

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.

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

greaterbostonstage.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

greaterbostonstage.org SEO score

92

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

greaterbostonstage.org

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