Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

yellowbus.uk

Yellowbus Solutions Ltd - Managed IT Support, Hosted Services and Connectivity, Securely to Business Parks, Government, Nuclear

Page Load Speed

2.3 sec in total

First Response

173 ms

Resources Loaded

1.5 sec

Page Rendered

606 ms

yellowbus.uk screenshot

About Website

Welcome to yellowbus.uk homepage info - get ready to check Yellowbus best content right away, or after learning these important things about yellowbus.uk

At Yellowbus Solutions we work with you to improve your IT infrastructure with over 15 years experience working in some of the most secure industries in the world we are experts in taking care of your...

Visit yellowbus.uk

Key Findings

We analyzed Yellowbus.uk page load time and found that the first response time was 173 ms and then it took 2.1 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

yellowbus.uk performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

yellowbus.uk

173 ms

www.yellowbus.uk

277 ms

jquery-1.11.2.js

57 ms

project.css

97 ms

legacyGalleryModule.css

52 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 68% of them (45 requests) were addressed to the original Yellowbus.uk, 15% (10 requests) were made to Cdn2.hubspot.net and 5% (3 requests) were made to Static.hsappstatic.net. The less responsive or slowest element that took the longest time to load (771 ms) belongs to the original domain Yellowbus.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.0 kB (5%)

Content Size

2.8 MB

After Optimization

2.7 MB

In fact, the total size of Yellowbus.uk main page is 2.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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 61.8 kB

  • Original 73.4 kB
  • After minification 66.5 kB
  • After compression 11.6 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 61.8 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 73.9 kB

  • Original 2.6 MB
  • After minification 2.5 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. Yellowbus images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 7.8 kB

  • Original 158.5 kB
  • After minification 158.5 kB
  • After compression 150.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-22%

Potential reduce by 4.6 kB

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 16.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. Yellowbus.uk needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 22% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

34

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

Accessibility Review

yellowbus.uk accessibility score

82

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

yellowbus.uk 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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yellowbus.uk SEO score

90

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

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 Yellowbus.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 Yellowbus.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 data is detected on the main page of Yellowbus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: