Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 65

    SEO

    Google-friendlier than
    25% of websites

tab.by

Поиск лекарств в аптеках Беларуси

Page Load Speed

4 sec in total

First Response

806 ms

Resources Loaded

3 sec

Page Rendered

145 ms

tab.by screenshot

About Website

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

Visit tab.by

Key Findings

We analyzed Tab.by page load time and found that the first response time was 806 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

tab.by performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.309

38/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

tab.by

806 ms

style.css

761 ms

jquery.min.js

878 ms

jquery.autocomplete.js

507 ms

chosen.jquery.js

643 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 74% of them (34 requests) were addressed to the original Tab.by, 7% (3 requests) were made to Pagead2.googlesyndication.com and 4% (2 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (888 ms) belongs to the original domain Tab.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 309.7 kB (32%)

Content Size

957.7 kB

After Optimization

648.0 kB

In fact, the total size of Tab.by main page is 957.7 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. 35% of websites need less resources to load. Javascripts take 437.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 37.9 kB

  • Original 48.1 kB
  • After minification 47.2 kB
  • After compression 10.2 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 37.9 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 14.5 kB

  • Original 410.0 kB
  • After minification 395.5 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. Tab images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 204.1 kB

  • Original 437.2 kB
  • After minification 421.9 kB
  • After compression 233.0 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 204.1 kB or 47% of the original size.

CSS Optimization

-85%

Potential reduce by 53.1 kB

  • Original 62.4 kB
  • After minification 49.0 kB
  • After compression 9.3 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.by needs all CSS files to be minified and compressed as it can save up to 53.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (18%)

Requests Now

45

After Optimization

37

The browser has sent 45 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 9 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

tab.by accessibility score

79

Accessibility Issues

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

Buttons do not have an accessible name

Low

No form fields have multiple labels

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

tab.by best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

tab.by SEO score

65

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

    RU

  • 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.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tab.by 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: