16.6 sec in total
406 ms
15.9 sec
228 ms
Click here to check amazing Queen Elizabeth Theatre content for Canada. Otherwise, check out these important facts you probably never knew about queenelizabeththeatre.org
The Queen Elizabeth Theatre, Vancouver, Canada. Purchase tickets and view events for the Queen Elizabeth Theatre .
Visit queenelizabeththeatre.orgWe analyzed Queenelizabeththeatre.org page load time and found that the first response time was 406 ms and then it took 16.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
queenelizabeththeatre.org performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value18.6 s
0/100
25%
Value10.9 s
6/100
10%
Value50 ms
100/100
30%
Value0.239
52/100
15%
Value11.9 s
17/100
10%
406 ms
101 ms
194 ms
104 ms
104 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 63% of them (44 requests) were addressed to the original Queenelizabeththeatre.org, 11% (8 requests) were made to Apis.google.com and 10% (7 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (14.3 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 486.3 kB (60%)
807.6 kB
321.2 kB
In fact, the total size of Queenelizabeththeatre.org main page is 807.6 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. 55% of websites need less resources to load. Javascripts take 602.6 kB which makes up the majority of the site volume.
Potential reduce by 26.3 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 26.3 kB or 78% of the original size.
Potential reduce by 960 B
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. Queen Elizabeth Theatre images are well optimized though.
Potential reduce by 416.3 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 416.3 kB or 69% of the original size.
Potential reduce by 42.8 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. Queenelizabeththeatre.org needs all CSS files to be minified and compressed as it can save up to 42.8 kB or 82% of the original size.
Number of requests can be reduced by 54 (79%)
68
14
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Queen Elizabeth Theatre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.queenelizabeththeatre.org
406 ms
style.css
101 ms
events_manager.css
194 ms
checkbox.css
104 ms
form.css
104 ms
jquery.js
362 ms
jquery-migrate.min.js
139 ms
jquery.ui.core.min.js
194 ms
jquery.ui.widget.min.js
194 ms
jquery.ui.position.min.js
205 ms
jquery.ui.mouse.min.js
187 ms
jquery.ui.sortable.min.js
283 ms
jquery.ui.datepicker.min.js
297 ms
jquery.ui.menu.min.js
248 ms
jquery.ui.autocomplete.min.js
250 ms
jquery.ui.resizable.min.js
319 ms
jquery.ui.draggable.min.js
339 ms
jquery.ui.button.min.js
298 ms
jquery.ui.dialog.min.js
350 ms
events-manager.js
429 ms
jquery-1.4.1.min.js
538 ms
jquery.prettyPhoto.js
420 ms
jquery-supersleight.js
370 ms
jquery.nivo.slider.js
387 ms
cufon-yui.js
441 ms
Bebas_Neue_400.font.js
473 ms
League_Gothic_400.font.js
532 ms
init.js
472 ms
plusone.js
35 ms
show_ads.js
6 ms
placeholders.min.js
442 ms
reset.css
437 ms
common.css
473 ms
main.css
472 ms
sidebar.css
482 ms
footer.css
485 ms
sliders.css
524 ms
prettyPhoto.css
523 ms
nivo-slider.css
525 ms
ga.js
24 ms
bg.jpg
263 ms
queen-lgoo.png
262 ms
social_rss.png
73 ms
container_bg.png
71 ms
post_title_bg.png
71 ms
widgets.js
19 ms
__utm.gif
43 ms
cb=gapi.loaded_0
61 ms
zrt_lookup.html
128 ms
show_ads_impl.js
79 ms
likebox.php
180 ms
ads
261 ms
osd.js
76 ms
cb=gapi.loaded_1
19 ms
fastbutton
78 ms
E3TzvQNU166.css
14151 ms
q68gy-v_YMF.js
14166 ms
FJmpeSpHpjS.js
14283 ms
0wM5s1Khldu.js
14208 ms
1bNoFZUdlYZ.js
14208 ms
null
14151 ms
opacity_bg.png
52 ms
postmessageRelay
70 ms
cb=gapi.loaded_0
20 ms
cb=gapi.loaded_1
20 ms
3193398744-postmessagerelay.js
34 ms
rpc:shindig_random.js
39 ms
cb=gapi.loaded_0
5 ms
I6-MnjEovm5.js
43 ms
pQrUxxo5oQp.js
43 ms
queenelizabeththeatre.org accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
queenelizabeththeatre.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
queenelizabeththeatre.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Queenelizabeththeatre.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 Queenelizabeththeatre.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.
queenelizabeththeatre.org
Open Graph description is not detected on the main page of Queen Elizabeth Theatre. 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: