Tools & Wizards About Us
splittickets.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

splittickets.com

Split Train Tickets (Official Site)

Page Load Speed

1.2 sec in total

First Response

56 ms

Resources Loaded

637 ms

Page Rendered

489 ms

splittickets.com screenshot

About Website

Welcome to splittickets.com homepage info - get ready to check Split Tickets best content right away, or after learning these important things about splittickets.com

The Official Guide To Split Train Tickets:- Everything you need to know about saving money with split ticketing to booking legal cheap split train tickets online.

Visit splittickets.com

Key Findings

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

Performance Metrics

splittickets.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

splittickets.com

56 ms

splittickets.com

90 ms

bootstrap.css

138 ms

style.css

58 ms

owl.theme.css

51 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 57% of them (25 requests) were addressed to the original Splittickets.com, 34% (15 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (339 ms) belongs to the original domain Splittickets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 625.4 kB (40%)

Content Size

1.6 MB

After Optimization

930.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Splittickets.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. 55% of websites need less resources to load. Images take 806.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 20.0 kB

  • Original 26.2 kB
  • After minification 21.8 kB
  • After compression 6.2 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 4.4 kB, which is 17% 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 20.0 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 20.0 kB

  • Original 806.3 kB
  • After minification 786.3 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. Split Tickets images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 345.3 kB

  • Original 446.6 kB
  • After minification 343.6 kB
  • After compression 101.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 345.3 kB or 77% of the original size.

CSS Optimization

-87%

Potential reduce by 240.1 kB

  • Original 276.6 kB
  • After minification 222.6 kB
  • After compression 36.4 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. Splittickets.com needs all CSS files to be minified and compressed as it can save up to 240.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (70%)

Requests Now

27

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Split 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 12 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

splittickets.com

splittickets.com

56 ms

splittickets.com

splittickets.com

90 ms

bootstrap.css

bootstrap.css

138 ms

style.css

style.css

58 ms

owl.theme.css

owl.theme.css

51 ms

owl.carousel.css

owl.carousel.css

56 ms

prettyPhoto.css

prettyPhoto.css

76 ms

minimal-slider.css

minimal-slider.css

57 ms

fontawesome-all.css

fontawesome-all.css

99 ms

css

css

42 ms

css

css

76 ms

js

js

59 ms

jquery-2.2.3.min.js

jquery-2.2.3.min.js

98 ms

minimal-slider.js

minimal-slider.js

65 ms

owl.carousel.js

owl.carousel.js

87 ms

move-top.js

move-top.js

75 ms

easing.js

easing.js

79 ms

bootstrap.js

bootstrap.js

154 ms

jquery-1.7.2.js

jquery-1.7.2.js

162 ms

jquery.quicksand.js

jquery.quicksand.js

102 ms

pretty-script.js

pretty-script.js

101 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

117 ms

gtm.js

gtm.js

190 ms

1.jpg

1.jpg

339 ms

2.jpg

2.jpg

172 ms

3.jpg

3.jpg

172 ms

logo_small.png

logo_small.png

169 ms

booking_form.png

booking_form.png

171 ms

move_up.png

move_up.png

30 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

36 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

64 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

92 ms

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

93 ms

pxiGyp8kv8JHgFVrLPTucHtG.woff

pxiGyp8kv8JHgFVrLPTucHtG.woff

99 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

98 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

98 ms

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

98 ms

pxiGyp8kv8JHgFVrJJLucHtG.woff

pxiGyp8kv8JHgFVrJJLucHtG.woff

99 ms

pxiDyp8kv8JHgFVrJJLmg1hVF9eI.woff

pxiDyp8kv8JHgFVrJJLmg1hVF9eI.woff

99 ms

pxiDyp8kv8JHgFVrJJLm21lVF9eI.woff

pxiDyp8kv8JHgFVrJJLm21lVF9eI.woff

144 ms

pxiDyp8kv8JHgFVrJJLmv1pVF9eI.woff

pxiDyp8kv8JHgFVrJJLmv1pVF9eI.woff

143 ms

pxiAyp8kv8JHgFVrJJLmE0tCMPQ.woff

pxiAyp8kv8JHgFVrJJLmE0tCMPQ.woff

145 ms

pxiDyp8kv8JHgFVrJJLmr19VF9eI.woff

pxiDyp8kv8JHgFVrJJLmr19VF9eI.woff

144 ms

pxiDyp8kv8JHgFVrJJLmy15VF9eI.woff

pxiDyp8kv8JHgFVrJJLmy15VF9eI.woff

144 ms

Accessibility Review

splittickets.com accessibility score

87

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

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

splittickets.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

splittickets.com SEO score

78

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Splittickets.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 Splittickets.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

splittickets.com

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