Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

hornblower.ticketmob.com

ticketmob.com

Page Load Speed

4.1 sec in total

First Response

778 ms

Resources Loaded

3.2 sec

Page Rendered

163 ms

hornblower.ticketmob.com screenshot

About Website

Click here to check amazing Hornblower Ticketmob content for United States. Otherwise, check out these important facts you probably never knew about hornblower.ticketmob.com

Hornblower

Visit hornblower.ticketmob.com

Key Findings

We analyzed Hornblower.ticketmob.com page load time and found that the first response time was 778 ms and then it took 3.4 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

hornblower.ticketmob.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

hornblower.ticketmob.com

778 ms

bootstrap.css

267 ms

bootstrap-ms.css

145 ms

bootstrap-theme.css

157 ms

font-awesome.min.css

160 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 14% of them (15 requests) were addressed to the original Hornblower.ticketmob.com, 29% (31 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Cdn.optimizely.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (72%)

Content Size

1.7 MB

After Optimization

466.9 kB

In fact, the total size of Hornblower.ticketmob.com main page is 1.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. 80% 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. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 33.9 kB

  • Original 43.6 kB
  • After minification 39.1 kB
  • After compression 9.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 33.9 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 1.2 kB

  • Original 69.0 kB
  • After minification 67.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. Hornblower Ticketmob images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 939.1 kB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 347.4 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 939.1 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 222.0 kB

  • Original 263.9 kB
  • After minification 230.9 kB
  • After compression 42.0 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. Hornblower.ticketmob.com needs all CSS files to be minified and compressed as it can save up to 222.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (79%)

Requests Now

98

After Optimization

21

The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hornblower Ticketmob. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

hornblower.ticketmob.com accessibility score

66

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

Best Practices

hornblower.ticketmob.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

High

Browser errors were logged to the console

SEO Factors

hornblower.ticketmob.com SEO score

85

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hornblower.ticketmob.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Hornblower.ticketmob.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

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