Access reader.bg. ::: Устройства за четене на електронни книги ::: ReaderBG :::

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.077

95/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

reader.bg

378 ms

reader.bg

460 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Reader.bg and no external sources were called. The less responsive or slowest element that took the longest time to load (460 ms) belongs to the original domain Reader.bg.

Content Size

1.1 MB

After Optimization

878.6 kB

In fact, the total size of Reader.bg main page is 1.1 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 822.9 kB which makes up the majority of the site volume.

HTML Optimization

-44%

Potential reduce by 548 B

Original 1.2 kB
After minification 1.2 kB
After compression 688 B

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 548 B or 44% of the original size.

Image Optimization

-2%

Potential reduce by 17.9 kB

Original 822.9 kB
After minification 805.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. Reader images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 121.3 kB

Original 184.6 kB
After minification 177.9 kB
After compression 63.4 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 121.3 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 47.0 kB

Original 56.6 kB
After minification 45.3 kB
After compression 9.6 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. Reader.bg needs all CSS files to be minified and compressed as it can save up to 47.0 kB or 83% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

High

robots.txt is not valid

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

BG
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reader.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian 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 Reader.bg main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

reader.bg

Open Graph description is not detected on the main page of Reader. 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: