Tools & Wizards About Us
raileasy1t.trainsplit.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% 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

raileasy1t.trainsplit.com

Split Ticketing with TrainSplit | Mobile App | Save up to 90%

Page Load Speed

4.5 sec in total

First Response

998 ms

Resources Loaded

3.1 sec

Page Rendered

367 ms

raileasy1t.trainsplit.com screenshot

About Website

Welcome to raileasy1t.trainsplit.com homepage info - get ready to check Raileasy 1 T Train Split best content for United Kingdom right away, or after learning these important things about raileasy1t.trainsplit.com

TrainSplit compares routes & fares to get the best value through split ticketing with no booking fee & saving up to 90%

Visit raileasy1t.trainsplit.com

Key Findings

We analyzed Raileasy1t.trainsplit.com page load time and found that the first response time was 998 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

raileasy1t.trainsplit.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

trainsplit.com

998 ms

css2

27 ms

app.e68028da.css

325 ms

home.314c7798.css

247 ms

jquery.timepicker.min.css

252 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Raileasy1t.trainsplit.com, 9% (3 requests) were made to Fonts.googleapis.com and 9% (3 requests) were made to Directus.trainsplit.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Directus.trainsplit.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (39%)

Content Size

2.5 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Raileasy1t.trainsplit.com main page is 2.5 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. 20% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 297.8 kB

  • Original 351.7 kB
  • After minification 338.7 kB
  • After compression 53.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. 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 297.8 kB or 85% of the original size.

Image Optimization

-29%

Potential reduce by 588.6 kB

  • Original 2.0 MB
  • After minification 1.4 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. Obviously, Raileasy 1 T Train Split needs image optimization as it can save up to 588.6 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-88%

Potential reduce by 114.8 kB

  • Original 130.8 kB
  • After minification 130.8 kB
  • After compression 15.9 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 114.8 kB or 88% 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. Raileasy1t.trainsplit.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

29

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Raileasy 1 T Train Split. 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

trainsplit.com

trainsplit.com

998 ms

css2

css2

27 ms

app.e68028da.css

app.e68028da.css

325 ms

home.314c7798.css

home.314c7798.css

247 ms

jquery.timepicker.min.css

jquery.timepicker.min.css

252 ms

extra-css

extra-css

460 ms

avatar.jpg

avatar.jpg

188 ms

app-homepage.svg

app-homepage.svg

189 ms

google-play-new.svg

google-play-new.svg

268 ms

appstore.svg

appstore.svg

287 ms

runtime.128d72e1.js

runtime.128d72e1.js

272 ms

app.c8695539.js

app.c8695539.js

591 ms

home.786b1c4d.js

home.786b1c4d.js

699 ms

sharethis.js

sharethis.js

19 ms

jquery.timepicker.min.js

jquery.timepicker.min.js

374 ms

api.js

api.js

35 ms

nra_white.svg

nra_white.svg

462 ms

css

css

16 ms

css

css

33 ms

ic_empty_basket_blue.svg

ic_empty_basket_blue.svg

291 ms

ic_journey_planner.svg

ic_journey_planner.svg

351 ms

294c5869-0139-4f48-98fc-2f8fe2adbbe7

294c5869-0139-4f48-98fc-2f8fe2adbbe7

542 ms

TSWebHeroImage_L.e7a1e38b.webp

TSWebHeroImage_L.e7a1e38b.webp

404 ms

5fdfdf73-2ee8-49d0-b9d7-381fd5a13a71

5fdfdf73-2ee8-49d0-b9d7-381fd5a13a71

1125 ms

217feb48-5338-4579-9811-9f73a626fcca

217feb48-5338-4579-9811-9f73a626fcca

1300 ms

S6uyw4BMUTPHvxo.woff

S6uyw4BMUTPHvxo.woff

18 ms

S6u9w4BMUTPHh7USeww.woff

S6u9w4BMUTPHh7USeww.woff

29 ms

S6u9w4BMUTPHh6UVeww.woff

S6u9w4BMUTPHh6UVeww.woff

29 ms

ic_share_twitter.svg

ic_share_twitter.svg

227 ms

ic_share_facebook.svg

ic_share_facebook.svg

275 ms

trainsplit_logo_blue.svg

trainsplit_logo_blue.svg

133 ms

ic_close.svg

ic_close.svg

83 ms

ic_plus_grey.svg

ic_plus_grey.svg

93 ms

Accessibility Review

raileasy1t.trainsplit.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

raileasy1t.trainsplit.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

raileasy1t.trainsplit.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 Raileasy1t.trainsplit.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 Raileasy1t.trainsplit.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

raileasy1t.trainsplit.com

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