Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

Page Load Speed

1.3 sec in total

First Response

56 ms

Resources Loaded

860 ms

Page Rendered

396 ms

tab.bz screenshot

About Website

Welcome to tab.bz homepage info - get ready to check Tab best content for United States right away, or after learning these important things about tab.bz

Store and share lists of links, text and other things

Visit tab.bz

Key Findings

We analyzed Tab.bz page load time and found that the first response time was 56 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

tab.bz performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value3,680 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

tab.bz

56 ms

d3c7fe355771ce4627f5b1540a7d0d76540302af.css

62 ms

a3cfc6ccd945d7098da45d159efa58502e83d20d.js

170 ms

font-awesome.min.css

129 ms

analytics.js

138 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 54% of them (14 requests) were addressed to the original Tab.bz, 15% (4 requests) were made to Platform.twitter.com and 12% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (225 ms) relates to the external source Platform.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.8 kB (41%)

Content Size

467.3 kB

After Optimization

273.4 kB

In fact, the total size of Tab.bz main page is 467.3 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. 40% of websites need less resources to load. Images take 360.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 16.5 kB

  • Original 21.3 kB
  • After minification 18.4 kB
  • After compression 4.8 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 3.0 kB, which is 14% 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 16.5 kB or 78% of the original size.

Image Optimization

-36%

Potential reduce by 129.7 kB

  • Original 360.1 kB
  • After minification 230.3 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, Tab needs image optimization as it can save up to 129.7 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-45%

Potential reduce by 26.9 kB

  • Original 59.2 kB
  • After minification 59.2 kB
  • After compression 32.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 26.9 kB or 45% of the original size.

CSS Optimization

-77%

Potential reduce by 20.6 kB

  • Original 26.7 kB
  • After minification 26.7 kB
  • After compression 6.1 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. Tab.bz needs all CSS files to be minified and compressed as it can save up to 20.6 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (37%)

Requests Now

19

After Optimization

12

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

Accessibility Review

tab.bz accessibility score

70

Accessibility Issues

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

tab.bz 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

Missing source maps for large first-party JavaScript

SEO Factors

tab.bz SEO score

81

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

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tab.bz can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Tab.bz 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 Tab. 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: