Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

blog.tfl.gov.uk

TfL Digital

Page Load Speed

2.4 sec in total

First Response

227 ms

Resources Loaded

1.2 sec

Page Rendered

994 ms

blog.tfl.gov.uk screenshot

About Website

Click here to check amazing Blog TfL content for United Kingdom. Otherwise, check out these important facts you probably never knew about blog.tfl.gov.uk

Visit blog.tfl.gov.uk

Key Findings

We analyzed Blog.tfl.gov.uk page load time and found that the first response time was 227 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

blog.tfl.gov.uk performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value23.3 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

blog.tfl.gov.uk

227 ms

163 ms

css

89 ms

148 ms

176 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Blog.tfl.gov.uk, 26% (24 requests) were made to Pixel.wp.com and 13% (12 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (377 ms) relates to the external source S0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 659.3 kB (37%)

Content Size

1.8 MB

After Optimization

1.1 MB

In fact, the total size of Blog.tfl.gov.uk main page is 1.8 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. 65% of websites need less resources to load. Images take 909.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 85.5 kB

  • Original 108.0 kB
  • After minification 106.2 kB
  • After compression 22.5 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 85.5 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 4.6 kB

  • Original 909.2 kB
  • After minification 904.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. Blog TfL images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 539.2 kB

  • Original 741.7 kB
  • After minification 617.2 kB
  • After compression 202.5 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 539.2 kB or 73% of the original size.

CSS Optimization

-76%

Potential reduce by 30.0 kB

  • Original 39.6 kB
  • After minification 37.1 kB
  • After compression 9.7 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. Blog.tfl.gov.uk needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (71%)

Requests Now

82

After Optimization

24

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

Accessibility Review

blog.tfl.gov.uk accessibility score

89

Accessibility Issues

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-*] attributes do not match their roles

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

Links do not have a discernible name

Best Practices

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

SEO Factors

blog.tfl.gov.uk SEO score

92

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

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 Blog.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 Blog.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 Blog 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: