Report Summary

  • 66

    Performance

    Renders faster than
    78% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    38% of websites

  • 92

    SEO

    Google-friendlier than
    80% of websites

tabix.io

TABIX - Open source simple business intelligence application and sql editor tool for ClickHouse Database.

Page Load Speed

5.3 sec in total

First Response

362 ms

Resources Loaded

3 sec

Page Rendered

2 sec

tabix.io screenshot

About Website

Visit tabix.io now to see the best up-to-date TABIX content for India and also check out these interesting facts you probably never knew about tabix.io

TABIX - Open source simple business intelligence application and sql editor tool for ClickHouse Database.

Visit tabix.io

Key Findings

We analyzed Tabix.io page load time and found that the first response time was 362 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

tabix.io performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

tabix.io

362 ms

tabix.io

400 ms

bootstrap.min.css

193 ms

animate.min.css

289 ms

font-awesome.min.css

295 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 75% of them (24 requests) were addressed to the original Tabix.io, 13% (4 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Ui.tabix.io. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Tabix.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.0 kB (57%)

Content Size

389.6 kB

After Optimization

167.6 kB

In fact, the total size of Tabix.io main page is 389.6 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. 55% of websites need less resources to load. CSS take 208.2 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 35.3 kB

  • Original 39.1 kB
  • After minification 14.1 kB
  • After compression 3.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 25.1 kB, which is 64% 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 35.3 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 9.2 kB

  • Original 142.2 kB
  • After minification 133.1 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. TABIX images are well optimized though.

CSS Optimization

-85%

Potential reduce by 177.5 kB

  • Original 208.2 kB
  • After minification 203.5 kB
  • After compression 30.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. Tabix.io needs all CSS files to be minified and compressed as it can save up to 177.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (45%)

Requests Now

22

After Optimization

12

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

Accessibility Review

tabix.io accessibility score

80

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

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

tabix.io 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tabix.io SEO score

92

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

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 Tabix.io 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 Tabix.io 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 TABIX. 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: