Tools & Wizards About Us
oldtheatreroyal.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

oldtheatreroyal.com

Bath's Old Theatre Royal - Museum, Tours, Live Events & Conferences

Page Load Speed

3.4 sec in total

First Response

280 ms

Resources Loaded

3 sec

Page Rendered

121 ms

oldtheatreroyal.com screenshot

About Website

Visit oldtheatreroyal.com now to see the best up-to-date Old Theatre Royal content and also check out these interesting facts you probably never knew about oldtheatreroyal.com

The Old Theatre Royal is open to the public on Tuesday, Wednesday, Thursday and Saturday for Guided Tours and is one of the must see places to visit in Bath

Visit oldtheatreroyal.com

Key Findings

We analyzed Oldtheatreroyal.com page load time and found that the first response time was 280 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

oldtheatreroyal.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.415

23/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

oldtheatreroyal.com

280 ms

oldtheatreroyal.com

1386 ms

analytics.js

36 ms

wp-emoji-release.min.js

135 ms

styles.css

216 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 82% of them (53 requests) were addressed to the original Oldtheatreroyal.com, 12% (8 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Oldtheatreroyal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 908.5 kB (32%)

Content Size

2.8 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oldtheatreroyal.com main page is 2.8 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 45.8 kB

  • Original 57.7 kB
  • After minification 53.1 kB
  • After compression 11.9 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 45.8 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 73.7 kB

  • Original 1.7 MB
  • After minification 1.6 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. Old Theatre Royal images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 379.2 kB

  • Original 547.7 kB
  • After minification 524.5 kB
  • After compression 168.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 379.2 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 409.8 kB

  • Original 500.1 kB
  • After minification 481.9 kB
  • After compression 90.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. Oldtheatreroyal.com needs all CSS files to be minified and compressed as it can save up to 409.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (54%)

Requests Now

54

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Old Theatre Royal. 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 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

oldtheatreroyal.com

oldtheatreroyal.com

280 ms

oldtheatreroyal.com

oldtheatreroyal.com

1386 ms

analytics.js

analytics.js

36 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

135 ms

styles.css

styles.css

216 ms

style.css

style.css

244 ms

styles.css

styles.css

479 ms

font-awesome.min.css

font-awesome.min.css

323 ms

xt-facebook-events.css

xt-facebook-events.css

322 ms

wprev-public_template1.css

wprev-public_template1.css

246 ms

wptripadvisor_w3.css

wptripadvisor_w3.css

297 ms

wprs_unslider.css

wprs_unslider.css

325 ms

wprs_unslider-dots.css

wprs_unslider-dots.css

326 ms

icon-list.css

icon-list.css

378 ms

default.min.css

default.min.css

401 ms

font-awesome.css

font-awesome.css

481 ms

virtue.css

virtue.css

718 ms

default.css

default.css

406 ms

css

css

39 ms

styles.css

styles.css

458 ms

jquery.js

jquery.js

638 ms

jquery-migrate.min.js

jquery-migrate.min.js

486 ms

frontend.min.js

frontend.min.js

540 ms

powered-by.js

powered-by.js

559 ms

fts-global.js

fts-global.js

561 ms

wprev-public.js

wprev-public.js

567 ms

wprs-unslider-min.js

wprs-unslider-min.js

620 ms

script.js

script.js

643 ms

collect

collect

12 ms

js

js

60 ms

plugins.js

plugins.js

910 ms

select2-min.js

select2-min.js

746 ms

main.js

main.js

653 ms

wp-embed.min.js

wp-embed.min.js

746 ms

FB-f-Logo__blue_291.png

FB-f-Logo__blue_291.png

85 ms

Twitter_logo_blue-e1423388383877.png

Twitter_logo_blue-e1423388383877.png

86 ms

instagram-icon-grey-background.jpg

instagram-icon-grey-background.jpg

85 ms

OTR-Gold-Logo_trans-800-e1423398909809.png

OTR-Gold-Logo_trans-800-e1423398909809.png

83 ms

OTR-Gold-Logo_trans-8001-e1423398935786.png

OTR-Gold-Logo_trans-8001-e1423398935786.png

84 ms

loader.gif

loader.gif

169 ms

Guidedtour-910x365.jpg

Guidedtour-910x365.jpg

271 ms

wedding-Charlotte-and-Moray-9908-910x365.jpg

wedding-Charlotte-and-Moray-9908-910x365.jpg

170 ms

wedding-Charlotte-and-Moray-9849-910x365.jpg

wedding-Charlotte-and-Moray-9849-910x365.jpg

323 ms

venues4.jpg

venues4.jpg

271 ms

wedding-Charlotte-and-Moray-9821-910x365.jpg

wedding-Charlotte-and-Moray-9821-910x365.jpg

327 ms

Beggars-910x365.jpg

Beggars-910x365.jpg

271 ms

performances9-910x365.png

performances9-910x365.png

585 ms

austen-1-910x365.jpg

austen-1-910x365.jpg

404 ms

aliceinwonderland-910x365.jpg

aliceinwonderland-910x365.jpg

330 ms

performances6.jpg

performances6.jpg

333 ms

Beggars-Opera-Thumbnail-240x250.jpg

Beggars-Opera-Thumbnail-240x250.jpg

405 ms

Venue-Hire-Thumbnail-240x250.jpg

Venue-Hire-Thumbnail-240x250.jpg

409 ms

12-underground-240x250.jpg

12-underground-240x250.jpg

410 ms

History-thumbnail-240x250.jpg

History-thumbnail-240x250.jpg

415 ms

gig5-240x250.jpg

gig5-240x250.jpg

485 ms

visitbathclear.png

visitbathclear.png

486 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

19 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

23 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

31 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

38 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

39 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

38 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

39 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

40 ms

virtue_icons.ttf

virtue_icons.ttf

467 ms

Accessibility Review

oldtheatreroyal.com accessibility score

71

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

oldtheatreroyal.com 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

SEO Factors

oldtheatreroyal.com SEO score

91

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

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 Oldtheatreroyal.com 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 Oldtheatreroyal.com 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

oldtheatreroyal.com

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