Tools & Wizards About Us
ticketking.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

ticketking.com

The Official Mirvish Website | Tickets to the Best Theatre in Toronto

Page Load Speed

2.5 sec in total

First Response

28 ms

Resources Loaded

1.3 sec

Page Rendered

1.1 sec

ticketking.com screenshot

About Website

Click here to check amazing Ticketking content for Canada. Otherwise, check out these important facts you probably never knew about ticketking.com

The best entertainment in Toronto. Bringing musicals, dramas, comedies and more to the theatre stage for over 50 years.

Visit ticketking.com

Key Findings

We analyzed Ticketking.com page load time and found that the first response time was 28 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ticketking.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value4,800 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

ticketking.com

28 ms

ticketking.com

16 ms

www.mirvish.com

304 ms

main.min.css

9 ms

site.js

20 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ticketking.com, 20% (17 requests) were made to Mirvish.com and 11% (9 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (392 ms) relates to the external source Consentag.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.9 kB (11%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ticketking.com main page is 1.6 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. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 173.7 kB

  • Original 191.6 kB
  • After minification 123.6 kB
  • After compression 17.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. This page needs HTML code to be minified as it can gain 68.0 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 173.7 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.1 MB
  • After minification 1.1 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. Ticketking images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.2 kB

  • Original 273.7 kB
  • After minification 273.6 kB
  • After compression 267.5 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

-0%

Potential reduce by 0 B

  • Original 33.3 kB
  • After minification 33.3 kB
  • After compression 33.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. Ticketking.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (63%)

Requests Now

68

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ticketking.com

ticketking.com

28 ms

ticketking.com

ticketking.com

16 ms

www.mirvish.com

www.mirvish.com

304 ms

main.min.css

main.min.css

9 ms

site.js

site.js

20 ms

js

js

66 ms

gtm.js

gtm.js

85 ms

fbevents.js

fbevents.js

16 ms

logomark-alt.svg

logomark-alt.svg

9 ms

logo.svg

logo.svg

8 ms

logo-alt.svg

logo-alt.svg

10 ms

js

js

99 ms

analytics.js

analytics.js

94 ms

js

js

94 ms

roundtrip.js

roundtrip.js

283 ms

destination

destination

231 ms

uwt.js

uwt.js

320 ms

events.js

events.js

301 ms

events.js

events.js

344 ms

jquery.min.js

jquery.min.js

332 ms

874c5b3bc4.js

874c5b3bc4.js

347 ms

page.js

page.js

330 ms

css2

css2

341 ms

main.min.js

main.min.js

282 ms

iframe_api

iframe_api

345 ms

asyncjs.php

asyncjs.php

345 ms

consenTag.js

consenTag.js

392 ms

ft600x600_les-mis-2023-800x800-web.jpg

ft600x600_les-mis-2023-800x800-web.jpg

284 ms

ft400x400_six-2023-800x800-web.jpg

ft400x400_six-2023-800x800-web.jpg

247 ms

ft400x400_rush-seats-800x800.jpg

ft400x400_rush-seats-800x800.jpg

272 ms

ft400x400_dog-man-2024-web-asset_800_x_800.jpg

ft400x400_dog-man-2024-web-asset_800_x_800.jpg

312 ms

ft400x400_jcs-2024-web-assets_800_x_800.jpg

ft400x400_jcs-2024-web-assets_800_x_800.jpg

313 ms

l_600x600_titanique-2024-web-asset_800_x_800.jpg

l_600x600_titanique-2024-web-asset_800_x_800.jpg

339 ms

s_300x200_jfod-2024-web-asset_800_x_800.jpg

s_300x200_jfod-2024-web-asset_800_x_800.jpg

299 ms

s_300x200_six-2023-800x800-web.jpg

s_300x200_six-2023-800x800-web.jpg

312 ms

s_300x200_cfa-2024-web-assets_800_x_800.jpg

s_300x200_cfa-2024-web-assets_800_x_800.jpg

316 ms

logomark.svg

logomark.svg

326 ms

collect

collect

88 ms

collect

collect

114 ms

collect

collect

199 ms

activityi;src=12783153;type=ev-mi0;cat=ev-mi0;ord=7226181066595;npa=0;auiddc=2093108477.1715573272;pscdl=noapi;frm=0;gtm=45fe4580z86295141za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.mirvish.com%2F

activityi;src=12783153;type=ev-mi0;cat=ev-mi0;ord=7226181066595;npa=0;auiddc=2093108477.1715573272;pscdl=noapi;frm=0;gtm=45fe4580z86295141za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.mirvish.com%2F

185 ms

collect

collect

116 ms

saq_pxl

saq_pxl

38 ms

js

js

99 ms

adsct

adsct

268 ms

adsct

adsct

253 ms

main.MTExZjAwMWE5MQ.js

main.MTExZjAwMWE5MQ.js

102 ms

sm.25.html

sm.25.html

53 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

81 ms

www-widgetapi.js

www-widgetapi.js

67 ms

popup_silent.html

popup_silent.html

39 ms

ga-audiences

ga-audiences

111 ms

ga-audiences

ga-audiences

149 ms

VIZ5CY6BSVHDVJLPKM4ENW

VIZ5CY6BSVHDVJLPKM4ENW

89 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

105 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

145 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

156 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

156 ms

src=12783153;type=ev-mi0;cat=ev-mi0;ord=7226181066595;npa=0;auiddc=*;pscdl=noapi;frm=0;gtm=45fe4580z86295141za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.mirvish.com%2F

src=12783153;type=ev-mi0;cat=ev-mi0;ord=7226181066595;npa=0;auiddc=*;pscdl=noapi;frm=0;gtm=45fe4580z86295141za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.mirvish.com%2F

173 ms

jquery.min.js

jquery.min.js

105 ms

mustache.min.js

mustache.min.js

125 ms

DHSZIMLB3ZARZAZMKD5ATB.js

DHSZIMLB3ZARZAZMKD5ATB.js

21 ms

out

out

7 ms

sendrolling.js

sendrolling.js

6 ms

out

out

5 ms

out

out

14 ms

out

out

15 ms

out

out

16 ms

out

out

27 ms

out

out

27 ms

pixel

pixel

89 ms

getuam

getuam

54 ms

tap.php

tap.php

82 ms

Pug

Pug

85 ms

integration

integration

57 ms

rum

rum

25 ms

sd

sd

10 ms

xuid

xuid

6 ms

in

in

4 ms

bounce

bounce

14 ms

sync

sync

17 ms

spp.pl

spp.pl

13 ms

activityi;src=14486773;type=invmedia;cat=six_t0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=0;gdpr_consent=;ord=1

activityi;src=14486773;type=invmedia;cat=six_t0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=0;gdpr_consent=;ord=1

94 ms

Accessibility Review

ticketking.com accessibility score

88

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

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

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

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

SEO Factors

ticketking.com SEO score

100

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ticketking.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 Ticketking.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

ticketking.com

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