Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

shakespearelives.org

Shakespeare Lives

Page Load Speed

5.3 sec in total

First Response

1.8 sec

Resources Loaded

3 sec

Page Rendered

488 ms

shakespearelives.org screenshot

About Website

Visit shakespearelives.org now to see the best up-to-date Shakespeare Lives content for Russia and also check out these interesting facts you probably never knew about shakespearelives.org

A global celebration of William Shakespeare on the 400th anniversary of his death

Visit shakespearelives.org

Key Findings

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

Performance Metrics

shakespearelives.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value22,170 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.691

7/100

15%

TTI (Time to Interactive)

Value33.9 s

0/100

10%

Network Requests Diagram

www.shakespearelives.org

1767 ms

webtrends.min.js

389 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

10 ms

css_MEszPaU-QQ7sVjz1mZc_OKfa4GQqsxkxCdvyMqn4n0Q.css

11 ms

bc-theme.css

91 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 61% of them (34 requests) were addressed to the original Shakespearelives.org, 7% (4 requests) were made to Sui.live.solas.britishcouncil.digital and 5% (3 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Shakespearelives.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 713.1 kB (54%)

Content Size

1.3 MB

After Optimization

619.2 kB

In fact, the total size of Shakespearelives.org main page is 1.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 494.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 58.5 kB

  • Original 70.6 kB
  • After minification 64.3 kB
  • After compression 12.1 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 58.5 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 14.9 kB

  • Original 423.1 kB
  • After minification 408.2 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. Shakespeare Lives images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 230.4 kB

  • Original 344.0 kB
  • After minification 317.2 kB
  • After compression 113.6 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 230.4 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 409.3 kB

  • Original 494.5 kB
  • After minification 493.3 kB
  • After compression 85.2 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. Shakespearelives.org needs all CSS files to be minified and compressed as it can save up to 409.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (37%)

Requests Now

51

After Optimization

32

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

Accessibility Review

shakespearelives.org accessibility score

63

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

shakespearelives.org best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

shakespearelives.org SEO score

76

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

High

robots.txt is not valid

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

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

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