Tools & Wizards About Us
teabass.com screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

teabass.com

Andrew Nesbitt | Andrew is a software developer, based in Somerset, UK. He spends most of his days programming in Ruby, contributing to open source pr...

Page Load Speed

856 ms in total

First Response

55 ms

Resources Loaded

365 ms

Page Rendered

436 ms

teabass.com screenshot

About Website

Welcome to teabass.com homepage info - get ready to check Teabass best content right away, or after learning these important things about teabass.com

Andrew is a software developer, based in Somerset, UK. He spends most of his days programming in Ruby, contributing to open source projects and organising local developer user groups.

Visit teabass.com

Key Findings

We analyzed Teabass.com page load time and found that the first response time was 55 ms and then it took 801 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

teabass.com performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

teabass.com

55 ms

nesbitt.io

71 ms

style.css

54 ms

bootstrap.min.css

68 ms

bootstrap-icons.min.css

60 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Teabass.com, 56% (9 requests) were made to Avatars.githubusercontent.com and 19% (3 requests) were made to Nesbitt.io. The less responsive or slowest element that took the longest time to load (112 ms) relates to the external source Nesbitt.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.5 kB (7%)

Content Size

835.2 kB

After Optimization

774.7 kB

  • HTML
  • Images

In fact, the total size of Teabass.com main page is 835.2 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. Images take 820.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 11.0 kB

  • Original 14.7 kB
  • After minification 13.1 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 1.6 kB, which is 11% 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 11.0 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 49.5 kB

  • Original 820.5 kB
  • After minification 771.0 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. Teabass images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

13

After Optimization

13

  • Images
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teabass. According to our analytics all requests are already optimized.

Network Requests Diagram

teabass.com

teabass.com

55 ms

nesbitt.io

nesbitt.io

71 ms

style.css

style.css

54 ms

bootstrap.min.css

bootstrap.min.css

68 ms

bootstrap-icons.min.css

bootstrap-icons.min.css

60 ms

face.jpg

face.jpg

112 ms

7920922

7920922

22 ms

24639960

24639960

22 ms

98474690

98474690

25 ms

11243589

11243589

24 ms

33007786

33007786

22 ms

11708074

11708074

21 ms

317889

317889

8 ms

1503512

1503512

8 ms

63009639

63009639

7 ms

bootstrap-icons.woff

bootstrap-icons.woff

12 ms

Accessibility Review

teabass.com accessibility score

71

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

teabass.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

teabass.com SEO score

91

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

Image elements do not have [alt] attributes

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

teabass.com

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