Tools & Wizards About Us

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

stlshakespeare.org

St. Louis Shakespeare: Pages

Page Load Speed

2 sec in total

First Response

63 ms

Resources Loaded

1.2 sec

Page Rendered

760 ms

About Website

Welcome to stlshakespeare.org homepage info - get ready to check St L Shakespeare best content for United States right away, or after learning these important things about stlshakespeare.org

St. Louis Shakespeare, presenting exciting classical theatre in St. Louis since 1984.

Visit stlshakespeare.org

Key Findings

We analyzed Stlshakespeare.org page load time and found that the first response time was 63 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

stlshakespeare.org performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.815

4/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

stlshakespeare.org

63 ms

www.stlshakespeare.org

107 ms

menu.js

14 ms

xr_main.css

25 ms

xr_text.css

25 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 54% of them (38 requests) were addressed to the original Stlshakespeare.org, 13% (9 requests) were made to W.sharethis.com and 7% (5 requests) were made to Sd.sharethis.com. The less responsive or slowest element that took the longest time to load (415 ms) belongs to the original domain Stlshakespeare.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.6 kB (23%)

Content Size

1.1 MB

After Optimization

844.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 25.1 kB

  • Original 29.7 kB
  • After minification 29.6 kB
  • After compression 4.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 25.1 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 47.9 kB

  • Original 816.6 kB
  • After minification 768.7 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. St L Shakespeare images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 154.4 kB

  • Original 219.8 kB
  • After minification 219.4 kB
  • After compression 65.4 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 154.4 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 25.2 kB

  • Original 30.8 kB
  • After minification 30.6 kB
  • After compression 5.6 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. Stlshakespeare.org needs all CSS files to be minified and compressed as it can save up to 25.2 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

66

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

stlshakespeare.org accessibility score

76

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

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

Impact

Issue

High

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

Best Practices

stlshakespeare.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

stlshakespeare.org SEO score

83

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

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

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stlshakespeare.org 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 Stlshakespeare.org main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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