Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

oyster.tfl.gov.uk

Oyster online - Transport for London - Contactless and Oyster

Page Load Speed

5.7 sec in total

First Response

361 ms

Resources Loaded

5.2 sec

Page Rendered

145 ms

oyster.tfl.gov.uk screenshot

About Website

Welcome to oyster.tfl.gov.uk homepage info - get ready to check Oyster Tfl best content for United Kingdom right away, or after learning these important things about oyster.tfl.gov.uk

Official online shop for Oyster card. Order your Travelcard or Bus & Tram Pass, top up Oyster pay as you go, or view your journeys.

Visit oyster.tfl.gov.uk

Key Findings

We analyzed Oyster.tfl.gov.uk page load time and found that the first response time was 361 ms and then it took 5.4 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

oyster.tfl.gov.uk performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value700 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

oyster.tfl.gov.uk

361 ms

entry.do

517 ms

tflGlobal.css

788 ms

oyster.css

321 ms

toploading.js

319 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 30% of them (16 requests) were addressed to the original Oyster.tfl.gov.uk, 41% (22 requests) were made to Account.tfl.gov.uk and 7% (4 requests) were made to Lo.v.liveperson.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Account.tfl.gov.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 945.0 kB (67%)

Content Size

1.4 MB

After Optimization

464.8 kB

In fact, the total size of Oyster.tfl.gov.uk main page is 1.4 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. Javascripts take 846.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 27.7 kB

  • Original 35.4 kB
  • After minification 30.2 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 15% 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 27.7 kB or 78% of the original size.

Image Optimization

-27%

Potential reduce by 52.2 kB

  • Original 191.8 kB
  • After minification 139.6 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. Obviously, Oyster Tfl needs image optimization as it can save up to 52.2 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 578.8 kB

  • Original 846.1 kB
  • After minification 815.7 kB
  • After compression 267.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 578.8 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 286.3 kB

  • Original 336.5 kB
  • After minification 301.1 kB
  • After compression 50.2 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. Oyster.tfl.gov.uk needs all CSS files to be minified and compressed as it can save up to 286.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (51%)

Requests Now

49

After Optimization

24

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

Accessibility Review

oyster.tfl.gov.uk accessibility score

93

Accessibility Issues

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

oyster.tfl.gov.uk best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

oyster.tfl.gov.uk SEO score

99

Search Engine Optimization Advices

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 Oyster.tfl.gov.uk 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 Oyster.tfl.gov.uk 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 Oyster Tfl. 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: