8.2 sec in total
3.2 sec
4.1 sec
911 ms
Welcome to gettickets.ca homepage info - get ready to check Get Tickets best content for Canada right away, or after learning these important things about gettickets.ca
Visit gettickets.caWe analyzed Gettickets.ca page load time and found that the first response time was 3.2 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
gettickets.ca performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value4.8 s
30/100
25%
Value3.0 s
94/100
10%
Value50 ms
100/100
30%
Value0.186
65/100
15%
Value5.1 s
75/100
10%
3236 ms
24 ms
36 ms
208 ms
124 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 61% of them (30 requests) were addressed to the original Gettickets.ca, 22% (11 requests) were made to Dashboard.gettickets.ca and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Gettickets.ca.
Page size can be reduced by 340.9 kB (13%)
2.7 MB
2.4 MB
In fact, the total size of Gettickets.ca main page is 2.7 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. 40% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 28.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 5.6 kB, which is 16% 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 28.9 kB or 81% of the original size.
Potential reduce by 94.8 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. Get Tickets images are well optimized though.
Potential reduce by 117.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 117.6 kB or 71% of the original size.
Potential reduce by 99.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. Gettickets.ca needs all CSS files to be minified and compressed as it can save up to 99.6 kB or 88% of the original size.
Number of requests can be reduced by 7 (17%)
41
34
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Get Tickets. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
gettickets.ca
3236 ms
css
24 ms
css
36 ms
foundation.css
208 ms
app.css
124 ms
custom.modernizr.js
99 ms
foundation.min.js
100 ms
jquery.min.js
68 ms
analytics.js
95 ms
PreviewEventImages.ashx
224 ms
bg-charcoal-stripe.png
92 ms
logo-get-tickets@2x.png
112 ms
bg-nav.png
91 ms
custom-medium-small.jpg
156 ms
fireworks-medium-small.jpg
201 ms
coc-medium-small.jpg
197 ms
ago-medium-small.jpg
266 ms
bg-silver-stripe.png
115 ms
jetblue.jpg
152 ms
the-gentlemens-expo.jpg
186 ms
rogers-wireless-box-office.png
162 ms
logo-get-tickets-white@2x.png
177 ms
icon-facebook.png
234 ms
icon-twitter.png
212 ms
design-branding-agency.png
234 ms
PreviewEventImages.ashx
163 ms
PreviewEventImages.ashx
233 ms
PreviewEventImages.ashx
147 ms
PreviewEventImages.ashx
173 ms
PreviewEventImages.ashx
261 ms
PreviewEventImages.ashx
262 ms
PreviewEventImages.ashx
213 ms
PreviewEventImages.ashx
262 ms
PreviewEventImages.ashx
270 ms
PreviewEventImages.ashx
260 ms
montserrat-regular-webfont.woff
151 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
22 ms
IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff
22 ms
glegoo-regular-webfont.woff
165 ms
8x8S7gQMbbduiGv8gbUJ0Q.woff
22 ms
collect
26 ms
zepto.js
277 ms
montserrat-regular-webfont.ttf
44 ms
glegoo-regular-webfont.ttf
57 ms
bg-black-clear-bottom-left.png
30 ms
custom-xlarge.jpg
92 ms
fireworks-xlarge.jpg
87 ms
coc-xlarge.jpg
146 ms
ago-xlarge.jpg
186 ms
gettickets.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
[role] values are not valid
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
gettickets.ca 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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
gettickets.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gettickets.ca 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 Gettickets.ca 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.
gettickets.ca
Open Graph description is not detected on the main page of Get Tickets. 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: