Tools & Wizards About Us
tickets.centertix.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

tickets.centertix.com

CenterTix :: Official Box Office of Alaska Center for the Performing Arts

Page Load Speed

2.2 sec in total

First Response

121 ms

Resources Loaded

1.2 sec

Page Rendered

936 ms

tickets.centertix.com screenshot

About Website

Welcome to tickets.centertix.com homepage info - get ready to check Tickets Center Tix best content for United States right away, or after learning these important things about tickets.centertix.com

CenterTix is your gateway to world class performances, right here in Anchorage, Alaska! All the hottest upcoming events & shows plus purchase tickets online at the guaranteed best price. We’re the Off...

Visit tickets.centertix.com

Key Findings

We analyzed Tickets.centertix.com page load time and found that the first response time was 121 ms and then it took 2.1 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

tickets.centertix.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value640 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

tickets.centertix.com

121 ms

tickets.centertix.com

178 ms

www.centertix.com

240 ms

centertix.com

538 ms

site-DNHhzfSo.css

20 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 11% of them (2 requests) were addressed to the original Tickets.centertix.com, 78% (14 requests) were made to Centertix.com and 6% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (538 ms) relates to the external source Centertix.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 488.4 kB (18%)

Content Size

2.8 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Tickets.centertix.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. 30% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 344.7 kB

  • Original 402.4 kB
  • After minification 399.6 kB
  • After compression 57.7 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 344.7 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 143.7 kB

  • Original 2.3 MB
  • After minification 2.2 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. Tickets Center Tix images are well optimized though.

CSS Optimization

-0%

Potential reduce by 40 B

  • Original 14.1 kB
  • After minification 14.1 kB
  • After compression 14.1 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. Tickets.centertix.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tickets Center Tix. According to our analytics all requests are already optimized.

Network Requests Diagram

tickets.centertix.com

tickets.centertix.com

121 ms

tickets.centertix.com

tickets.centertix.com

178 ms

www.centertix.com

www.centertix.com

240 ms

centertix.com

centertix.com

538 ms

site-DNHhzfSo.css

site-DNHhzfSo.css

20 ms

site-ByTZIpTd.css

site-ByTZIpTd.css

30 ms

gtm.js

gtm.js

62 ms

44826b436f31ae14705ea2351d412fa6.jpg

44826b436f31ae14705ea2351d412fa6.jpg

27 ms

9d5f2459dd97a59e18e025d2194bdf8b.jpg

9d5f2459dd97a59e18e025d2194bdf8b.jpg

26 ms

4ed59744c8d03bb781e4a6a375654eef.jpg

4ed59744c8d03bb781e4a6a375654eef.jpg

34 ms

33119127655.jpg

33119127655.jpg

40 ms

dd8d7f5b7582d6bbed5cbff91ffcfd85.jpg

dd8d7f5b7582d6bbed5cbff91ffcfd85.jpg

41 ms

0a734ba1495f2941c2f7a30747612886.jpg

0a734ba1495f2941c2f7a30747612886.jpg

39 ms

32014e9ab79cfda871aa188da3956bff.jpg

32014e9ab79cfda871aa188da3956bff.jpg

40 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

82 ms

3fec2866f33a0b21ad38b59442cc41de.jpg

3fec2866f33a0b21ad38b59442cc41de.jpg

31 ms

ticket-icon-ebeefe.svg

ticket-icon-ebeefe.svg

36 ms

d3ec52666f19711a38691a6033984fb9.jpg

d3ec52666f19711a38691a6033984fb9.jpg

42 ms

Accessibility Review

tickets.centertix.com accessibility score

76

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.

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

High

ARIA IDs are not unique

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

Links do not have a discernible name

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

tickets.centertix.com best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tickets.centertix.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

Links do not have descriptive text

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 Tickets.centertix.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 Tickets.centertix.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

tickets.centertix.com

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