Tools & Wizards About Us

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

book.splitticketing.com

Split Train Tickets | E-Tickets | Google/Apple Wallet | Save £20 on average

Page Load Speed

7.7 sec in total

First Response

2.4 sec

Resources Loaded

5.1 sec

Page Rendered

165 ms

About Website

Visit book.splitticketing.com now to see the best up-to-date Book Split Ticketing content for United Kingdom and also check out these interesting facts you probably never knew about book.splitticketing.com

The Split Ticketing Champions - Compare Fares and Get the Best Value For Money Through Split Tickets and Booking Cheap Train Tickets Online And On Our Mobile App, Etickets To Your Phone, No Booking Fe...

Visit book.splitticketing.com

Key Findings

We analyzed Book.splitticketing.com page load time and found that the first response time was 2.4 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

book.splitticketing.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value2,520 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

book.splitticketing.com

2446 ms

css2

26 ms

app.e68028da.css

461 ms

home.314c7798.css

253 ms

jquery.timepicker.min.css

596 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 63% of them (15 requests) were addressed to the original Book.splitticketing.com, 13% (3 requests) were made to Fonts.googleapis.com and 13% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Book.splitticketing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 335.8 kB (51%)

Content Size

658.1 kB

After Optimization

322.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Book.splitticketing.com main page is 658.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 314.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 262.8 kB

  • Original 314.2 kB
  • After minification 309.6 kB
  • After compression 51.4 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 262.8 kB or 84% of the original size.

JavaScript Optimization

-26%

Potential reduce by 72.9 kB

  • Original 285.0 kB
  • After minification 285.0 kB
  • After compression 212.1 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 72.9 kB or 26% of the original size.

CSS Optimization

-0%

Potential reduce by 167 B

  • Original 58.9 kB
  • After minification 58.9 kB
  • After compression 58.8 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. Book.splitticketing.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (55%)

Requests Now

20

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

book.splitticketing.com accessibility score

84

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

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

Best Practices

book.splitticketing.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

Missing source maps for large first-party JavaScript

SEO Factors

book.splitticketing.com SEO score

90

Search Engine Optimization Advices

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 Book.splitticketing.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 Book.splitticketing.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 Book Split Ticketing. 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: